Give feedback

How would you rate this Learning Path?

Review frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
Why do I need a bare-metal Arm64 server?
A bare-metal server provides direct access to the processor’s EL2 virtualization support and hardware that supports FEAT_NV2. A standard VM doesn’t provide the access needed to enable nested virtualization.
How do I confirm that nested virtualization is enabled on the host?
Check the host’s kernel messages for VHE+NV2 mode initialized successfully. If you see VHE mode initialized successfully without +NV2, nested virtualization isn’t enabled. Check whether the kernel argument was applied and whether the hardware supports FEAT_NV2.
How do I verify that the hypervisor VM can run a nested guest?
Inside the L1 hypervisor VM, check the kernel messages for CPU: All CPU(s) started at EL2 and confirm that /dev/kvm exists. These checks show that virtualization support is available to the VM.
How do I connect to the nested guest VM after it starts?
In the L1 hypervisor VM, use virsh net-dhcp-leases default to find the L2 guest’s IP address. Connect with ssh -i ~/guest_key fedora@<L2-guest-IP-address> using the private key that you copied into the hypervisor VM.
Which result should I compare across bare metal and guest VMs?
Compare events per second from your sysbench output to assess throughput. After pinning each system to the specified cores, calculate each guest’s overhead against your bare-metal result rather than treating the example numbers as expected results.

Share

Tell others about this Learning Path.

Back
Return to Servers and Cloud Computing