A system administrator is troubleshooting severe audio packet dropouts and latency spikes on a virtualized voice gateway server. The host hardware runs a standard Windows Server operating system with a hosted virtualization software package managing the gateway guest virtual machine. Diagnostics reveal that background host OS maintenance tasks and host device driver interrupts are periodically preempting CPU access from the virtualization software layer. Which architectural change should the administrator make to eliminate this host OS scheduling bottleneck?
- Migrate the virtual machine to a Type 1 hypervisor installed directly on bare-metal hardware, eliminating host operating system resource contention.Cevap
- BReconfigure the existing hosted hypervisor to execute guest kernel calls inside ring 0 of the host operating system.
- CConvert the existing Type 2 hypervisor instance into a Type 1 hypervisor by allocating dedicated physical CPU cores to the host operating system.
- DDeploy a lightweight desktop OS to manage hardware interactions while maintaining the hosted hypervisor structure.
Cevap
Migrate the virtual machine to a Type 1 hypervisor installed directly on bare-metal hardware, eliminating host operating system resource contention.
The option specifying migration to a Type 1 hypervisor installed directly on bare-metal hardware is correct because Type 1 hypervisors bypass general-purpose host operating systems entirely. By operating directly on host hardware, the hypervisor eliminates host OS kernel overhead, background service interference, and host driver interrupt latency.
Adım Adım Çözüm
Anahtar Kavram
Type 1 (bare-metal) hypervisors run directly on system hardware without a host operating system, providing lower latency and direct resource management, whereas Type 2 (hosted) hypervisors run as applications on top of an existing host operating system.
Tahmini Süre:2m 0s