Nested virtualization with VirtualBox OSE 6.1.8, any success?

[Sebastian Strollo]

Hi

I’m running 12.2-RELEASE-p4 (on an Intel i7-10710U cpu w 64G RAM) as the host OS and using virtualbox-ose-nox11-6.1.18 (from pkg).

I have a guest VM that runs Ubuntu 20.04, and for some testing and development I need it to be able to run KVM, hence I need “nested virtualization”. Has anyone had any luck with the "--nested-hw-virt on” option?

I’m not having any luck at all, if I try to enable it then startup of my VM just hangs, I get the following error in VBoxSVC.log (which I think is the relevant one, the whole log is attached - I suspect the disk that it can’t close is just a result of it shutting down even though it comes before in the log)


  00:54:00.390457 Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={d0a0163f-e254-4e5b-a1f2-011cf991c38d} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0


And looking for that id in xpti.dat I find “IVirtualBox”:


  % grep d0a0163f-e254-4e5b-a1f2-011cf991c38d ~/.config/VirtualBox/xpti.dat
  329,IVirtualBox,{d0a0163f-e254-4e5b-a1f2-011cf991c38d},0,-1,1


If I “vboxmanage modifyvm --nested-hw-virt off” then my VM starts up fine, so I’ve eliminated other problems.

I assume that the kernel has to allow VirtualBox to do this kind of stuff? Is there perhaps a sysctl setting to permit this, or is it simply not doable in FreeBSD-12?

Thanks,

/Sebastian

PS. I’d actually much rather run my VM under bhyve, anyone know the status of nested virtualization there?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: VBoxSVC.log
Type: application/octet-stream
Size: 3244 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-virtualization/attachments/20210317/055b8ac7/attachment.obj>