Before you read any further, as Dane pointed out, you can install Hyper-V on Microsoft Windows 8 Consumer Preview, but after rebooting you will be presented by a “blue screen”, because a HAL_Memory_Allocation was thrown. This is broken since the beta build. Let’s hope they fix this in the RTM.

 

Meet the power of |”Intel VT-x/EPT”. Normally when you want to install Hyper-V on Windows 8 inside VMware Workstation 8 you will get the following message:

 

Hyper-V cannot be installed: A hypervisor is already running.

 

image

 

Shutdown the machine and edit the Virtual Machine Settings > Hardware > Processors > check the “Virtualize Intel VT-x/EPT”:

 

image

 

One more thing you should do, is edit the vmx file of the Windows 8 VMware virtual machine and add the setting  “hypervisor.cpuid.v0 = “FALSE”, as described here: http://www.veeam.com/blog/nesting-hyper-v-with-vmware-workstation-8-and-esxi-5.html

 

Now you can boot the Windows 8 VMware virtual machine and add install Hyper-V.

Go to Control Panel > Programs and Features > Turn Windows features on or off >

image

Now you will get the message: “Provides the services that you can use to create and manage virtual machines and their resources”.

image

 

 

 

More information can be found, here: http://virtualizedgeek.com/2011/09/16/nested-win8-hyperv/

10 Comments

  1. Thanks for the post Roel! I’m not sure if you’ve checked out the new codenamed Server “8” Beta that was released the same time as the 8 Consumer Preview, but apparently they’ve broken this ability for the server OS build. I know from personal experience that with the Server 8 Dev Preview, you could nest Hyper-V in VMware Workstation. As of the beta release, you no longer can nest Hyper-V Server in VMware workstation…Throws as HAL_Memory_Allocation and vcpu-0: Not implemented error. Kind of strange.
    Let me know if you have a chance to test this out. Thanks!
    Dane

  2. There is a solution to getting Windows 8 Beta (build 6250) that came out Feb/2012 to work as a HyperV host nested within VMware workstation. In addition to having the
    hypervisor.cpuid.v0 = “FALSE”
    in the VMX file, all add the line
    mce.enable = TRUE
    to your VMX file. With these 2 lines added to your VMX file, you no longer get the HAL_Memory_Allocation error, HyperV boots up fine and works. Working on 2 nested systems now…
    (note: I read this note on a VMware Community page, although it was unclear whether the note was referring to Win8 Beta, but I tried it and it worked (http://communities.vmware.com/docs/DOC-8970))

    Rand
  3. Rand’s Comment worked. was able to stand up the beta no problems.

    notes:
    added following 2 lines to bottom of .vmx
    hypervisor.cpuid.v0 = “FALSE”
    mce.enable = TRUE

    changed quotes around false to regular quotes

    Eddie
  4. Pingback: vNiklas Virtualization blog » Windows Server 2012 (8 beta) Hyper-V enabled inside a VMware Fusion VM

  5. Pingback: Running Windows Phone 8 Emulator within VMware Virtual Machine | JJ Bussert

  6. Hi,

    Please help me!! I am getting the same error when i tried to run windows phone 8.1 emulator inside windows 8.1 virtual machine… Please help me with this issue

    Saikiran

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.