- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - VMware
- >
- Host CPU incompatible (migration problem) - ESX 3....
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО11-04-2010 12:23 AM
тАО11-04-2010 12:23 AM
I have a weird problem during host update process. I'm using a ESX cluster with this specs:
- 2 HP Blades Proliant BL480c G1 (Xeon E5450 3Ghz) with ESX 3.5.0 build 283373 (already updated to last ESX 3.5.0build)
- 2 HP Blades Proliant BL480c G1 (Xeon E5450 3Ghz) with ESX 3.5.0 build 153875 (next hosts to update)
HA and DRS support.
I already updated two of my four host, but when I'm trying migrate all VM's from my third host for put this host in maintenance mode (if I put this mode directly, the VM's aren't been migrated automatically -maybe a bug?, It keep at 2% permanently and never end the task-, so I need migrate manually), I receive an error message (I put it bottom) that I already received in the past when I hadn't the hyperthreading and VT configuration correctly set, but now, I have disabled the hyperthreading and enabled IntelVT in all host, so I don't understand the problem. By other hand, in the past this problem only happened with 64bits CPU VM, but now happen with many VM (32 & 64 bits).
I've tried some scenarios and this is the result:
1 - Migrate VM in power ON state: fail
2 - Migrate VM in power OFF state: ok
3 - Migrate VM in power ON state hidding NX previously in VM configuration, and show NX when VM already is in target host: ok
* If I return to source host a VM after a previous migration, this VM won't have problem anymore for migrate again to other host, independently of his state (it can be in poweron with expose NX).
I can avoid the problem with scenarios 2 and 3, but I want know the cause of problem...
ERROR (I read many discussions about this error message, but I don't find my solution):
-----------------------------------------------
Unable to migrate from xxx.server to yyy.server: Host CPU is
incompatible with the virtual machine's requirements at CPUID level
0x80000001 register 'edx'.
hosts bits: 0010:0000:0000:0000:0000:0000:0000:0000
required: 00x00:0000:0001:0000:0000:x000:0000:0000
*
NX/ND (data execution protection). If the virtual machine does not need
this feature, power oof the virtual machine and remove the NX/XD
requirement by editing the virtual machine settings (advanced options).
---------------------------------------------
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2010 09:44 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2010 11:44 PM
тАО11-04-2010 11:44 PM
Re: Host CPU incompatible (migration problem) - ESX 3.5
If is the second case, I don't think that would be the problem, since I have two host without update to last build, and only one of them have this problem.
By other hand, EVC mode is disabled at cluster level, since vCenter say that 3 of my 4 host are incompatible (the only compatible is the host that are showing this problem). But all host have same hardware... and same CPU... I don't understand...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2010 11:49 PM
тАО11-04-2010 11:49 PM
Re: Host CPU incompatible (migration problem) - ESX 3.5
If you have EVC mode disabled, it is really strange. Update ESX soon or contact Vmware support.
Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-05-2010 02:33 AM
тАО11-05-2010 02:33 AM
Re: Host CPU incompatible (migration problem) - ESX 3.5
This 3 hosst was showed as incompatible with EVC mode and migration of many VM from the only host that had NX activated in BIOS to this hosts, produce incompatible CPU problems.
So, problem fixed.
PS: the problem was the NX support from bios, not the status (on/off) of the EVC in the cluster, but the NX support also affect to the posibility of enable EVC. EVC required NX bit support from BIOS enabled.
Thank you very much
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-05-2010 11:40 AM
тАО11-05-2010 11:40 AM
Re: Host CPU incompatible (migration problem) - ESX 3.5
VMKB1001131 - vMotion fails with the error: problem detected at CPUID level 0x80000001 register 'edx'
http://kb.vmware.com/kb/1001131