Host CPU incompatible when booting 64bit Virtual Machine

July 31, 2008 by John Tran · 13 Comments 

If you have created a Windows 64bit virtual machine you need to ensure that you have enabled Virtualisation Technology in the host system BIOS. This feature is disabled by default so needs to be manually enabled.

If it is not enabled you will get the following error when you power on the virtual machine.

The cpu of the host is incompatible with the cpu feature requirement of the virtual machine; problem detected at cpu id level 0×80000001 regsiter edx.


About John Tran

Comments

13 Responses to “Host CPU incompatible when booting 64bit Virtual Machine”
  1. Roger Zan says:

    I figured out the solution. You have to go to the CPUID mask for the VM Advanced Options and change the 0×800000001 register edx to

    –1- —- —- —- —- —- —- —-

    By default it’s set to:

    —- —- —1 —- —- —- —- —-

    The dashes are 0 bits.

    Once you make this change, you should be able to start up the x64 VM without a problem. It’s stupid that this needs to be done, but until VMWare figures out a way to correct this, I guess this tweak will have to do.

  2. Daniel Ruiz says:

    You are the man… thanks for posting. I was tearing out my hair

    I had to change it from:
    —- —- —H —- —- —- —- —-

    to:
    –1- —- —- —- —- —- —- —-

    on ESX 3.5

    Daniel

  3. sumeet says:

    Thanks for posting this.

  4. Carter says:

    Thanks! This did the trick for me. :-)

  5. LodgeCat says:

    Sure glad you figured this out…Nice Work!

  6. Andrew says:

    Can someone help me I am new with ESX and I found as You posted 0×800000001 register edx

    and what should I do with that:

    RRTR HRRR RRRH RRRR RRRR XRRR RRRR RRRR

    What should i put in there?

    Thx for help

  7. ilissan says:

    Thanks! Great works like a charm!

  8. Giuliano says:

    Thanks a lot! it works, i’m very happy!!!!!!!!

  9. Gary Singh says:

    It worked…perhaps the error message itself indicates the bits. so make sure when you set 1 as bit it should be replace 3 from the left. See the error my message very closely.

    BUT it is good solution to put. I guess VMware has fixed in ESX 4.1

  10. Cordova says:

    Thanks! And yes the error message in 4.1 actually tells you what is required so if I had payed attention I would have saved a few hairs or two.

  11. shah says:

    i am so thankful for that great work pls keep it up!!!!!

  12. Jeevan says:

    Thanks Daniel Ruiz and Roger Zan your trick helped me .
    i still have 1 issue . i am geting “starting windows” when i am install win2008 R2, after that screen VM igs shutting down.

  13. Calvin says:

    wow great post would have been in a lot of trouble otherwise.
    using esx3.5u1 here.
    In response to Andrew’s post (i’m sure he found the answer anyway), i used:
    RR1R RRRR RRRR RRRR RRRR XRRR RRRR RRRR

    just note that it seems to be common practice to restart vcenter services after changing these settings. worked for me.

Speak Your Mind

Tell us what you're thinking...
and oh, if you want a pic to show with your comment, go get a gravatar!