KubeVirt & K8s Virt interview questions

1. A.A Red Hat tool that bulk-migrates VMs from vSphere, Hyper-V, OVA or OpenStack into OpenShift Virtualization
2. B.The KubeVirt object representing one running VM instance, created and managed by a higher-level VirtualMachine spec
3. C.Red Hat's productized KubeVirt that lets OpenShift run traditional VMs next to containers, positioned as a leading VMware migration target
4. D.A CNCF project that runs virtual machines as native Kubernetes objects, scheduling each VM inside a pod so VMs and containers share one orchestrator

Answer + AI explanation with Pro

1. A.KubeVirt
2. B.Dedicated CPU placement
3. C.Hostpath and local storage caveats
4. D.LiveMigrationPolicy

Answer + AI explanation with Pro

1. A.KubeVirt — A CNCF project that runs virtual machines as native Kubernetes objects, scheduling each VM inside a pod so VMs and containers share one orchestrator
2. B.KubeVirt — CRDs that capture and roll back a VM disks and state using CSI volume snapshots.
3. C.KubeVirt — The pod that wraps and supervises a single KubeVirt VM's QEMU/libvirt process inside the Kubernetes node
4. D.KubeVirt — Memory requested as hugepages via the guest memory spec, requiring hugepages preallocated on the node.

Answer + AI explanation with Pro

1. A.Memory requested as hugepages via the guest memory spec, requiring hugepages preallocated on the node.
2. B.The KubeVirt object representing one running VM instance, created and managed by a higher-level VirtualMachine spec
3. C.Red Hat's productized KubeVirt that lets OpenShift run traditional VMs next to containers, positioned as a leading VMware migration target
4. D.CRDs that capture and roll back a VM disks and state using CSI volume snapshots.

Answer + AI explanation with Pro

1. A.Hugepages in KubeVirt
2. B.KubeVirt
3. C.OpenShift Virtualization
4. D.ReadWriteMany requirement for live migration

Answer + AI explanation with Pro

1. A.OpenShift Virtualization — Red Hat's productized KubeVirt that lets OpenShift run traditional VMs next to containers, positioned as a leading VMware migration target
2. B.OpenShift Virtualization — A VirtualMachineInstance is the running pod-like instance; a VirtualMachine is the declarative spec that manages its lifecycle.
3. C.OpenShift Virtualization — Controls which Kubernetes nodes a VMI may schedule on using labels, affinity, and tolerations.
4. D.OpenShift Virtualization — DataVolumes (CDI) import or clone images into PVCs backed by a StorageClass for VM disks.

Answer + AI explanation with Pro

1. A.The pod that wraps and supervises a single KubeVirt VM's QEMU/libvirt process inside the Kubernetes node
2. B.Controls which Kubernetes nodes a VMI may schedule on using labels, affinity, and tolerations.
3. C.Red Hat's productized KubeVirt that lets OpenShift run traditional VMs next to containers, positioned as a leading VMware migration target
4. D.Live migration requires shared ReadWriteMany block storage so both source and target nodes can access the disk.

Answer + AI explanation with Pro

1. A.OpenShift Virtualization
2. B.virt-launcher
3. C.Migration Toolkit for Virtualization (MTV/Forklift)
4. D.virtctl

Answer + AI explanation with Pro

1. A.virt-launcher — The pod that wraps and supervises a single KubeVirt VM's QEMU/libvirt process inside the Kubernetes node
2. B.virt-launcher — A Red Hat tool that bulk-migrates VMs from vSphere, Hyper-V, OVA or OpenStack into OpenShift Virtualization
3. C.virt-launcher — CRDs that capture and roll back a VM disks and state using CSI volume snapshots.
4. D.virt-launcher — KubeVirt VMs on RWO local storage cannot live-migrate because the disk is bound to one node, requiring RWX storage for mobility

Answer + AI explanation with Pro

1. A.A KubeVirt component that imports, uploads or clones disk images into PersistentVolumes via DataVolume resources for VM consumption
2. B.A KubeVirt abstraction that declaratively provisions and populates a PVC for a VM disk, handling import and clone orchestration
3. C.The KubeVirt command-line client for VM lifecycle and console/VNC/SSH access, layered on top of kubectl
4. D.Cluster policy selecting VMs by label and tuning bandwidth, completion timeout, and auto-converge for migrations.

Answer + AI explanation with Pro

1. A.RWX block for live migration
2. B.Containerized Data Importer (CDI)
3. C.virtctl
4. D.VirtualMachineSnapshot and Restore

Answer + AI explanation with Pro

1. A.Containerized Data Importer (CDI) — Red Hat's productized KubeVirt that lets OpenShift run traditional VMs next to containers, positioned as a leading VMware migration target
2. B.Containerized Data Importer (CDI) — A CNCF project that runs virtual machines as native Kubernetes objects, scheduling each VM inside a pod so VMs and containers share one orchestrator
3. C.Containerized Data Importer (CDI) — A KubeVirt component that imports, uploads or clones disk images into PersistentVolumes via DataVolume resources for VM consumption
4. D.Containerized Data Importer (CDI) — Requests exclusive pinned host cores for a VMI to remove scheduling jitter for latency-sensitive workloads.

Answer + AI explanation with Pro

1. A.Cluster policy selecting VMs by label and tuning bandwidth, completion timeout, and auto-converge for migrations.
2. B.A Red Hat tool that bulk-migrates VMs from vSphere, Hyper-V, OVA or OpenStack into OpenShift Virtualization
3. C.The KubeVirt object representing one running VM instance, created and managed by a higher-level VirtualMachine spec
4. D.A KubeVirt abstraction that declaratively provisions and populates a PVC for a VM disk, handling import and clone orchestration

Answer + AI explanation with Pro

1. A.DataVolume
2. B.Live migration with RWX storage
3. C.ReadWriteMany requirement for live migration
4. D.OpenShift Virtualization

Answer + AI explanation with Pro

1. A.DataVolume — A KubeVirt abstraction that declaratively provisions and populates a PVC for a VM disk, handling import and clone orchestration
2. B.DataVolume — A KubeVirt component that imports, uploads or clones disk images into PersistentVolumes via DataVolume resources for VM consumption
3. C.DataVolume — Cluster policy selecting VMs by label and tuning bandwidth, completion timeout, and auto-converge for migrations.
4. D.DataVolume — A VirtualMachineInstance is the running pod-like instance; a VirtualMachine is the declarative spec that manages its lifecycle.

Answer + AI explanation with Pro

1. A.The KubeVirt object representing one running VM instance, created and managed by a higher-level VirtualMachine spec
2. B.Cluster policy selecting VMs by label and tuning bandwidth, completion timeout, and auto-converge for migrations.
3. C.KubeVirt VM live migration needs the disk PVC to be RWX so both the source and target virt-launcher pods can access storage simultaneously
4. D.A KubeVirt abstraction that declaratively provisions and populates a PVC for a VM disk, handling import and clone orchestration

Answer + AI explanation with Pro

1. A.Hostpath and local storage caveats
2. B.ReadWriteMany requirement for live migration
3. C.VirtualMachineInstance (VMI)
4. D.Hugepages in KubeVirt

Answer + AI explanation with Pro

1. A.ReadWriteMany requirement for live migration — The KubeVirt object representing one running VM instance, created and managed by a higher-level VirtualMachine spec
2. B.ReadWriteMany requirement for live migration — KubeVirt VM live migration needs the disk PVC to be RWX so both the source and target virt-launcher pods can access storage simultaneously
3. C.ReadWriteMany requirement for live migration — A Red Hat tool that bulk-migrates VMs from vSphere, Hyper-V, OVA or OpenStack into OpenShift Virtualization
4. D.ReadWriteMany requirement for live migration — CRDs that capture and roll back a VM disks and state using CSI volume snapshots.

Answer + AI explanation with Pro

1. A.Controls which Kubernetes nodes a VMI may schedule on using labels, affinity, and tolerations.
2. B.The KubeVirt command-line client for VM lifecycle and console/VNC/SSH access, layered on top of kubectl
3. C.KubeVirt VMs on RWO local storage cannot live-migrate because the disk is bound to one node, requiring RWX storage for mobility
4. D.Cluster policy selecting VMs by label and tuning bandwidth, completion timeout, and auto-converge for migrations.

Answer + AI explanation with Pro

1. A.VirtualMachineSnapshot and Restore
2. B.Bridge and Multus networking
3. C.KubeVirt
4. D.virtctl

Answer + AI explanation with Pro

1. A.virtctl — Memory requested as hugepages via the guest memory spec, requiring hugepages preallocated on the node.
2. B.virtctl — CRDs that capture and roll back a VM disks and state using CSI volume snapshots.
3. C.virtctl — The KubeVirt command-line client for VM lifecycle and console/VNC/SSH access, layered on top of kubectl
4. D.virtctl — The KubeVirt object representing one running VM instance, created and managed by a higher-level VirtualMachine spec

Answer + AI explanation with Pro

1. A.KubeVirt uses Multus to attach VMs to multiple networks, including bridge or SR-IOV secondary networks for VLAN and high-performance traffic
2. B.A KubeVirt component that imports, uploads or clones disk images into PersistentVolumes via DataVolume resources for VM consumption
3. C.A Red Hat tool that bulk-migrates VMs from vSphere, Hyper-V, OVA or OpenStack into OpenShift Virtualization
4. D.A CNCF project that runs virtual machines as native Kubernetes objects, scheduling each VM inside a pod so VMs and containers share one orchestrator

Answer + AI explanation with Pro

1. A.Migration Toolkit for Virtualization (MTV/Forklift)
2. B.VirtualMachineInstance (VMI)
3. C.RWX block for live migration
4. D.virt-launcher

Answer + AI explanation with Pro

1. A.Migration Toolkit for Virtualization (MTV/Forklift) — Cluster policy selecting VMs by label and tuning bandwidth, completion timeout, and auto-converge for migrations.
2. B.Migration Toolkit for Virtualization (MTV/Forklift) — A Red Hat tool that bulk-migrates VMs from vSphere, Hyper-V, OVA or OpenStack into OpenShift Virtualization
3. C.Migration Toolkit for Virtualization (MTV/Forklift) — The KubeVirt mechanism that moves a running VMI between nodes by starting a target virt-launcher and handing over the QEMU state once memory is synced
4. D.Migration Toolkit for Virtualization (MTV/Forklift) — KubeVirt VM live migration needs the disk PVC to be RWX so both the source and target virt-launcher pods can access storage simultaneously

Answer + AI explanation with Pro

1. A.The KubeVirt object representing one running VM instance, created and managed by a higher-level VirtualMachine spec
2. B.Requests exclusive pinned host cores for a VMI to remove scheduling jitter for latency-sensitive workloads.
3. C.Red Hat's productized KubeVirt that lets OpenShift run traditional VMs next to containers, positioned as a leading VMware migration target
4. D.Controls which Kubernetes nodes a VMI may schedule on using labels, affinity, and tolerations.

Answer + AI explanation with Pro

1. A.DataVolume
2. B.virtctl
3. C.VirtualMachineInstance (VMI)
4. D.virt-launcher

Answer + AI explanation with Pro

1. A.VirtualMachineInstance (VMI) — Requests exclusive pinned host cores for a VMI to remove scheduling jitter for latency-sensitive workloads.
2. B.VirtualMachineInstance (VMI) — Red Hat's productized KubeVirt that lets OpenShift run traditional VMs next to containers, positioned as a leading VMware migration target
3. C.VirtualMachineInstance (VMI) — A KubeVirt abstraction that declaratively provisions and populates a PVC for a VM disk, handling import and clone orchestration
4. D.VirtualMachineInstance (VMI) — The KubeVirt object representing one running VM instance, created and managed by a higher-level VirtualMachine spec

Answer + AI explanation with Pro

1. A.Live migration requires shared ReadWriteMany block storage so both source and target nodes can access the disk.
2. B.The KubeVirt mechanism that moves a running VMI between nodes by starting a target virt-launcher and handing over the QEMU state once memory is synced
3. C.The KubeVirt command-line client for VM lifecycle and console/VNC/SSH access, layered on top of kubectl
4. D.CRDs that capture and roll back a VM disks and state using CSI volume snapshots.

Answer + AI explanation with Pro

1. A.Live migration with RWX storage
2. B.LiveMigrationPolicy
3. C.OpenShift Virtualization
4. D.virt-launcher

Answer + AI explanation with Pro

1. A.Live migration with RWX storage — The pod that wraps and supervises a single KubeVirt VM's QEMU/libvirt process inside the Kubernetes node
2. B.Live migration with RWX storage — A KubeVirt component that imports, uploads or clones disk images into PersistentVolumes via DataVolume resources for VM consumption
3. C.Live migration with RWX storage — The KubeVirt mechanism that moves a running VMI between nodes by starting a target virt-launcher and handing over the QEMU state once memory is synced
4. D.Live migration with RWX storage — KubeVirt VM live migration needs the disk PVC to be RWX so both the source and target virt-launcher pods can access storage simultaneously

Answer + AI explanation with Pro