I think you are going to find this in any case where you try to run more than one HV at a time. This is also why you can't enable W8's HV inside a W8 VM.
The HV's aren't smart so by allowing more than one you could have device conflicts.
Its not "fixable", when you enable Hyper-V it changes the way windows on the host loads, it loads the hyper-v hypervisor and your host OS is actually running on top of that hypervisor. It goes without saying that you can't have multiple hypervisors layered.
ccatlett1984 said:
Its not "fixable", when you enable Hyper-V it changes the way windows on the host loads, it loads the hyper-v hypervisor and your host OS is actually running on top of that hypervisor. It goes without saying that you can't have multiple hypervisors layered.
ccatlett1984 said:
Its not "fixable", when you enable Hyper-V it changes the way windows on the host loads, it loads the hyper-v hypervisor and your host OS is actually running on top of that hypervisor. It goes without saying that you can't have multiple hypervisors layered.
Unless of course you run vmware wks 8 or esx5, in which case you can nest hyper-v inside it as well as 64bit guests etc..
Hopefully hyper-v comes to the party in a similar fashion at some point.. So clearly the model of nested hypervisors does work and is possible..
Nesting Hyper-V with VMware Workstation 8 and ESXi 5 | Veeam Software Official Blog
www.veeam.com
Hi there
This is the OTHER WAY AROUND -- I don't want to run Hyper-V as a Virtual machine -- I was hoping to run HYPER-V on a HOST and run VM's using the HYPER-V super/ hyper visor.
Running a VM is fine -- BUT :
Since the HOST OS is actually a Windows machine it *Should* be able to run vmware workstation on it as a "standard" application on it too. Nesting vm's is not a very good idea unless you are simply testing the environment.
Latest Threads & replies: 
