nerdexam
CompTIA

SK0-004 · Question #432

An administrator is asked to move a 64-bit guest to a new host. However, the guest will not boot on the new host. Which of the following is the cause of the problem?

The correct answer is D. The new host's hypervisor is not Type 2. A 64-bit guest VM requires the new host to have a compatible Type 2 hypervisor installed to provide the correct virtualization environment for the guest to boot.

Troubleshooting

Question

An administrator is asked to move a 64-bit guest to a new host. However, the guest will not boot on the new host. Which of the following is the cause of the problem?

Options

  • AThe new host's hypervisor is not Type 1
  • BThe management interface is not activated on the host
  • CIn the BIOS, AMD-V Intel VT are not turned on
  • DThe new host's hypervisor is not Type 2

How the community answered

(29 responses)
  • A
    10% (3)
  • B
    14% (4)
  • C
    3% (1)
  • D
    72% (21)

Why each option

A 64-bit guest VM requires the new host to have a compatible Type 2 hypervisor installed to provide the correct virtualization environment for the guest to boot.

AThe new host's hypervisor is not Type 1

A Type 1 (bare-metal) hypervisor runs directly on hardware and generally supports 64-bit guests when hardware virtualization is available, so the hypervisor being Type 1 is not itself the stated cause.

BThe management interface is not activated on the host

The management interface controls administrative access to the hypervisor host and has no bearing on whether a guest VM can boot.

CIn the BIOS, AMD-V Intel VT are not turned on

While disabled AMD-V or Intel VT in the BIOS can block 64-bit virtualization, the scenario identifies the hypervisor type mismatch on the new host as the cause of the boot failure.

DThe new host's hypervisor is not Type 2Correct

A Type 2 (hosted) hypervisor runs on top of a host operating system and provides the virtualization layer guest VMs depend on to run. If the new host lacks the matching Type 2 hypervisor, a guest VM created and configured for that environment cannot find the required runtime and will fail to boot. VM images and configurations are often tightly coupled to the hypervisor type they were created on, requiring conversion before they can run on a different type.

Concept tested: Type 1 vs Type 2 hypervisor guest VM compatibility

Source: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-technology-overview

Topics

#hypervisor types#hardware virtualization#AMD-V Intel VT#64-bit guests

Community Discussion

No community discussion yet for this question.

Full SK0-004 Practice