NCA-5.15 · Question #46
An administrator is managing two AHV and vSphere-based clusters. The administrator is able to install a Windows Guest OS from an ISO Image to VMware VMs, but is unable to do the same activity with…
The correct answer is B. Provide virtIO drivers. AHV is based on KVM, which uses paravirtualized storage controllers (VirtIO-SCSI) and network adapters (VirtIO-Net). Windows does not ship with VirtIO drivers natively, so during OS installation from an ISO, Windows cannot detect the virtual disk because it has no driver for…
Question
An administrator is managing two AHV and vSphere-based clusters. The administrator is able to install a Windows Guest OS from an ISO Image to VMware VMs, but is unable to do the same activity with AHV VMs. What should the administrator do to successfully perform this action with AHV VMs?
Options
- AVerify cluster iSCSI Data Services IP
- BProvide virtIO drivers
- CManage Nutanix Guest Tools
- DChange VM settings from BIOS to UEFi
How the community answered
(63 responses)- A5% (3)
- B71% (45)
- C10% (6)
- D14% (9)
Explanation
AHV is based on KVM, which uses paravirtualized storage controllers (VirtIO-SCSI) and network adapters (VirtIO-Net). Windows does not ship with VirtIO drivers natively, so during OS installation from an ISO, Windows cannot detect the virtual disk because it has no driver for the VirtIO controller. The administrator must inject or load the VirtIO drivers during the installation wizard (via a secondary ISO or driver floppy) for Windows to see the disk and complete installation. VMware uses the LSI Logic or PVSCSI controllers that Windows recognizes more readily. iSCSI Data Services IP (A) relates to external iSCSI connections, not local VM disk visibility. Nutanix Guest Tools (C) are installed post-OS installation. BIOS/UEFI (D) affects boot firmware, not disk driver detection.
Topics
Community Discussion
No community discussion yet for this question.