Hi everyone


Found a mega show stopper here
I MUST have VMware available on a laptop / workstation.

If you enable HYPER-V on W8 then you can't start VMware

I know if you use hyper-v you'll probably want it on a server - but on a WORKSTATION DEVELOPMENT OS I think people will be testing / developing on all sorts of platforms.

I'm quite happy to run Hyper-V as a stand alone Server but the feature I thought MS was bringing to the table was to enable this on a WORKSTATION giving benefits of being able to use the development facilities of a workstation instead of the more limited development possibilities on a server which isn't really suitable to be used as a workstation in most cases.



enc image

Cheers
jimbo

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.

Do you think that MSFT is going to fix this?

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.

Originally Posted by ccatlett1984

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

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.

Cheers
jimbo