Page 2 of 2

Re: Nested virtualization: Success stories (and failures)

PostPosted: 18. Jan 2019, 01:33
by socratis
Friis wrote:I updated Virtualbox to 6.0.2 and felt like I didn't get as far as I used to.
Not sure what I'm seeing here, and not sure why both the logs. You included the Win10 host logs, in which I see no errors...

Friis wrote:in Unraid I have run activate nested virtualization script
Not sure what that is as well...

Re: Nested virtualization: Success stories (and failures)

PostPosted: 19. Jan 2019, 18:07
by Friis
socratis wrote:Not sure what I'm seeing here, and not sure why both the logs. You included the Win10 host logs, in which I see no errors...

Then I don't know what logs needs to be added. VBoxHardening.log? windows log?

socratis wrote:Not sure what that is as well...

Unraid is my host OS, Windows 10 is my VM, windows 7 is my nested VM.

Re: Nested virtualization: Success stories (and failures)

PostPosted: 19. Jan 2019, 19:21
by socratis
@Friis
The way that I understand nested virtualization is VirtualBox-inside-VirtualBox. Is there a VirtualBox for Unraid OS? What's Unraid based on? And are you trying to run?

    Unraid (version?) as host
      » VirtualBox (version?)
        » Win10 (flavor/version?) as guest
          » VirtualBox (version?)
            » Win7 (flavor/version?) as nested guest

Re: Nested virtualization: Success stories (and failures)

PostPosted: 20. Jan 2019, 03:09
by Friis
Unraid, uses KVM virtualization.
Unraid (Version 6.6.6) host
Windows 10 (pro 1803) as guest
VirtualBox (6.0.0 - works best)
Windows 7 (Enterprise? I think, been some time since I have been in it) as nested guest

Unraid support GPU passthrough (Type 1 virtualization I think)

Virtualbox 6.0.0 I get to the point where windows asks me if I would like to start normally or run repair. after click run normally, the VM freezes. (6.0.2 I don't get that option)
Unraid has Hyper-V activated for Windows 10 VM, which also seem to be what is the best paravirtualization option in Virtualbox.

Re: Nested virtualization: Success stories (and failures)

PostPosted: 20. Jan 2019, 12:53
by socratis
Pending an answer from the developers, I (personally) am going to be looking initially, only in the following scenarios:
socratis wrote:The way that I understand nested virtualization is VirtualBox-inside-VirtualBox.

I wouldn't know where/what to start looking for in a KVM log. :o
And I don't plan to either, because I can't run KVM...

Re: Nested virtualization: Success stories (and failures)

PostPosted: 20. Jan 2019, 15:47
by Tom B
Log file:

Virtualbox: 6.0.2
Host: Arch Linux
Guest: Windows 10 with Nested virtualization enabled
CPU: AMD Threadripper 1950x


Crashes during windows boot.

Re: Nested virtualization: Success stories (and failures)

PostPosted: 20. Mar 2019, 23:24
by 0xs4ni
>Host: Ubuntu Bionic 18.04.2
>Host VBox: 6.0.4
-> Guest: Ubuntu Bionic 18.04.1
-> Guest Vbox: 6.0.4
--> Nested Guest: Boot2Docker 18.09.3

I was going through the Docker tutorial for swarms while following along in a VM then ran into an error code about the bios needing to support "VT-x/AMD-V" despite the box already being checked and found the Other Thread, realized my host vbox didn't have the update. After purging the previous installation and its related files and reinstalling+acquiring the expansion pack I was able to get it running as expected.

Not sure yet how Boot2Docker is configured by default but it took a sec to setup, these aren't things relating to virtualbox itself and more-so how the setup of a nested vm works through Docker that simply utilizes Virtualbox in the process. Happy to see this implemented, thank you for the hard work!

Initially I just removed the previous installation, but upon receiving an error code relating to drivers I circled back with

$ apt-get purge virtualbox-5.2
$ dpkg -P virtualbox-5.2
$ apt-get autoremove
$ reboot

then install the Expansion Pack, no more errors, nested virtualization achieved.

The host is using an AMD A12 processor.

Re: Nested virtualization: Success stories (and failures)

PostPosted: 20. Mar 2019, 23:51
by socratis
0xs4ni wrote:then install the Expansion Pack, no more errors, nested virtualization achieved.
Thanks for sharing your success story! 8)

Would you mind doing a couple of things?
  1. Start the 1st VM,
  2. start the 2nd VM,
  3. shutdown the 2nd VM,
  4. grab the VBox.log of the 2nd VM,
  5. shutdown the 1st VM,
  6. grab the VBox.log of the 1st VM,
  7. ZIP both logs and attach them here
I'd like to see how a log within a log looks like... ;)

Re: Nested virtualization, VT-x/AMD-V in the guest: Success stories (and failures)

PostPosted: 1. Jul 2019, 10:52
by NeilZhang
First thanks a lot for such wonderful feature!
My issue is about ESXi 6.7.
I installed ESXi 6.7 on VirtualBox 6.0.8 (amd64), then created a 64bit Linux guest on the ESXi.
I could created it without any issue so I thought the Nested virtualization did work and I also confirmed this point through below ESXi command.
[root@vCenter:~] esxcfg-info -w | grep "HV Support"
|----HV Support...............................................3

While when I tried to start the guest I would get error 'This host does not support "AMD RVI" hardware assisted MMU virtualization' and failed.

I did similar things with VMware workstation and ESXi then also created a 64bit LInux guest on the ESXi, and it worked well.

So it seems VirtualBox could not expose AMD-RVI to the ESXi guest, right?

Re: Nested virtualization, VT-x/AMD-V in the guest: Success stories (and failures)

PostPosted: 8. Aug 2019, 13:13
by pedro4444
great