Hypervisor Concepts interview questions

1. A.A Type 1 hypervisor installed directly on physical hardware with no underlying OS, giving better performance and security (e.g. ESXi, Hyper-V, Xen)
2. B.a hypervisor running on a host OS (VMware Workstation, VirtualBox)
3. C.A hardware unit (Intel VT-d, AMD-Vi) that translates and isolates device DMA, enabling safe PCI passthrough and SR-IOV to VMs
4. D.a hypervisor running directly on bare metal (ESXi, Hyper-V, KVM, Xen)

Answer + AI explanation with Pro

1. A.Virtual machine monitor (VMM)
2. B.Trap-and-emulate
3. C.Type 1 hypervisor
4. D.Confidential computing attestation

Answer + AI explanation with Pro

1. A.Type 1 hypervisor — A pre-packaged VM image bundling an OS and application, often distributed as an OVA/OVF for quick deployment
2. B.Type 1 hypervisor — Whether a snapshot captures only crash-consistent disk state or an application-consistent state via guest quiescing and VSS/freeze hooks
3. C.Type 1 hypervisor — The operating system that runs inside a virtual machine, unaware it is virtualized except through paravirtual drivers
4. D.Type 1 hypervisor — a hypervisor running directly on bare metal (ESXi, Hyper-V, KVM, Xen)

Answer + AI explanation with Pro

1. A.Software installed in the guest (VMware Tools, qemu-guest-agent, Hyper-V Integration Services) providing paravirtual drivers, time sync, quiescing and graceful shutdown
2. B.a hypervisor running directly on bare metal (ESXi, Hyper-V, KVM, Xen)
3. C.Whether a snapshot captures only crash-consistent disk state or an application-consistent state via guest quiescing and VSS/freeze hooks
4. D.a hypervisor running on a host OS (VMware Workstation, VirtualBox)

Answer + AI explanation with Pro

1. A.Device emulation vs passthrough
2. B.Virtual appliance
3. C.Type 2 hypervisor
4. D.Confidential computing attestation

Answer + AI explanation with Pro

1. A.Type 2 hypervisor — a hypervisor running on a host OS (VMware Workstation, VirtualBox)
2. B.Type 2 hypervisor — Emulation presents a virtual device the hypervisor implements in software, while passthrough hands a real PCI device to one VM via the IOMMU for native speed
3. C.Type 2 hypervisor — a hypervisor running directly on bare metal (ESXi, Hyper-V, KVM, Xen)
4. D.Type 2 hypervisor — The classic virtualization model where privileged guest instructions trap to the VMM which emulates them; fails for x86 sensitive-but-unprivileged instructions, motivating VT-x

Answer + AI explanation with Pro

1. A.Type 1 — the kernel module turns Linux itself into a bare-metal hypervisor
2. B.A technique where the guest OS is modified to make hypercalls to the hypervisor instead of issuing privileged instructions, improving efficiency (classic Xen PV)
3. C.A design where the hypervisor is kept minimal and drivers/management live in a privileged partition or service VM, reducing the trusted computing base (Xen dom0, Hyper-V root partition)
4. D.A hardware unit (Intel VT-d, AMD-Vi) that translates and isolates device DMA, enabling safe PCI passthrough and SR-IOV to VMs

Answer + AI explanation with Pro

1. A.IOMMU
2. B.KVM classification
3. C.overcommit
4. D.Virtual disk

Answer + AI explanation with Pro

1. A.KVM classification — A pre-packaged VM image bundling an OS and application, often distributed as an OVA/OVF for quick deployment
2. B.KVM classification — Type 1 — the kernel module turns Linux itself into a bare-metal hypervisor
3. C.KVM classification — A design where the hypervisor is kept minimal and drivers/management live in a privileged partition or service VM, reducing the trusted computing base (Xen dom0, Hyper-V root partition)
4. D.KVM classification — A file or block object presented to a VM as a physical disk, in formats such as VMDK, VHDX or qcow2

Answer + AI explanation with Pro

1. A.A Type 2 hypervisor that runs as an application on top of a conventional host operating system, relying on the host OS for hardware access (e.g. VirtualBox, VMware Workstation)
2. B.CPU extensions Intel VT-x / AMD-V that accelerate virtualization
3. C.a hypervisor running directly on bare metal (ESXi, Hyper-V, KVM, Xen)
4. D.a hypervisor running on a host OS (VMware Workstation, VirtualBox)

Answer + AI explanation with Pro

1. A.hardware-assisted virtualization
2. B.Snapshot consistency level
3. C.overcommit
4. D.Virtual appliance

Answer + AI explanation with Pro

1. A.hardware-assisted virtualization — CPU extensions Intel VT-x / AMD-V that accelerate virtualization
2. B.hardware-assisted virtualization — A Type 1 hypervisor installed directly on physical hardware with no underlying OS, giving better performance and security (e.g. ESXi, Hyper-V, Xen)
3. C.hardware-assisted virtualization — The classic virtualization model where privileged guest instructions trap to the VMM which emulates them; fails for x86 sensitive-but-unprivileged instructions, motivating VT-x
4. D.hardware-assisted virtualization — allocating more vCPU/vRAM than physical, relying on non-simultaneous peak usage

Answer + AI explanation with Pro

1. A.A technique where the guest OS is modified to make hypercalls to the hypervisor instead of issuing privileged instructions, improving efficiency (classic Xen PV)
2. B.Hardware page-table virtualization (Intel EPT, AMD RVI/NPT) that maps guest physical to host physical memory without costly shadow page tables
3. C.allocating more vCPU/vRAM than physical, relying on non-simultaneous peak usage
4. D.Running a hypervisor inside a virtual machine, exposing virtualization CPU extensions to the guest so it can host its own VMs

Answer + AI explanation with Pro

1. A.Virtual disk
2. B.Second Level Address Translation (SLAT)
3. C.Confidential computing attestation
4. D.overcommit

Answer + AI explanation with Pro

1. A.overcommit — A design where the hypervisor is kept minimal and drivers/management live in a privileged partition or service VM, reducing the trusted computing base (Xen dom0, Hyper-V root partition)
2. B.overcommit — Another name for the hypervisor component that creates, runs and manages virtual machines by mediating access to physical hardware
3. C.overcommit — The operating system that runs inside a virtual machine, unaware it is virtualized except through paravirtual drivers
4. D.overcommit — allocating more vCPU/vRAM than physical, relying on non-simultaneous peak usage

Answer + AI explanation with Pro

1. A.A process where a confidential VM proves to a relying party, via hardware-signed measurements, that it runs unmodified on genuine SEV-SNP or TDX hardware
2. B.A Type 2 hypervisor that runs as an application on top of a conventional host operating system, relying on the host OS for hardware access (e.g. VirtualBox, VMware Workstation)
3. C.A technique where the guest OS is modified to make hypercalls to the hypervisor instead of issuing privileged instructions, improving efficiency (classic Xen PV)
4. D.a hypervisor running on a host OS (VMware Workstation, VirtualBox)

Answer + AI explanation with Pro

1. A.Type 2 hypervisor
2. B.Hosted hypervisor
3. C.KVM classification
4. D.Snapshot consistency level

Answer + AI explanation with Pro

1. A.Hosted hypervisor — The classic virtualization model where privileged guest instructions trap to the VMM which emulates them; fails for x86 sensitive-but-unprivileged instructions, motivating VT-x
2. B.Hosted hypervisor — Type 1 — the kernel module turns Linux itself into a bare-metal hypervisor
3. C.Hosted hypervisor — A Type 2 hypervisor that runs as an application on top of a conventional host operating system, relying on the host OS for hardware access (e.g. VirtualBox, VMware Workstation)
4. D.Hosted hypervisor — CPU extensions (Intel VT-x, AMD-V) that let the hypervisor run guest code directly with a new privilege ring, removing the need for binary translation

Answer + AI explanation with Pro

1. A.CPU extensions Intel VT-x / AMD-V that accelerate virtualization
2. B.A Type 1 hypervisor installed directly on physical hardware with no underlying OS, giving better performance and security (e.g. ESXi, Hyper-V, Xen)
3. C.A Type 2 hypervisor that runs as an application on top of a conventional host operating system, relying on the host OS for hardware access (e.g. VirtualBox, VMware Workstation)
4. D.Emulation presents a virtual device the hypervisor implements in software, while passthrough hands a real PCI device to one VM via the IOMMU for native speed

Answer + AI explanation with Pro

1. A.Bare-metal hypervisor
2. B.overcommit
3. C.Hardware-assisted virtualization
4. D.Guest OS

Answer + AI explanation with Pro

1. A.Bare-metal hypervisor — A Type 1 hypervisor installed directly on physical hardware with no underlying OS, giving better performance and security (e.g. ESXi, Hyper-V, Xen)
2. B.Bare-metal hypervisor — Hardware page-table virtualization (Intel EPT, AMD RVI/NPT) that maps guest physical to host physical memory without costly shadow page tables
3. C.Bare-metal hypervisor — The classic virtualization model where privileged guest instructions trap to the VMM which emulates them; fails for x86 sensitive-but-unprivileged instructions, motivating VT-x
4. D.Bare-metal hypervisor — Another name for the hypervisor component that creates, runs and manages virtual machines by mediating access to physical hardware

Answer + AI explanation with Pro

1. A.Whether a snapshot captures only crash-consistent disk state or an application-consistent state via guest quiescing and VSS/freeze hooks
2. B.Another name for the hypervisor component that creates, runs and manages virtual machines by mediating access to physical hardware
3. C.A process where a confidential VM proves to a relying party, via hardware-signed measurements, that it runs unmodified on genuine SEV-SNP or TDX hardware
4. D.The operating system that runs inside a virtual machine, unaware it is virtualized except through paravirtual drivers

Answer + AI explanation with Pro

1. A.IOMMU
2. B.Virtual machine monitor (VMM)
3. C.Microkernel hypervisor architecture
4. D.Guest OS

Answer + AI explanation with Pro

1. A.Guest OS — A design where the hypervisor is kept minimal and drivers/management live in a privileged partition or service VM, reducing the trusted computing base (Xen dom0, Hyper-V root partition)
2. B.Guest OS — A technique where the guest OS is modified to make hypercalls to the hypervisor instead of issuing privileged instructions, improving efficiency (classic Xen PV)
3. C.Guest OS — The operating system that runs inside a virtual machine, unaware it is virtualized except through paravirtual drivers
4. D.Guest OS — Whether a snapshot captures only crash-consistent disk state or an application-consistent state via guest quiescing and VSS/freeze hooks

Answer + AI explanation with Pro

1. A.Another name for the hypervisor component that creates, runs and manages virtual machines by mediating access to physical hardware
2. B.Whether a snapshot captures only crash-consistent disk state or an application-consistent state via guest quiescing and VSS/freeze hooks
3. C.A Type 2 hypervisor that runs as an application on top of a conventional host operating system, relying on the host OS for hardware access (e.g. VirtualBox, VMware Workstation)
4. D.Running a hypervisor inside a virtual machine, exposing virtualization CPU extensions to the guest so it can host its own VMs

Answer + AI explanation with Pro

1. A.hardware-assisted virtualization
2. B.Virtual machine monitor (VMM)
3. C.KVM classification
4. D.Confidential computing attestation

Answer + AI explanation with Pro

1. A.Virtual machine monitor (VMM) — A Type 2 hypervisor that runs as an application on top of a conventional host operating system, relying on the host OS for hardware access (e.g. VirtualBox, VMware Workstation)
2. B.Virtual machine monitor (VMM) — Another name for the hypervisor component that creates, runs and manages virtual machines by mediating access to physical hardware
3. C.Virtual machine monitor (VMM) — CPU extensions (Intel VT-x, AMD-V) that let the hypervisor run guest code directly with a new privilege ring, removing the need for binary translation
4. D.Virtual machine monitor (VMM) — A hardware unit (Intel VT-d, AMD-Vi) that translates and isolates device DMA, enabling safe PCI passthrough and SR-IOV to VMs

Answer + AI explanation with Pro

1. A.a hypervisor running directly on bare metal (ESXi, Hyper-V, KVM, Xen)
2. B.CPU extensions (Intel VT-x, AMD-V) that let the hypervisor run guest code directly with a new privilege ring, removing the need for binary translation
3. C.Emulation presents a virtual device the hypervisor implements in software, while passthrough hands a real PCI device to one VM via the IOMMU for native speed
4. D.Software installed in the guest (VMware Tools, qemu-guest-agent, Hyper-V Integration Services) providing paravirtual drivers, time sync, quiescing and graceful shutdown

Answer + AI explanation with Pro

1. A.Device emulation vs passthrough
2. B.Hardware-assisted virtualization
3. C.overcommit
4. D.Hosted hypervisor

Answer + AI explanation with Pro

1. A.Hardware-assisted virtualization — Whether a snapshot captures only crash-consistent disk state or an application-consistent state via guest quiescing and VSS/freeze hooks
2. B.Hardware-assisted virtualization — A Type 1 hypervisor installed directly on physical hardware with no underlying OS, giving better performance and security (e.g. ESXi, Hyper-V, Xen)
3. C.Hardware-assisted virtualization — CPU extensions (Intel VT-x, AMD-V) that let the hypervisor run guest code directly with a new privilege ring, removing the need for binary translation
4. D.Hardware-assisted virtualization — a hypervisor running on a host OS (VMware Workstation, VirtualBox)

Answer + AI explanation with Pro