Virtualbox can be nested in a Hyper-V VM but VMware cannot

[mfelker]

Host:  Windows 8

Hyper-V role installed

Windows Server 2012 Hyper-V VM

There is now  some fundemental difference between Virtualbox and VMware in this scenario.

Virtualbox and Oracle extensions not only install in a  Hyper-V VM but can create a VM with connectivity, .  It is known that VMware won't install in a Hyper-V and immediately says so.

What is the difference here if  Virtualbox is the same type of virtualization as VMware and quite different from Hyper-V?   I didn't expect this new Virtualbox  capability and   I don't expect that VMware engioneers will modify their code to allow this nested behavior  - or even can without changing the code base.

Virtualbox 4.24 appears to be capable of host-guest and guest-host cut  and  paste now although I haven't yet ltested this.

Intersting ...

[admin]

If your host has EPT or RVI, you can make this work with some difficulty.

1. Remove the Hyper-V role.

2. Install Workstation.

3. Add the Hyper-V role.

4. Add the following configuration option to C:\ProgramData\VMWare\VMware Workstation\config.ini:

vmx.allowNested = TRUE

It's not a configuration that we intend to support.

Note that if your host does not have EPT or RVI, this is a good way to crash the management OS.

[admin]

Oops.  I misread your post.  Coercing the Workstation installer to let you install in a Hyper-V guest may be a little bit trickier, though I'm sure Workstation would run fine once you got past that hurdle.

[admin]

You could probably install Workstation in a Windows Server 2012 Workstation VM, convert the vmdk to a vhd, and then attach the vhd to your Windows Server 2012 Hyper-V VM.

[mfelker]

I will try that when I get a chance for sure because  I will uninsntall the Hyper-V role and install VMware WS 9.  One of the main reasons to instgall WS for me is the WSX program which is working great in Fedora 18 as well as Windows 7. Although it seems I can switch back and forth between Hyper-V and VMware (but not run the at the same time - it is  easier for lme just to  installl one virtualization product and re-install the other.  The number of reboots is not  question since this is an experimiental machine and I have a GA-990FXA-UD3 motherboard which is extremel;y reliable and durable  and has a dual BIOS.

[mfelker]

I'll try this also again because the machine is experimental.  I have an HP Proliant server which definitely is not experimental and can only run WS.

Thank you for all the .vmx configuration lines you have provided on virtualization

[mfelker]

It also worked fine installing an Ubuntu Server 12.04 LTS  in a Virtualbox which ran directly on theHyper-V enabled  host.  I didn't get a chance to see if it could work at the same time as a Hyper-V machinie - but that is not releavant as far as I'm concerned.  The guest had to be 32-bits however.  Running VB on the host is more interestinig than running it in a Virtual Machine of any kind  since that is mostly a stunt  - performance wise at least  (but could have a liittle  value in workinig with Hyper-V in a VMware environment - but this requires several of the workarounds you provided).  Too bad VMware is not interested in making its product compatible with Hyper-V.  I'm sure it could since Virtualbox works in the Hyper-V environment - it almsot certainly is not a technical problelm - except for the fact that you guys don't want to modify the codebas and of course their are markeing and legal reasons - maybe involving Microsoft. .

[admin]

Does VirtualBox work well within the Hyper-V environment (from a performance standpoint), or is that "just a stunt" as well?

[mfelker]

Yes.  It does work quite well.  This is much less of stunt than running it  inside a Hyper-V VM.  As always it depends on the amount of RAM you give the Virtutalbox VM.  I haive 24 GB of physical memory.  One does have to be a little careful about the display however.  In some guests I tried there was noi a toolbar  I could access although clearly the desktop was there (update notifications appeared etc). If I install Ubuntu server and then do an aptitude install ubuntu-gnome-desktop and kde-full  the desktop looks qutie normal.  As I said I think only 32-bit guests will be supported by VB in the Hyper-V host environment. I installed the VirtualBox guest additions as well after aptitude install build-essential I have not yet created any Virtual Machines in a Windows 8 host environment with no Hyper role  - but I've never had a problem with that.  As a sidenote I have not had any problems withk installing or uninstalling Ws 9 in Windows or Linux.    From past experience with qemu performance there will lag. badly

VMware howeve rhas one great feature that neither Hyper-V or VB has - the WSX program.  The more I use it the more I'm impressed.