Skip to content
Published on

[Virtualization] 03. VirtualBox and VMware: From Desktop to Enterprise

🇰🇷KO🇺🇸EN🇯🇵JA
Split View
Authors

Introduction

VirtualBox and VMware are among the most widely used virtualization products. VirtualBox represents open-source desktop virtualization, while VMware offers a full lineup from desktop (Workstation/Fusion) to enterprise (ESXi/vSphere).

VirtualBox Architecture

Core Structure

VirtualBox is an open-source Type 2 hypervisor managed by Oracle.

+-----------------------------------------------+
|           VirtualBox Manager (GUI/CLI)          |
+-----------------------------------------------+
|  VM 1         |  VM 2         |  VM 3          |
|  Guest Adds   |  Guest Adds   |  (No Adds)     |
+-----------------------------------------------+
|           VirtualBox VMM Engine                 |
|  (Ring-0 Driver + User-space Components)       |
+-----------------------------------------------+
|           Host OS (Windows/macOS/Linux)         |
+-----------------------------------------------+
|           Physical Hardware                     |
+-----------------------------------------------+

Key Features:

  • Type 2 hypervisor (runs on top of host OS)
  • Leverages Intel VT-x / AMD-V hardware virtualization
  • Cross-platform: Windows, macOS, Linux, Solaris
  • Free + open-source (GPLv3, Extension Pack is PUEL license)
  • Automatable via VBoxManage CLI

Virtual GPU Options

Virtual GPUResolution3D AccelerationNotes
VBoxVGAUp to 4KNoneLegacy, Windows XP and below
VBoxSVGAUp to 4KLimitedRecommended for Windows 7+
VMSVGAUp to 4KOpenGL ~3.0Recommended for Linux guests

Guest Additions

Guest Additions is a paravirtualized driver package installed in the guest OS.

Provided Features:

  • Mouse pointer integration (seamless switching)
  • Shared folders (host-guest file sharing)
  • Automatic screen resolution adjustment
  • Time synchronization
  • Clipboard sharing
  • Drag and drop
  • 3D acceleration (experimental OpenGL ~3.0, D3D experimental)

VirtualBox GPU Limitations

VirtualBox has clear GPU virtualization limitations.

  • No GPU Passthrough: Experimental PCI passthrough was removed in v6.1.0
  • No vGPU Support: No integration with NVIDIA GRID or AMD MxGPU
  • No Vulkan Support: Only OpenGL ~3.0 available
  • Max VRAM: 256MB (insufficient for GPU-intensive workloads)
  • Video Encode/Decode: No hardware acceleration
[VirtualBox GPU Feature Summary]

GPU Passthrough:   Not supported
vGPU:              Not supported
Vulkan:            Not supported
OpenGL:            ~3.0 (experimental)
DirectX:           Experimental (partial D3D 8/9)
Max VRAM:          256MB
Monitors:          Up to 8 (2D only)

VMware Product Family

Product Lineup

+-----------------------------------------------------+
|                   VMware Products                     |
+-----------------------------------------------------+
|                                                       |
|  [Desktop]              [Enterprise]                  |
|                                                       |
|  Workstation Pro/Player  ESXi (Type 1 Hypervisor)    |
|  (Windows/Linux)         vCenter Server               |
|                          vSphere Suite                |
|  Fusion Pro/Player       vSAN                        |
|  (macOS)                 NSX (Network Virtualization)|
|                          Aria (Monitoring)            |
+-----------------------------------------------------+

VMware Workstation

+-----------------------------------------+
|  VM 1 (Windows)  |  VM 2 (Ubuntu)       |
|  NAT / Bridged   |  Host-Only / Custom  |
+-----------------------------------------+
|  VMware Workstation Pro                  |
|  (Type 2 Hypervisor)                    |
+-----------------------------------------+
|  Host OS (Windows / Linux)              |
+-----------------------------------------+
|  Hardware (VT-x/AMD-V required)         |
+-----------------------------------------+

Key Features:

  • Snapshots and clones (Linked Clone for disk savings)
  • Virtual Network Editor (NAT, bridged, host-only, custom)
  • Unity mode (integrate guest apps into host desktop)
  • Container support via vctl
  • UEFI Secure Boot support

VMware Fusion (macOS)

  • macOS-exclusive Type 2 hypervisor
  • Native Apple Silicon (M1/M2/M3/M4) support
  • Run ARM-based Windows 11 and Linux
  • Metal-based 3D graphics acceleration
  • macOS guest VM support (within license terms)

VMware ESXi (Type 1)

+---------------------------------------------------+
| VM 1        | VM 2        | VM 3        | VM 4    |
| (Production)| (Database)  | (Web App)   | (Test)  |
+---------------------------------------------------+
|                VMkernel                            |
|  +----------+  +----------+  +----------+         |
|  | VMFS 6   |  | vDS      |  | Firewall |         |
|  | Storage  |  | Network  |  | Module   |         |
|  +----------+  +----------+  +----------+         |
+---------------------------------------------------+
|           Physical Hardware                        |
|  (CPU, RAM, HBA/NIC, PCIe Devices)               |
+---------------------------------------------------+

VMkernel Core Components:

ComponentRole
VMkernelLightweight microkernel, resource scheduling
VMFSVM-specific clustered filesystem
vDS (Distributed Switch)Unified virtual network management across hosts
DCUIDirect Console User Interface (local management)

vSphere Ecosystem

vSphere is the combination of ESXi + vCenter Server, forming an enterprise virtualization platform.

Core Features

[vSphere Feature Architecture]

+------------------+
|   vCenter Server |  <-- Central Management
+--------+---------+
         |
    +----+----+----+----+
    |    |    |    |    |
  ESXi ESXi ESXi ESXi ESXi  <-- Cluster
    |    |    |    |    |
    +----+----+----+----+
         |
   Shared Storage (vSAN / SAN / NFS)
FeatureDescription
vMotionLive-migrate a running VM to another host
Storage vMotionLive-move VM disks to a different datastore
DRSDistributed Resource Scheduler - automatic load balancing
HAHigh Availability - auto-restart VMs on host failure
FTFault Tolerance - real-time VM duplication (lockstep)
vSANSoftware-defined storage from local disks

vMotion Workflow

Source ESXi Host              Destination ESXi Host
+------------------+         +------------------+
| VM (Running)     |         | VM (Preparing)   |
| Memory Pages     | ------> | Memory Copy      |
| (Pre-copy)       |         | (Iterative)      |
+------------------+         +------------------+
        |                            |
        |    1. Pre-copy memory       |
        |    2. Iterative dirty pages |
        |    3. Brief VM pause (~ms)  |
        |    4. Transfer final state  |
        |    5. Resume on destination |
        v                            v
   Shared Storage (SAN / vSAN / NFS)

VMware vGPU Support

NVIDIA GRID Integration

VMware ESXi fully supports NVIDIA GRID/vGPU.

+----------+ +----------+ +----------+
| VM 1     | | VM 2     | | VM 3     |
| vGPU     | | vGPU     | | vGPU     |
| Q-series | | C-series | | B-series |
+----------+ +----------+ +----------+
|         vGPU Manager (ESXi)        |
+------------------------------------+
|         Physical GPU               |
|   (NVIDIA A100/A30/L40S/etc.)     |
+------------------------------------+

vGPU Performance:

  • Achieves 88-96% of native performance (workload-dependent)
  • Per-profile VRAM and encoder allocation
  • GPU resource management via QoS policies

Supported Technologies

TechnologySupport Status
NVIDIA vGPU (mdev)Volta and earlier, software time-slicing
NVIDIA vGPU (SR-IOV)Ampere+, hardware partitioning
MIG-backed vGPUMIG slice allocation on A100/A30/H100
AMD MxGPUSR-IOV-based GPU sharing
ESXi 8u3+ mixed profilesMix different vGPU types on same GPU

Product Comparison Table

FeatureVirtualBoxVMware WorkstationVMware ESXi
TypeType 2Type 2Type 1
LicenseFree (GPLv3)Paid (free Player available)Paid (subscription)
Host OSWin/Mac/LinuxWindows/LinuxNone (bare-metal)
Max VM RAMHost-dependentHost-dependentFull physical RAM
Max vCPUs3232Unlimited (by license)
GPU PassthroughNot supportedNot supportedSupported (VFIO)
vGPUNot supportedNot supportedNVIDIA GRID, AMD MxGPU
3D AccelerationOpenGL ~3.0DX11, OpenGL 4.3vGPU-dependent
Live MigrationNot supportedNot supportedvMotion supported
SnapshotsSupportedSupportedSupported
Primary UsePersonal/DevDevelopment/TestingProduction/Datacenter

vSphere 9.0 Licensing Changes

Following Broadcom's acquisition of VMware in 2024, the licensing model changed significantly.

Key Changes:

  • Perpetual licenses eliminated; subscription-only
  • Individual product sales discontinued (cannot purchase ESXi alone)
  • Consolidated into two bundles:
    • VVF (VMware vSphere Foundation): Base virtualization + vSAN
    • VCF (VMware Cloud Foundation): Full SDDC stack (vSphere + vSAN + NSX + Aria)
  • Switched from per-socket to per-core licensing
  • Free ESXi license (vSphere Hypervisor) discontinued
[Licensing Change Summary]

Before (VMware):
  ESXi Free  |  vSphere Std  |  vSphere Ent+  |  Individual purchase
  (free)     |  (perpetual)  |  (perpetual)    |

After (Broadcom):
  VVF (vSphere Foundation)  |  VCF (Cloud Foundation)
  (subscription, per-core)   |  (subscription, per-core)
  No individual ESXi purchase, no free license

This shift has led many organizations to evaluate alternatives such as Proxmox VE and Nutanix AHV.

Hands-On: VBoxManage CLI

# Create a VM
VBoxManage createvm --name "test-ubuntu" --ostype "Ubuntu_64" --register

# Configure memory and vCPUs
VBoxManage modifyvm "test-ubuntu" --memory 4096 --cpus 4

# Create and attach virtual disk
VBoxManage createmedium disk --filename "test-ubuntu.vdi" --size 50000
VBoxManage storagectl "test-ubuntu" --name "SATA" --add sata
VBoxManage storageattach "test-ubuntu" --storagectl "SATA" \
  --port 0 --device 0 --type hdd --medium "test-ubuntu.vdi"

# Attach ISO
VBoxManage storageattach "test-ubuntu" --storagectl "SATA" \
  --port 1 --device 0 --type dvddrive --medium ubuntu.iso

# Configure network (NAT -> Bridge)
VBoxManage modifyvm "test-ubuntu" --nic1 bridged --bridgeadapter1 en0

# Start VM
VBoxManage startvm "test-ubuntu" --type headless

# Take snapshot
VBoxManage snapshot "test-ubuntu" take "clean-install"

# List VMs
VBoxManage list vms
VBoxManage list runningvms
Quiz: VirtualBox/VMware Knowledge Check

Q1. Why can you not use GPU passthrough in VirtualBox?

VirtualBox removed experimental PCI passthrough in v6.1.0. If you need vGPU or GPU passthrough, use VMware ESXi, KVM/QEMU, or Proxmox VE instead.

Q2. What is the core principle of VMware vMotion?

It pre-copies the running VM's memory to the destination host, iteratively transfers changed pages, then briefly pauses the VM (a few ms) to transfer the final state. Since shared storage is used, no disk movement is needed.

Q3. How does VMkernel differ from a standard Linux kernel?

VMkernel is a lightweight microkernel specialized for virtualization, focusing exclusively on resource scheduling and hardware abstraction without general-purpose features. A standard Linux kernel is a monolithic kernel for diverse use cases.

Q4. What is the biggest licensing change after the Broadcom acquisition?

Perpetual licenses were eliminated in favor of subscription-only. ESXi can no longer be purchased individually; it is only available through VVF or VCF bundles. The free ESXi license was also discontinued.

Q5. What key value do Guest Additions/VMware Tools provide?

They improve graphics, network, and storage performance through paravirtualized drivers, and provide host-guest integration features like mouse integration, shared folders, automatic resolution adjustment, and clipboard sharing.

Discuss on Twitter • View on GitHub