Comments on: Cannot vmotion on new IBM x3650 servers http://www.sysdigg.com/cannot-vmotion-on-new-ibm-x3650-servers Thu, 09 Feb 2012 19:49:36 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: IBM BIOS recommendations for ESX | EsxBulletin.com http://www.sysdigg.com/cannot-vmotion-on-new-ibm-x3650-servers/comment-page-1#comment-1937 IBM BIOS recommendations for ESX | EsxBulletin.com Wed, 05 Oct 2011 19:38:59 +0000 http://www.sysdigg.com/cannot-vmotion-on-new-ibm-x3650-servers#comment-1937 [...] Bit in the CPU settings was disabled.  This can cause vMotion to fail as described in this article here .  So you would want to enable the Execute Disable [...] [...] Bit in the CPU settings was disabled.  This can cause vMotion to fail as described in this article here .  So you would want to enable the Execute Disable [...]

]]> By: IBM BIOS recommendations for ESX « IT Knowledge Base http://www.sysdigg.com/cannot-vmotion-on-new-ibm-x3650-servers/comment-page-1#comment-1773 IBM BIOS recommendations for ESX « IT Knowledge Base Tue, 19 Jul 2011 09:07:31 +0000 http://www.sysdigg.com/cannot-vmotion-on-new-ibm-x3650-servers#comment-1773 [...] Bit in the CPU settings was disabled.  This can cause vMotion to fail as described in this article here .  So you would want to enable the Execute Disable [...] [...] Bit in the CPU settings was disabled.  This can cause vMotion to fail as described in this article here .  So you would want to enable the Execute Disable [...]

]]> By: J.J. http://www.sysdigg.com/cannot-vmotion-on-new-ibm-x3650-servers/comment-page-1#comment-679 J.J. Thu, 08 Oct 2009 18:35:49 +0000 http://www.sysdigg.com/cannot-vmotion-on-new-ibm-x3650-servers#comment-679 Good catch but you actually want that disabled on all of your hosts if you plan on using Enhanced Vmotion Compatibility mode (mixing different CPU steppings or families together, e.g. adding a newer M2 to an existing x3650 farm/cluster): EVC covers your VMs from the Host level: Put your ESX hosts in to maintenance mode one at a time and make a bios setting change, once the entire farm/cluster is changed, you should then be able to enable Enhanced Vmotion Compatibility (EVC), but you must be on ESX 3.5 Update 2 or higher to use this mode. In the Bios, Execute Protection is Intel eXecute Disable (XD) on Intel processors. You’ll need that set to disable for Virtual Center to see your ESX host as EVC compatible. Enhanced VMotion Compatibility (EVC) processor support http://kb.vmware.com/kb/1003212 VMotion CPU Compatibility Requirements for Intel Processors http://kb.vmware.com/kb/1991 EVC and CPU Compatibility FAQ http://kb.vmware.com/kb/1005764 Vmotion info guide: http://www.vmware.com/files/pdf/vmotion_info_guide.pdf Good catch but you actually want that disabled on all of your hosts if you plan on using Enhanced Vmotion Compatibility mode (mixing different CPU steppings or families together, e.g. adding a newer M2 to an existing x3650 farm/cluster):

EVC covers your VMs from the Host level: Put your ESX hosts in to maintenance mode one at a time and make a bios setting change, once the entire farm/cluster is changed, you should then be able to enable Enhanced Vmotion Compatibility (EVC), but you must be on ESX 3.5 Update 2 or higher to use this mode. In the Bios, Execute Protection is Intel eXecute Disable (XD) on Intel processors. You’ll need that set to disable for Virtual Center to see your ESX host as EVC compatible.

Enhanced VMotion Compatibility (EVC) processor support
http://kb.vmware.com/kb/1003212

VMotion CPU Compatibility Requirements for Intel Processors
http://kb.vmware.com/kb/1991

EVC and CPU Compatibility FAQ
http://kb.vmware.com/kb/1005764

Vmotion info guide:
http://www.vmware.com/files/pdf/vmotion_info_guide.pdf

]]> By: JF http://www.sysdigg.com/cannot-vmotion-on-new-ibm-x3650-servers/comment-page-1#comment-566 JF Fri, 07 Aug 2009 12:20:26 +0000 http://www.sysdigg.com/cannot-vmotion-on-new-ibm-x3650-servers#comment-566 I had the same issue today, your tip saved my weekend !!!!!! Thanks a lot !! I had the same issue today, your tip saved my weekend !!!!!!
Thanks a lot !!

]]> By: BK http://www.sysdigg.com/cannot-vmotion-on-new-ibm-x3650-servers/comment-page-1#comment-553 BK Fri, 31 Jul 2009 20:40:02 +0000 http://www.sysdigg.com/cannot-vmotion-on-new-ibm-x3650-servers#comment-553 I had the same issue - this BIOS changed worked for me. Very odd though, as the ESX farm had multiple x3650 machines, all with the same BIOS level and settings - just one server would not allow vmotion to occur. Works now! Thanks! I had the same issue – this BIOS changed worked for me. Very odd though, as the ESX farm had multiple x3650 machines, all with the same BIOS level and settings – just one server would not allow vmotion to occur. Works now!
Thanks!

]]> By: IBM BIOS recommendations for ESX | The VMguy http://www.sysdigg.com/cannot-vmotion-on-new-ibm-x3650-servers/comment-page-1#comment-339 IBM BIOS recommendations for ESX | The VMguy Mon, 05 Jan 2009 18:31:05 +0000 http://www.sysdigg.com/cannot-vmotion-on-new-ibm-x3650-servers#comment-339 [...] Bit in the CPU settings was disabled.  This can cause vMotion to fail as described in this article here .  So you would want to enable the Execute Disable [...] [...] Bit in the CPU settings was disabled.  This can cause vMotion to fail as described in this article here .  So you would want to enable the Execute Disable [...]

]]>