[SOLVED] Virtualbox inside VM, exhausting RAM


Nov 4, 2019
I'm running proxmox 6.0-11, and trying to setup a Windows 10 VM, where Windows 10 should be hosting Virtualbox.

Verifying that nested virtualization is enabled:
$ cat /sys/module/kvm_intel/parameters/nested

The processor type is set to "host".

I've installed the VirtIO tools on the Windows 10 host and given it 16gb of RAM.
The Ballooning services is running.
When I try to start a guest inside Virtualbox, proxmox reports full RAM usage and Windows logs out the user.
The guest I try to start is given 2Gb of RAM.

The closes previous issue to this I could find was this thread: https://forum.proxmox.com/threads/nested-virtualisation-problem.59647/
Any ideas / suggestions on what to check/test next?

GIFs of the host logging out the user and the RAM spike: https://imgur.com/a/z1ixCs9

root at proxmox in /etc/pve/qemu-server
$ cat 105.conf
agent: 1
balloon: 4096
bootdisk: virtio0
cores: 6
cpu: host
memory: 16384
name: VirtualBox
net0: virtio=2E:55:CD:27:B2:87,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
parent: InitialInstall
scsihw: virtio-scsi-pci
smbios1: uuid=061b9454-81c6-47b6-b2b8-ceb041a1de4a
sockets: 1
virtio0: local-lvm:vm-105-disk-0,cache=writeback,size=200G
vmgenid: 8bd70e00-f754-4f14-a6e8-b141282700dd

Virtualbox's VBoxSVC.log:
00:00:00.000464 main     VirtualBox COM Server 6.0.14 r133895 win.amd64 (Oct 10 2019 19:44:31) release log
00:00:00.000466 main     Log opened 2019-11-05T16:46:32.594733500Z
00:00:00.000466 main     Build Type: release
00:00:00.000469 main     OS Product: Windows 10
00:00:00.000470 main     OS Release: 10.0.18362
00:00:00.000471 main     OS Service Pack: 
00:00:00.065667 main     DMI Product Name: Standard PC (i440FX + PIIX, 1996)
00:00:00.076504 main     DMI Product Version: pc-i440fx-4.0
00:00:00.076515 main     Host RAM: 16383MB (15.9GB) total, 12342MB (12.0GB) available
00:00:00.076522 main     Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
00:00:00.076523 main     Process ID: 2684
00:00:00.076523 main     Package type: WINDOWS_64BITS_GENERIC
00:00:00.132930          VirtualBox: object creation starts
00:00:00.133076          Home directory: 'C:\Users\bob\.VirtualBox'
00:00:00.133147          Installed Drivers:
00:00:00.137041            C:\Windows\system32\DRIVERS\VBoxNetLwf.sys (Version:
00:00:00.137367            C:\Windows\system32\DRIVERS\VBoxUSBMon.sys (Version:
00:00:00.137670            C:\Windows\system32\DRIVERS\VBoxDrv.sys (Version:
00:00:00.138239            C:\Windows\system32\DRIVERS\VBoxNetAdp6.sys (Version:
00:00:00.144287          Loading settings file "C:\Users\bob\.VirtualBox\VirtualBox.xml" with version "1.12-windows"
00:00:00.217295          Getting USB descriptor (id 0) failed with error 31
00:00:00.219197          USB: Unknown USB device detected (idVendor: 0x0627, idProduct: 0x0001)
00:00:00.327063          HostDnsMonitor::updateInfo
00:00:00.327081          HostDnsMonitor: old information
00:00:00.327083            no server entries
00:00:00.327084            no domain set
00:00:00.327084            no search string entries
00:00:00.327085          HostDnsMonitor: new information
00:00:00.327085            server 1:
00:00:00.327086            server 2:
00:00:00.327086            server 3:
00:00:00.327086            domain: mydomain
00:00:00.327087            no search string entries
00:00:00.383412          VD: VDInit finished with VINF_SUCCESS
00:00:00.388528          Loading settings file "C:\Users\bob\Downloads\19-2M-64bit\LinuxMint\LinuxMint.vbox" with version "1.16-windows"
00:00:00.389455          VirtualBox: object created
00:00:06.632971          Saving settings file "C:\Users\bob\Downloads\19-2M-64bit\LinuxMint\LinuxMint.vbox" with version "1.16-windows"
I'm running proxmox 6.0-11, and trying to setup a Windows 10 VM, where Windows 10 should be hosting Virtualbox.
This is not a supported scenario. Why not run the LinuxMint on the hypervisor itself and connect via SPICE? This can give you also a seamless experience while removing the nested factor.
Thanks for the reply.
Have setup a Mint instance, connecting via SPICE like you said.
Did a Mint, connecting via SPICE like you said, works :)
  • Like
Reactions: Alwin


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!