HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- VM no not start
Operating System - HP-UX
1827448
Members
5837
Online
109965
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-26-2011 08:46 AM
04-26-2011 08:46 AM
VM no not start
The last boot message is :
hpvmdynmem: unable to reach target memory size of 2106 MB after 60 seconds, resulting memory size is 5370 MB.
Thanks for your comments and help
I am usig T2767CC B.04.20.05 Integrity VM
hpvmdynmem: unable to reach target memory size of 2106 MB after 60 seconds, resulting memory size is 5370 MB.
Thanks for your comments and help
I am usig T2767CC B.04.20.05 Integrity VM
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-26-2011 11:40 AM
04-26-2011 11:40 AM
Re: VM no not start
As the message says, there is insufficient memory available to reach the targeted amount. Reduce the memory config in the VM, or check where you can reduce memory from any other vm's running
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-26-2011 01:26 PM
04-26-2011 01:26 PM
Re: VM no not start
Thanks for your comments
The issue is that I have a BL890 with 80GB RAM, only one VM with 18 GB and the problem persist.
I am loking for last VM Patches
I will keep you informed
Best Regards
The issue is that I have a BL890 with 80GB RAM, only one VM with 18 GB and the problem persist.
I am loking for last VM Patches
I will keep you informed
Best Regards

Not applicable
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-26-2011 11:16 PM
04-26-2011 11:16 PM
Re: VM no not start
It's a known problem with unpatched V4.2.5.
The problem is indirectly caused by HPVM V4.2.5 enabling HPVM dynamic memory feature by default. The default values of ram_dyn_target_start and ram_dyn_max can default to 2G which, in the case of a larger memory guest, will not be enough memory for the guest to properly run or even boot.
The problem is resolved in HPVM V4.2.5 Day1 Core patch PHSS_41190 (or later). Make sure to install the latest HPVM patches immediately after updating HPVM.
Note!
If the guest boot was already attempted before the patch was installed, installing the patch by itself will not prevent the problem and reconfiguration of dynamic memory settings is necessary for the guest
to be able to boot again.
As a workaround HPVM dynamic memory can be disabled by
# hpvmmodify -P ${guest_name} -x ram_dyn_type=none
The manageability features for HP-UX guests brought by enabling HPVM dynamic memory can safely be re-enabled once PHSS_41190 (or later) has been installed by
# hpvmmodify -P ${guest_name} -x ram_dyn_type=any
If ram_dyn_target_start and ram_dyn_max have already been set, then you need to change their values to the desired range dependent on the configured memory size.
It's recommended that ram_dyn_target_start (and ram_dyn_min) should not fall below 25% (or 1GB whichever is higher) of memory configured for the guest. ram_dyn_max should be set to the memory configured.
The problem is indirectly caused by HPVM V4.2.5 enabling HPVM dynamic memory feature by default. The default values of ram_dyn_target_start and ram_dyn_max can default to 2G which, in the case of a larger memory guest, will not be enough memory for the guest to properly run or even boot.
The problem is resolved in HPVM V4.2.5 Day1 Core patch PHSS_41190 (or later). Make sure to install the latest HPVM patches immediately after updating HPVM.
Note!
If the guest boot was already attempted before the patch was installed, installing the patch by itself will not prevent the problem and reconfiguration of dynamic memory settings is necessary for the guest
to be able to boot again.
As a workaround HPVM dynamic memory can be disabled by
# hpvmmodify -P ${guest_name} -x ram_dyn_type=none
The manageability features for HP-UX guests brought by enabling HPVM dynamic memory can safely be re-enabled once PHSS_41190 (or later) has been installed by
# hpvmmodify -P ${guest_name} -x ram_dyn_type=any
If ram_dyn_target_start and ram_dyn_max have already been set, then you need to change their values to the desired range dependent on the configured memory size.
It's recommended that ram_dyn_target_start (and ram_dyn_min) should not fall below 25% (or 1GB whichever is higher) of memory configured for the guest. ram_dyn_max should be set to the memory configured.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP