Page 1 of 1

VirtualBox Limits

PostPosted: 2. May 2011, 00:26
by Technologov
Those are VirtualBox 4.0.6 limits, from what I was able to find from various sources.

Host: (per Physical Machine limits)
Linux/Solaris 64-bit and 32-bit hosts, CPUs[1]: 256
Windows 64-bit and 32-bit hosts, CPUs[1]: 32 (?)
Host-only Networks: 8
on Linux 64-bit hosts: 1023 VMs (on standard kernels up to 127 VMs. UPDATE: 8191 VMs on VBox 4.1) [2]
on Linux 32-bit hosts: 127 VMs
on Windows hosts: 63 VMs [3]
Windows Hosts Incompatible Software: see here
Linux Hosts Incompatible Software: Xen and KVM.
RAM: 16 TiB (on 64-bit hosts)
RAM: 64 GiB (on 32-bit hosts)

[1] Any logical CPU: Can be physical CPU or Core or Hardware Thread, such as Intel Hyper-Threading Technology.
Code for hard VMM limits here.
For details, see include/VBox/param.h

[2] NOTE: This will require several VBoxSVC processes, for several system users. Up to 1k VMs per VBoxSVC process.

[3] According to Klaus, this is due to Windows limited the array of objects one can wait for to 64. link

Guests: (per Virtual Machine limits)
CPUs per guest: 32 Cores
RAM per guest: 16 GiB on 64-bit hosts (UPDATE: 1 TiB RAM on VBox 4.1)
RAM per guest: 3.5 GiB on 32-bit hosts
vNICs per guest: 8
vMonitors per guest: 8
HDD size: 2 TiB

Network Stack / IPv6:
While VirtualBox has basic IPv6 enablement, certain parts are NOT IPv6 capable.
1. Bridge to Ethernet supports IPv6, but to WiFi is IPv4-only
2. NAT is IPv4-only. (workaround: NATv6 is provided via VDE on Linux hosts)
3. UDP Tunnel - guest layer supports IPv6, but host layer is IPv4-only.
4. Host-only network - DHCP server is IPv4-only.
5. RDP Server is IPv4-only.
6. Teleportation ?
7. Proxy ?
8. VNC server ?