Understanding Nested Virtualization
Nested virtualization is a technique where a hypervisor runs inside another hypervisor. In your specific scenario, VMware Workstation (or Player) acts as the host hypervisor, while Ubuntu serves as the guest operating system. Inside that Ubuntu instance, you install QEMU to act as a secondary hypervisor. For this architecture to function correctly, the outer layer (VMware) must pass through the virtualization capabilities of the physical CPU to the inner layer (Ubuntu).
If nested virtualization is disabled, QEMU attempts to access CPU flags like vtx or svm but finds them unavailable. The error message typically reads "KVM: VMX disabled by BIOS" or simply fails to initialize the KVM accelerator. Enabling this feature is not about performance optimization; it is a strict technical requirement for running any virtual machine software within a virtual machine.
Configuring VMware Settings
The first step involves modifying the configuration of your Ubuntu virtual machine in VMware. You do not need to shut down the host computer, only the Ubuntu guest. Open VMware and select the Ubuntu VM, then choose Edit Virtual Machine Settings.
- Navigate to the Processors section in the settings menu.
- Locate the checkbox labeled Virtualize Intel VT-x/EPT or AMD-V/RVI.
- Check this box to enable the feature.
- Click OK to save the changes.
This setting instructs VMware to present the hardware virtualization instructions to the guest OS kernel. If you are using an older version of VMware, such as Legacy VMware Player mentioned in related guides, ensure you are using a compatible build that supports modern CPU instruction sets. After applying these changes, restart the Ubuntu virtual machine to ensure the new processor topology is loaded.
Verifying Hardware Support in Ubuntu
Once Ubuntu has rebooted, you must verify that the operating system can see the virtualization extensions. Open a terminal window and use the lscpu command. Look for the line labeled Flags in the output. You should see either vtx (for Intel processors) or svm (for AMD processors) listed among the flags.
If these flags are missing, nested virtualization is still not active. Check the VMware status bar at the bottom of the window to confirm the VM is powered on. Sometimes, changes require a full power cycle rather than just a restart. Additionally, ensure that your physical CPU actually supports these extensions. Most modern CPUs do, but older models may lack the necessary hardware support entirely.
You can also check if the KVM module is loaded by running lsmod | grep kvm. The presence of kvm_intel or kvm_amd indicates that the Linux kernel has successfully detected the virtualization hardware provided by VMware.
Installing and Configuring QEMU
With hardware support confirmed, proceed to install QEMU and the necessary utilities. Use the standard package manager to install the core components:
sudo apt update
sudo apt install qemu-system-x86 qemu-utils virt-manager libvirt-daemon-system libvirt-clients bridge-utilsWhile qemu-system-x86 provides the emulator, installing libvirt tools allows for more robust management of virtual machines via XML definitions and command-line interfaces. However, basic usage can be achieved with just the QEMU binaries. It is important to note that virt-manager is a graphical frontend and is not strictly required for QEMU to function, though it simplifies the creation of complex network configurations.
Create a disk image for your test virtual machine using qemu-img:
qemu-img create -f qcow2 test_vm.qcow2 10GThis command creates a 10-gigabyte dynamically allocated QCOW2 image. You can now attempt to boot a simple ISO or another Linux distribution using this image. Ensure you specify the acceleration option to leverage the nested KVM support:
qemu-system-x86_64 -enable-kvm -m 2048 -hda test_vm.qcow2 cdrom.isoThe -enable-kvm flag tells QEMU to use the Kernel-based Virtual Machine interface, which is significantly faster than software emulation. If the VM boots successfully, your nested virtualization setup is complete.
Troubleshooting Common Issues
If QEMU fails to start with KVM enabled, check the dmesg logs for errors related to permission denied or device not found. Often, the user needs to be added to the kvm group to access the virtualization devices:
sudo usermod -aG kvm $USERLog out and log back in for this change to take effect. Another common issue arises from conflicting hypervisors. If you have other virtualization software installed on the Ubuntu host, such as VirtualBox, they may lock the KVM modules. Stop any competing services before launching QEMU.
Performance in nested virtualization is inherently lower than bare-metal virtualization due to the double translation of memory addresses and CPU instructions. Expect reduced throughput when running heavy workloads inside the QEMU guest. For development purposes, however, this setup provides a flexible and isolated testing environment without risking your primary host system.
Frequently Asked Questions
Can I run nested virtualization on VMware ESXi?
Yes, ESXi supports nested virtualization, but it requires enabling the feature in the cluster settings and marking the specific VM as a "nested" guest. You must also edit the VM's .vmx file to set vhv.enable = "TRUE". This process is more complex than in Workstation and requires administrative privileges on the hypervisor host.
Does nested virtualization affect the performance of my main Ubuntu installation?
Nested virtualization consumes additional CPU cycles because the host hypervisor must emulate the virtualization extensions for the guest. While idle performance remains largely unaffected, running intensive tasks inside QEMU will increase resource contention. Monitor your host system's load average to ensure stability during heavy workloads.
Is it possible to use GPU passthrough in a nested virtualization setup?
GPU passthrough is generally not feasible in nested setups because the outer hypervisor manages the physical GPU. The inner guest receives a virtualized display adapter, typically VGA or VirtIO-GPU. Attempting to pass through a GPU to the inner QEMU guest usually results in driver conflicts or black screens due to lack of direct hardware access.
What is the difference between QEMU-KVM and pure QEMU?
Pure QEMU emulates hardware entirely in software, which is slow but highly portable. QEMU-KVM utilizes the Linux kernel's virtualization module to accelerate execution by accessing hardware directly. In a nested environment, QEMU-KVM accesses the virtualized extensions exposed by VMware, providing near-native speeds compared to software emulation.
How do I share folders between the Ubuntu host and the QEMU guest?
You can use shared folders by configuring a VirtIO filesystem in QEMU. Mount a directory from the Ubuntu host into the QEMU guest using the -fsdev and -device virtio-9p-pci arguments. Alternatively, set up a Samba or NFS server on the Ubuntu host and mount the share within the QEMU guest for easier file exchange.