VirtualBox INSIDE HyperV

[marked]

I am using Server 2012 and have set up Hyper-V.

I have a Hyper-V guest containing Server 2003. I want to put my existing VirtualBox VMs INSIDE the Server 2003 VM. One has an ftp server set up and another has a mail server.

VirtualBox installed successfully inside the Server 2003 VM. However the network bridge option failed to work. NAT worked ok and the transfer rate using a shared folder was not bad (15 Mb/s). So I tried port forwarding for ftp however the transfer rate was very poor (few kb/s) and ftp usually crashed authenticating.

Is there a way to get the bridge to work or is it clashing with the hyper-v 'host' and no hope?

Also any hope in improving ftp port forwarding?

Many thanks,
Mark

[Perryg]

The best you can hope for is trial and error. Nested virtualization is not supported.

[BillG]

The basic problem is that, once Hyper-V is installed, the host OS is running on top of the hypervisor, not directly on the hardware - only the hypervisor has direct contact with the physical devices. I think that explains why, even though the vm will run, network performance is flaky.

[marked]

The basic problem is that, once Hyper-V is installed, the host OS is running on top of the hypervisor, not directly on the hardware - only the hypervisor has direct contact with the physical devices. I think that explains why, even though the vm will run, network performance is flaky.

My main problem is regarding network bridging. VB doesn't seem to be able to bridge itself with the 'hyper-v' virtual network adapter that is present in the host.

It doesn't report an error, rather guest network reports as 'limited', without the expected IP and external network access.