XK0-005 · Question #800
A Linux administrator is attempting to create a KVM on a remote Linux server. After failing to create the VM, the administrator runs some commands and reviews the following output: Output1: Output2…
The correct answer is B. The virtual server does not allow VMs running inside the VM. The inability to create a KVM virtual machine on a remote Linux server that is itself a virtual machine, often points to a lack of nested virtualization support. This means the hypervisor running the remote Linux server does not expose virtualization extensions to its guests.
Question
A Linux administrator is attempting to create a KVM on a remote Linux server. After failing to create the VM, the administrator runs some commands and reviews the following output:
Output1:
Output2:
Which of the following is the most likely cause of the issue?
Options
- AVirtualization does not work on 32-bit processors.
- BThe virtual server does not allow VMs running inside the VM.
- CThe memory capacity and swap space are both inadequate.
- DThe boot partition does not have enough available space.
How the community answered
(43 responses)- A2% (1)
- B86% (37)
- C5% (2)
- D7% (3)
Why each option
The inability to create a KVM virtual machine on a remote Linux server that is itself a virtual machine, often points to a lack of nested virtualization support. This means the hypervisor running the remote Linux server does not expose virtualization extensions to its guests.
Virtualization can work on 32-bit processors, though 64-bit is far more common and performant for modern virtualization. The issue is more about hardware support being available or passed through.
KVM (Kernel-based Virtual Machine) requires hardware virtualization extensions (Intel VT-x or AMD-V) to be available to the guest operating system. If the remote Linux server is itself a virtual machine, the underlying hypervisor must explicitly enable "nested virtualization" for its guest to then be able to run KVM virtual machines. The failure to create a VM suggests these hardware extensions are not being passed through, meaning the virtual server does not allow VMs running inside the VM.
Inadequate memory or swap space would likely manifest as specific resource allocation errors, but the fundamental issue of KVM failing to *create* a VM often points to a lack of virtualization capabilities.
Insufficient boot partition space is generally unrelated to the ability to create and run a VM, which primarily depends on data storage space and available system resources like CPU and RAM.
Concept tested: KVM virtualization requirements, nested virtualization, hypervisor capabilities
Source: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-nested_virtualization-chap_nested_virtualization
Topics
Community Discussion
No community discussion yet for this question.