Host CPU is Incompatible - car Upgrade to vSPhere 4

Similar Questions

• VMotion fails with «Host CPU is incompatible...» »

  After setting our vCenter 4 / environment laboratory of ESX 4 with two hosts ESX 4, I added two of our ESX 3.5 hosts in vCenter 4 managed environment. These 3.5 hosts had 10 Windows 2003 EE 64-bit Server identical virtual machines, running on them. I then used storage vMotion (migration) to move all ten VMs over a LUN share by the ESX 4 hosts and migrate them while they are now running on the ESX 4 hosts.  They came over the fine. Activated fine. Ran very well. vMotioned back between the two ESX 4 hosts fine.

  I then put off 5 of the 10 computers virtual and enhanced their virtual hardware version 4 to version 7. I have them fed up.

  I have also built several new virtual machines on the host ESX 4 from scratch using the same process and the same image that I used to create virtual machines hosted on ESX 3.5 hosts. So far so good.  Can I vMotion between all 5 virtual machines that are still at version 4 guests two ESX 4 and I can vMotion new computers virtual 7 built on ESX4 host, but if I try to vMotion of 5 virtual machines have been upgraded to version 7, I get the message below.

  Host CPU is incomaptible with the requirements of the virtual machine to CPUID level 0 x 1 register 'cex '.
  Bits of the host: 0000:0000:0000:0000:0010:0000:0001
  Required: 1000:0000:0000:000 x: x 10 xx10:0: xxx0:x 001
  Inconsistency detected for these features:
  * General incompatibilities; see section 1993 of possible solutions.

  I read the KB article referenced, but this is to overcome the problems with fast vMotioning between levels or different processor types. These two hosts ESX 4 (10-esx-mp and mp-esx-11) are identical DL580 G5. It's only the improved VMs that fail to migrate.

  I stop each host ESX 4, restarted in the BIOS and set the option of VT processor on 'disable', of booted up the box, let it come completely up, then again, rebooted the box of ebb in BIOS and by setting the option VT back on 'enable '. It's not helping.

  Someone else has seen this?

  If you have identical CPU, then check the configuration of virtual machine (in the .vmx file) to see if there is an old CPUID mask value and simply remove them.

  Then again turn on the virtual machine.

  See also:

  http://KB.VMware.com/kb/1993

  André

• Host CPU is incompatible. ? !

  Ok

  I did a lot of research this upward and have found ways to correct this and comments, the problem is that I have three DL580 G5s that are entirely similar,.

  Same memory, CPU, even network cards, same level of BIOS.

  But when I try to migrate a guest to the second of the three I get a title and a discrepancy detected above these features: * NX/DX and so on.

  I have two clusters (first is DL380 G5s x 6 is second of the G5s DL580 x 3), I don't have this problem with the first group, can I VMotion a guest in the first group at will (in the first cluster only), I just tried to VMotion a guest from the first to the second cluster (power off) without problem.

  Now what I find is the guest of the first cluster can be moved to ONE of the hosts of the second cluster No. errors!

  Anyone have any ideas of what I'm againest?

  Thank you!!

  What processors model you are using? you have activated EVC on clusters? Please take a look at the articles below:

  VCA:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1003212

  forests of nx/HB masking:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1993

  HTH...

• VSphere Essentials Plus upgrade to vSphere with operations management standard

  Hello

  We currently have vSphere Essentials more running on 3 hosts, and we want to upgrade to vSphere with the Standard edition of management operations (with vCenter Server) using the kit of acceleration.

  Please confirm if it takes to change the key of any upgrade of software or installation or license only it will take?

  Waiting for the answer. Thank you

  Sound just change of license keys. Binaries are all of same for all versions, just the keys toggle features.

  -If you have found my reply useful/correct please close the message by checking the answer.

• checks before the upgrade to vSphere

  Hi all

  my whish is upgraded to esx 3.5 hosts I already to vSphere.

  I checked HCL and it seemed to be possible, but, not being only not sure about x 64 CPU tried to build 1 x 64-bit OS on each host and I received a message that it was not possible.

  So I guess I can't upgrade to vSphere.

  Am I wrong? or I can do other than buying other servers...

  I am running DL380 G5 and DELL poweredge 6850

  THX in advance,

  Daniele

  Daniele,

  It looks like there DELL shipped this server with several different processors.

  The only supported are those listed in the VMware HCL for DELL PowerEdge 6850

  It goes the same for HP DL380 G5

  André

• Upgrade infrastructure vSphere Essentials Plus 5.0

  I need to upgrade an infrastructure of VMware vSphere Essentials Plus 5.0 2 nodes of ESXi 5.0 and Windows server 2008 R2 based vCenter (virtual).

  I want to upgrade to vSphere 5.5 U2.

  Can I use the standard VMware CD to upgrade the host or vCenter or should I use Essentials more specific CD?

  Based on what I saw on KB 2057795 I should update the vCenter first, ESXi nodes later.

  Can I upgrade from 5.0 to 5.5 U2 or should I perform any intermediate task?

  Is the update process, I need to run described anywhere?

  Concerning

  Marius

  Can I use the standard VMware CD to upgrade the host or vCenter or should I use Essentials more specific CD?

  There is no difference between the installation media... the same ISO can be used for all editions of vSphere/vCenter.

  Based on what I saw on KB 2057795 I should update the vCenter first, ESXi nodes later.

  Yes, it is in order, all first the vCenter Server and vSphere ESXi hosts.

  Can I upgrade from 5.0 to 5.5 U2 or should I perform any intermediate task?

  You can go directly to version 5.5 Update 2, but for vSphere, ESXi hosts don't forget to check the HCL first just to make sure that your host supports version 5.5 Update 2.

  Is the update process, I need to run described anywhere?

  The following KB articles will guide you:

  VMware KB: Upgrading recommended vcenter Server 5.5

  VMware KB: Installation or upgrade to ESXi 5.5 best practices

• "No connection to the server of VR: does not not." after upgrade to vSphere 5.5

  As part of the upgrade to vSphere 5.1 to 5.5 along http://kb.vmware.com/kb/2057795 I've updated vSphere replication to 5.5.0.0 build 1309877. All rehearsals continued well then. I only add the new vCenter replication and it stopped for the old.

  After the migration of all VM including device just RV improved another 5.5 ESXi host I upgraded from original host and migrated the back of some VM. I noticed that only this VM is replicated again then. All other zeroes had "no connection to the server VR: does not not." and "Violation of RPO" messages (including RVS). If I migrate the original replication host virtual computer is restored. If I migrate to another connection from host to the server of VR is lost again - no matter what a host running VR.

  Any idea, please?

  Yes, it's possible, but I just wanted to rule out any more simple explanations first. I was worried especially when you said the VR server could not ping itself, but perhaps I misinterpreted what you were saying.

  In all cases, you can verify if this is your problem by looking for a line like this in the esx.conf of the hosts that you upgraded:

  / NET/vmkernelnic/Child [0001] / tags/4 = 'true '.

  If so, remove the line in the esx.conf and restart the host. Then, once the host is back, check that the network adapter assigned to the vmkernel is an accessible IP address.

  In my view, that the part "child [0001]" may be different on certain configurations if you do not find the exact line I've specified above, check around the lines part of [another] child.

• Upgrade to vSphere client 5.1 U1 but using vCenter/ESXi 5.1 (not U1)

  So I saw this recommendation from VMware:

  -----------

  The sequence for vSphere 5.1 update update 1 and their compatible VMware product (2037630)

  If you are using vSphere Client in your environment, it is recommended that you upgrade the vSphere Client to version 5.1 update 1.

  -----------

  
  

  My ESXi servers are still 5.1 (build 799733, some to the build 1021289), and my vCenter Server 5.1.0 build 947673. I should be able to install this patch for the client vSphere on my workstation without problem. It is recommended that VMware, right? That the client must be upgraded, regardless of the version of the host?

  
  

  (I still don't think that the web client (again), so I want to continue to use the vSphere client, if and when I can)

  
  

  Thank you

  
  

  the client is backward compatible, you should be fine

• Cannot use 'lab1' host because the host CPU is not compatible with the judgment of the virtual machine suspend state.

  I see that this error was mailed here, but can't seem to find a position with a resolution.

  We use Lab Manager 4.0.4 and just upgraded the hosts in our laboratory.  Before updating to ESXi 4.1 ESX 4.0 u1, we cancelled all VMs in all configurations.  There is none who were suspended, they were all turned off.  We have improved vcenter 4.0 to 4.1 as well.  We moved from a dell poweredge 1950 with two quad core intel L5410 to a r610 with two quad core intel processor E5506.

  When I try to turn on some of the lab configurations (our VM models all work fine), I get this error:

  • Cannot use 'lab1' host because the host CPU is not compatible with the judgment of the virtual machine suspend state.

  I threw the State for the lab configuration (even if it was turned off and cancelled) and still get this message.  I guess the processor architecture of these chips is quite similar, and both are Intel.

  If I go into this directory of Manager of laboratory inside the data store for one of these virtual machines that does not light and add to the inventory, he turned and starts fine on my server esxi 4.1.  So how do Lab Manager to get account it's well deploy and start it?

  Hey billk.

  Although not supported completely, you can solve it by going to the SQL of Lab Manager database.  Make sure that you back up your database before you do anything like that.

  Open the table "fsdir" and corresponds to the dir_id with the id Lab Manager VM.  Once you find the relevant line, change suspend_proctype_id to null (Zero-Ctrl).  You can do this while Lab Manager is still running.

  The results can be unstable (i.e. Windows can crash if it was a drastic change of CPU), but at least you look at a hard reset.  The bat reset certainly not being able to return to the previous state.

  Also note that while Lab Manager does not include CVS, if you activated, your virtual machines still work in CVS mode.  If you have a mixture of heterogenious of hosts in a cluster for Lab Manager, you can see this question pop up a lot.  There is absolutely nothing wrong with take back the virtual machine because of the VCA, but Lab Manager thinks otherwise and prevents it.

• Host CPU is not compatible

  Recently, I have rebuilt my VM relax from U 1 4.0 ESX to ESXi 4.1 with the latest updates. I have a 3 hosts who are identical in specs, all three are ML370 G5 HP servers. I have a Virtual Machine that gives me headaches. I can not migrate from the last host, I created. I get the following error message:

  Host CPU is not compatible with the requirements of the virtual machine to CPUID level 0 x 1 'ecx' register

  Bits of the host: 0000:0100:0000:1000:0010:0000:0001

  Required: x 000: x 000: 0000:10xx:xxx0:xx1x:xxxx:x 001

  Inconsistency detected for these features:

  * General incompatibilities

  If possible, use an active cluster with vMotion compatibility (EVC) Enhanced; See article 1003212. In the absence of EVC, see article 1993.

  The weird thing is that I can move to two other guests very well. I have all hosts patches at the same level, VMtools upgraded the virtual machine. I have no problem moving any other VM to this host. I'm going to create a cluster, but I want to assure that I can move all the VMS to all guests, first of all. Any suggestions would be greatly appreciated.

  Thank you

  Pete

  If you can try this

  1. Turn off the virtual machine.
  2. Click on the link change the settings of the virtual machine.
  3. Click the Options tab.
  4. Select mask CPUID under Advanced.
  5. Click Advanced.
  6. Click on reset default.
  7. Click OK.
  8. Click OK again.
  9. Turn on the virtual machine and migrate.

  .. .or you can just try and it turns off, remove the inventory, browse the data store, add to the inventory on the other host.  Then see if you can vMotion.

• Upgrade to VSphere, from ESX3.5 to 4.1

  I wanted to see if anyone out there has had experiences that you want to share in what concerns the upgrade to vsphere esx3.5. Traps, precautions and things you would have done differently in hindsight. We are in the process of upgrading and wanted to have an idea of what could be a problem and what to be aware of.  We do not have a test environment that I can try this upgrade, then it is an upgrade of the production and I'm very cautious and careful.

  Thank you

  Shawn Smith

  I just finished upgrading a cluster of very large from ESX 3.5 to ESXi 4.1. First step was to upgrade vCenter, who has been somewhat complicated by the fact that I had to go from a 32-bit host to a new 64-bit host. Detach the database from a stand-alone server to SQL 2005, then to attach to a host of cluster SQL 2008 has been an easy victory, as he provided us with resilient layer of database. Then I let vCenter 4.1 run with the host ESX 3.5 for a week or two, to prove the cross-compatibility.

  I chose to do a clean install of ESXi 4.1 on each host. It could have been much longer than other methods, but I felt it was the best in the long term. This involved: removing host ESX 3.5 of the cluster, install ESXi 4.1 and all the drivers and the HP management bundles and join this new ESXi 4.1 host in the cluster. Using vMotion, I was able to do the project with absolutely no downtime!

  Finally, I have updated versions of material to version 7 and put to update VMware tools for all the virtual machines in a controlled manner which corresponded with our routine systems maintenance windows. I'm very uncomfortable with the scenario and happy to help someone who needs guidance.

  -Omid bougouin

• ESX 3.5 upgrade to vSphere using Activation of Windows

  I'm trying to upgrade ESX 3.5 a customer to vSphere.   I have a single license of Windows Server 2003 Enterprise Edition and spin 4 VMS (clones) on a single ESX host.   (a real activation and 3 clones of the Windows VM already active)

  After that I've upgraded to vSphere each Windows VM will require reactivation of Windows.

  Can someone tell me what to expect regarding regarding the reactivation work or I will have to call Microsoft.  Microsoft will allow me to reactivate all 4 VM?  Is it the fact that the VM is clones impact of the process of reactivation with Microsoft?

  Thank you.

  Hello

  If Windows in the VM is already activated, it should not be necessary to "reactivate" once you upgrade to vSphere. I do updates all the time and have never had to reactivate windows.

  Best regards
  Edward L. Haletky VMware communities user moderator, VMware vExpert 2009, 2010

  Now available: url = http://www.astroarch.com/wiki/index.php/VMware_Virtual_Infrastructure_Security'VMware vSphere (TM) and Virtual Infrastructure Security' [/ URL]

  Also available url = http://www.astroarch.com/wiki/index.php/VMWare_ESX_Server_in_the_Enterprise"VMWare ESX Server in the enterprise" [url]

  Blogs: url = http://www.virtualizationpractice.comvirtualization practice [/ URL] | URL = http://www.astroarch.com/blog Blue Gears [url] | URL = http://itknowledgeexchange.techtarget.com/virtualization-pro/ TechTarget [url] | URL = http://www.networkworld.com/community/haletky Global network [url]

  Podcast: url = http://www.astroarch.com/wiki/index.php/Virtualization_Security_Round_Table_Podcastvirtualization security Table round Podcast [url] | Twitter: url = http://www.twitter.com/TexiwillTexiwll [/ URL]

• Upgrade to vSphere VI3

  Hello Experts!

  I'm currnetly running VI3 environment, and I want to upgrade to vSphere.

  I have a few new servers I want to install vSphere on also.

  Can I upgrade my server vCenter for sphere, then install vSphere on my new servers and still manage my pre-existing VI3 esx boxes using the new vCenter server running vSphere?

  Thanks in advance!

  I would create a new vCenter Server (VM) to manage all hosts. You need to keep your current online license Virtual Center server until you're completely out of VI3. Once this is done, you can retire the old virtual server Center Server and license.

  You can manage the VI3 hosts vSphere and the vcenter Server.

  What version of ESX do you currently use?

  Once you have the former hosts managed by the vCenter Server server, you can use the update/update Update Manager to vSphere/ESX/ESXi 4...

  VMware VCP4

  Review the allocation of points for "useful" or "right" answers.

• The upgrade to vSphere + SQL Express to SQL 2005 + new vCenter Server

  Hello world

  It's the scénarion that I have today:

  A node just two HA/DRS cluster with vCenter 2.5 update 4 and two esx 3.5 update 4.

  The environment has increased enough to move from SQL Express to SQL 2005 standard. In the process, I want to upgrade the environment to vSphere and the vCenter move another box.

  I'm quite familiar with the process of vSphere upgrade but I donít know how to move the vCenter to another machine AND I do not know how to go from Express to the standard version of SQL in the process. (I have a SQL machine ready for use)

  I do not know how to handle all the changes here, I thought it would be nice to all move to the new machine and DB so that I could continue with the upgrade to vSphere, if this has meaning or not, I'm waiting for your ideas.

  I hope someone will give me some guidance on moving from SQL Express to SQL and how to move vCenter to another server (of course with a different server name and IP address)

  Thanks in advance for your support.

  I just did something very similar a few Sundays ago and it was really easy.  Refer to the section of the Upgrade Guide that talks about upgrading to vCenter on another Machine... (starts at p. 49).  We went from SQL 2003 32 bits on 32-bit Windows 2003 to SQL 2005 64-bit on Windows 2008 R2 64-bit.  Both are running as VMs - vCenter 2.5 is still there only as a license server - until I get all my hosts upgraded.

• intend to upgrade to vsphere 4.0 and need help

  someone has upgraded to vphere 4 again and suggestions or the steps necessary to succeed.  Thanks in advance.

  What are the types of hosts will you update? In most cases, you can use VMware Update Manager for ESX4i and vSphere 4.0, because you can't make a room upgrade with vSphere 4.0 CD. If your environment is lower, then 10 hosts, then use Host Update Utility to perform the upgrade, which is fairly easy or install base plug-in and configured VUM and sanitize it massively if you wish and plan accordingly with VMotion feature so that you have no downtime or need to use Storage VMotion, if you need to migrate between stores.

  Once you have upgraded your hosts all vSphere 4.0, you have an option to clean the ESX 3.5/Boot and files in directory existing using the 'cleaning-esx3' service console command. If you like not vSphere 4.0 performance for some reasons, you can restore to the State ESX 3.x as well by using the command line "rollback-to-esx3' which will reconfigure your bootloader then you can manually delete the service console vmdk file.

  I would start by looking at the guide to documentation how do more efficiently with planning in advance and prepare here http://www.vmware.com/support/pubs/vs_pages/vsp_pubs_esxi40_i_vc40.html

  Steps to follow:

  1 back up your database

  2 download the license file and the upgrade to vCenter 4.0 Server and components, point to existing ODBC connection to keep data of perf or clean install.

  3. switch to level the esx host using component VUM

  4. upgrade tools vmware and vmware hardware at level 7

  There is a video online of 4 steps casting presented by VMware its pretty good and solid foundation.

  Good luck!

  If you found this information useful, please consider awarding points to 'Correct' or 'useful '. Thank you!!!

  Kind regards

  Stefan Nguyen

  VMware vExpert 2009

  iGeek Systems Inc.

  VMware, Citrix, Microsoft Consultant