[NotSupported] Nested virtualisation problem (Virtual box inside KVM)

[mercury131]

Hello everyone!

I try to run virtual box inside VM, but when I run vm inside virtual box it freezes.

How it looks:
https://gyazo.com/d837355d90eef7f8715b5a8914c61712
I still see virtual box start screen, F12 button not working.

But I can reset /poweroff this VM and virtualbox GIU working, I dont understand what hapening.

I check my PVE, nested virtualization enabled, my CPU support it, inside guest VM (centos 7, where installed Virtual box ) I run:

Code: Select all

[root@localhost ~]# virt-host-validate
  QEMU: Checking for hardware virtualization                                 : PASS
  QEMU: Checking if device /dev/kvm exists                                   : PASS
  QEMU: Checking if device /dev/kvm is accessible                            : PASS
  QEMU: Checking if device /dev/vhost-net exists                             : PASS
  QEMU: Checking if device /dev/net/tun exists                               : PASS
  QEMU: Checking for cgroup 'memory' controller support                      : PASS
  QEMU: Checking for cgroup 'memory' controller mount-point                  : PASS
  QEMU: Checking for cgroup 'cpu' controller support                         : PASS
  QEMU: Checking for cgroup 'cpu' controller mount-point                     : PASS
  QEMU: Checking for cgroup 'cpuacct' controller support                     : PASS
  QEMU: Checking for cgroup 'cpuacct' controller mount-point                 : PASS
  QEMU: Checking for cgroup 'cpuset' controller support                      : PASS
  QEMU: Checking for cgroup 'cpuset' controller mount-point                  : PASS
  QEMU: Checking for cgroup 'devices' controller support                     : PASS
  QEMU: Checking for cgroup 'devices' controller mount-point                 : PASS
  QEMU: Checking for cgroup 'blkio' controller support                       : PASS
  QEMU: Checking for cgroup 'blkio' controller mount-point                   : PASS
  QEMU: Checking for device assignment IOMMU support                         : WARN (No ACPI IVRS table found, IOMMU either disabled in BIOS or not supported by this hardware platform)
   LXC: Checking for Linux >= 2.6.26                                         : PASS
   LXC: Checking for namespace ipc                                           : PASS
   LXC: Checking for namespace mnt                                           : PASS
   LXC: Checking for namespace pid                                           : PASS
   LXC: Checking for namespace uts                                           : PASS
   LXC: Checking for namespace net                                           : PASS
   LXC: Checking for namespace user                                          : PASS
   LXC: Checking for cgroup 'memory' controller support                      : PASS
   LXC: Checking for cgroup 'memory' controller mount-point                  : PASS
   LXC: Checking for cgroup 'cpu' controller support                         : PASS
   LXC: Checking for cgroup 'cpu' controller mount-point                     : PASS
   LXC: Checking for cgroup 'cpuacct' controller support                     : PASS
   LXC: Checking for cgroup 'cpuacct' controller mount-point                 : PASS
   LXC: Checking for cgroup 'cpuset' controller support                      : PASS
   LXC: Checking for cgroup 'cpuset' controller mount-point                  : PASS
   LXC: Checking for cgroup 'devices' controller support                     : PASS
   LXC: Checking for cgroup 'devices' controller mount-point                 : PASS
   LXC: Checking for cgroup 'blkio' controller support                       : PASS
   LXC: Checking for cgroup 'blkio' controller mount-point                   : PASS
   LXC: Checking if device /sys/fs/fuse/connections exists                   : PASS

and see virtualisation is activated.

I check another VM with same qemu settings, with windows guest and Hyper V in it. Everything is working I can run 64bit VM, also I try VMware ESXI, it also works. I dont understand why Virtual box not run VM.

My proxmox VM config:

Code: Select all

args: -cpu host,+svm
balloon: 0
boot: cdn
bootdisk: sata0
cores: 8
cpu: host
efidisk0: SSD:vm-111-disk-1,size=128K
freeze: 1
ide2: local:iso/CentOS-7-x86_64-DVD-1908.iso,media=cdrom
machine: pc-i440fx-2.11
memory: 8192
name: OTUS3
net0: e1000=1E:5E:45:F0:1F:86,bridge=vmbr0,firewall=1
numa: 0
ostype: other
sata0: SSD:vm-111-disk-0,cache=directsync,size=200G
serial0: socket
smbios1: uuid=795d6338-6e51-400f-88c0-116c09845fee
sockets: 1
vmgenid: 7226a854-6037-4b75-902e-073320ca12fe

My PVE (proxmox) version pve-manager/6.0-9/508dcee0 (running kernel: 5.0.21-3-pve)

My CPU:
AMD FX(tm)-8320 Eight-Core

Virtual box VM settings:
https://gyazo.com/1e8889bd340e5416875128d4ac5871f6
https://gyazo.com/c85944dee0c20be9f8610e29855d4228
https://gyazo.com/479130ba31bc1385db0df047d43106b6

Also I try to run vm via terminal command, no errors in output:

Code: Select all

[root@localhost ~]# VBoxManage startvm 4
Waiting for VM "4" to power on...
VM "4" has been successfully started.

I try to Enable/Disable CPU acceleration, PAE, Nested Paging, add vCPU/RAM - nothing helps.

Please help me run Virtual box correctly =)

I need it for internal testing (vbox + vagrant tests)

Sorry I can not post links =(

[socratis]

Please attach the images locally in your response (see the "Upload attachment" tab below the reply form). Not a lot of people will go to 3rd party sites. Plus, it's more convenient if the image goes along with the message, same with the log. Oh, and you should ZIP your logs. It helps you, it helps us, it helps the server, it helps save a (virtual) tree or two...

Nested virtualisation problem (Virtual box inside KVM)

For the moment the only supported configuration is VirtualBox inside VirtualBox, nothing else. I'm afraid I'm going to have to mark this as [NotSupported].

[mercury131]

I understand this is unsupported configuration, I just think maybe some one have same issue and solve it =)
Or you can tell some VitualBox tweaks or troubleshoot guide.

[socratis]

Or you can tell some VitualBox tweaks or troubleshoot guide.

If I knew anything I would have already told you in my previous answer.

I just got VirtualBox-on-VirtualBox myself working. How about trying yourself that too first?