RATATOSK
← All releases

KubeVirtv1.10.0

Security 7Breaking changes 38Deprecations 1Important fixes 74Enhancements 39Dependency updates 7Other changes 31

Get KubeVirt alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Check before upgrading

Known issues1
Client-side apply of the KubeVirt operator manifest fails

The kubevirts.kubevirt.io CRD exceeds the 256 KiB annotation limit. The note names kubectl apply --server-side and kubectl create as alternatives.

> [!IMPORTANT]
> Installing the `kubevirt-operator.yaml` with client-side `kubectl apply -f kubevirt-operator.yaml` fails because the kubevirts.kubevirt.io CRD now exceeds the 256 KiB annotation limit. Use `kubectl apply --server-side` (or `kubectl create`) for `kubevirt-operator.yaml` instead. See #19980.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Security7medium3Security status unclear2

virt-api port-forward and SSH traffic redirection fixed

medium
AffectsVMIs with a pod network accessed via virtctl port-forward or virtctl ssh

When the launcher pod IP could not be resolved, virt-api used an unvalidated interface IP reported by the guest agent, allowing traffic to be redirected to arbitrary reachable endpoints. Port-forward and SSH now dial only the launcher pod IP, and VMIs without a pod network are rejected before websocket upgrade or dialing.

Show release-note lines
- [PR #18753][orelmisan] Fix SSRF vulnerability (CVE-2026-13318) in virt-api port-forward that allowed a malicious QEMU guest agent to redirect virtctl port-forward and ssh traffic to arbitrary network endpoints. virt-api now dials only the launcher pod IP and never the guest-agent-reported interface IP.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

virt-api port-forward protocol checks block SSRF

medium
Affectsvirt-api port-forward and SSH traffic(Inferred)

A malicious QEMU guest agent could redirect virtctl port-forward and SSH traffic to arbitrary network endpoints because the forwarded protocol was passed to net.Dial unchecked. Forwarded protocols other than tcp and udp now receive a BadRequest error.

Show release-note lines
- [PR #18753][orelmisan] Fix SSRF vulnerability (CVE-2026-13318) in virt-api port-forward that allowed a malicious QEMU guest agent to redirect virtctl port-forward and ssh traffic to arbitrary network endpoints. virt-api now dials only the launcher pod IP and never the guest-agent-reported interface IP.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

virt-api port-forward target selection fixed

medium
AffectsVMIs connected to the pod network

When the virt-launcher pod is multihomed or its binding leaves no address on the pod-side link, the reported interface IP can be unreachable from virt-api, preventing the port-forward tunnel from being established. Port-forward now dials the launcher pod IP when available, falling back to the interface-status IP; existing core bindings have no observable change, and VMIs without a pod network retain the prior behavior.

Show release-note lines
- [PR #19019][lllamnyp] virt-api: the port-forward subresource (used by `virtctl port-forward` and `virtctl ssh`) now dials the virt-launcher pod IP for VMIs connected to the pod network, instead of the first IP reported in the VMI interface status. The virt-api cluster role gains the `watch` verb on pods.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Migration identity sharing limited to proxy-enabled setups

AffectsKubeVirt setups with the migration proxy disabled

Previously, the synchronization controller pod received the migration identity even when the migration proxy was disabled. It now receives that identity only when the proxy is enabled.

Show release-note lines
- [PR #19490][awels] Only add virt-handler migration identity to synchronization controller if proxy is enabled.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

VM admission blocks restricted ContainerPath paths

Security status unclear
AffectsVM/VMI ContainerPath volumes

Submissions using paths matching /run/kubevirt* or /run/libvirt* are rejected at admission. These restrictions match the existing /var/run restrictions.

Show release-note lines
- [PR #19251][mhenriks] Check ContainerPathVolume feature gate at admission time.  Reject /run/kubevirt* and /run/libvirt* paths.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

VMI name label added to GPU info metric

Security status unclear
Affectsinstallations scraping or querying kubevirt_vmi_gpu_info(Inferred)

Before this release, kubevirt_vmi_gpu_info did not include a VMI name label.

Show release-note lines
- [PR #18902][machadovilaca] Add name label to kubevirt_vmi_gpu_info
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Export server token timing side channel fixed

Affectssetups using the export server token check

The token check did not use a constant-time comparison, creating a timing side channel. It now uses a constant-time comparison.

Show release-note lines
- [PR #18200][naruto-lgtm] Fixed a timing side channel in the export server token check by switching to a constant-time comparison.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Breaking changes38

Memory-dump PVC excluded from VM snapshots and exports

AffectsVM snapshots or exports with a memory-dump PVC attached(Inferred)

Restoring a snapshot or export did not restore the dump PVC even before this change.

Evidence“Snapshots and exports no longer include the dump PVC (restore never restored it anyway).” kubevirt/kubevirt/pull/19550 ↗
Show release-note lines
- [PR #19550][Acedus] Memory dumps are attached as utility volumes and require the UtilityVolumes feature gate, which is promoted to Beta and enabled by default. VM snapshots and exports no longer include the memory dump PVC.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

VirtualMachineBackup type reporting moves to per-volume status

Affectscheckpoint-based VirtualMachineBackups with disks missing the base checkpoint bitmap

Previously, one disk missing its base checkpoint bitmap caused the entire backup to fail, including disks with valid bitmaps. Now that disk is backed up in full while the others retain their incremental deltas.

Show release-note lines
- [PR #19056][Acedus] VirtualMachineBackup no longer fails when a disk has lost the base checkpoint's bitmap; that disk is backed up in full and type is now reported per volume in `status.includedVolumes[].type`, replacing the removed `status.type`.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

VirtualMachineBackup backup type reported per volume

Affectsclients or automation reading VirtualMachineBackup status(Inferred)

Previously, if a disk in a checkpoint-based backup had lost the base checkpoint's bitmap, it failed the entire backup. That disk is now backed up in full instead.

Show release-note lines
- [PR #19056][Acedus] VirtualMachineBackup no longer fails when a disk has lost the base checkpoint's bitmap; that disk is backed up in full and type is now reported per volume in `status.includedVolumes[].type`, replacing the removed `status.type`.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

io.kubevirt.disk.name now uses VM volume names

Affectsexported OCI artifacts with disk layers(Inferred)

Previously, the annotation held a sanitized PVC-derived mount-directory name rather than the VM-spec volume name, so it did not identify the VM volume. For example, a rootdisk volume backed by fedora-vm-rootdisk is now labeled rootdisk.

Evidence“The volume name is passed to the exporter pod and the layer is annotated with it. A volume `rootdisk` backed by claim `fedora-vm-rootdisk` is annotated `rootdisk`.” kubevirt/kubevirt/pull/19066 ↗
Show release-note lines
- [PR #19066][0xFelix] The io.kubevirt.disk.name annotation of exported OCI artifacts now carries the volume name from the VM instead of the PersistentVolumeClaim name
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

User-defined HostDisk volumes excluded from CBT

AffectsCBT with user-defined HostDisk volumes

When a missing DiskOrCreate image was silently recreated, its CBT overlay could keep describing a disk that no longer existed. HostDisk volumes no longer count toward CBT memory overhead.

Evidence“Only PVC and DataVolume volumes are eligible for CBT. User-defined HostDisk volumes are no longer tracked, and no longer count towards CBT's memory overhead.” kubevirt/kubevirt/pull/19410 ↗
Show release-note lines
- [PR #19410][Acedus] HostDisk volumes are no longer eligible for changed block tracking.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

virt-launcher-monitor no longer honors VIRT_LAUNCHER_LOG_VERBOSITY

Affectssetups that configure VIRT_LAUNCHER_LOG_VERBOSITY for virt-launcher-monitor(Inferred)

Previously, a valid integer value set the Go monitor’s log verbosity. The rewritten C monitor does not use the configured value to set its verbosity.

Evidence“- no `VIRT_LAUNCHER_LOG_VERBOSITY` in the monitor” kubevirt/kubevirt/pull/19240 ↗
Show release-note lines
- [PR #19240][vladikr] virt-launcher-monitor is rewritten in C to reduce memory footprint to about 2Mi
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Persistent-reservation LUNs now default to SCSI and reject non-SCSI buses

AffectsLUN disks with persistent reservation enabled
Evidence“Default bus to SCSI when reservation is true and bus is unset, and reject with a validation error when reservation is true with an explicitly non-SCSI bus.” kubevirt/kubevirt/pull/18267 ↗
Show release-note lines
- [PR #18267][akalenyu] Default LUN bus to SCSI when persistent reservation is enabled
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Software emulation now requires an explicit policy

AffectsKubeVirt clusters using Software Emulation or emulation policies for VMs

Previously, software emulation was controlled by a cluster-wide on/off behavior; it is now used only when selected through an emulation policy. Existing behavior is retained when the KubeVirt CR sets spec.configuration.emulationPolicy: Software.

Evidence“Action Required: Add `spec.configuration.emulationPolicy: Software` to kubevirt CR to keep existing behaviour if using Software Emulation” kubevirt/kubevirt/pull/19244 ↗
Show release-note lines
- [PR #19244][jschintag] Add configuration option for cluster wide and per VM emulation (Alpha Stage).
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Istio proxy termination removed from virt-launcher-monitor

AffectsKubeVirt setups using Istio sidecars
Action requiredIstio 1.27 or later, or native sidecar mode.

With legacy Istio injection, Envoy ran as a regular container and could keep the pod alive after the main container exited. virt-launcher-monitor no longer terminates the proxy during shutdown.

Show release-note lines
- [PR #19239][akalenyu] Istio sidecar proxy termination is no longer handled by virt-launcher-monitor; Istio >= 1.27 is required with kubevirt (alternatively, use native sidecar mode)
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Separate pull-mode endpoint links in VirtualMachineBackup status

AffectsVirtualMachineBackup status for pull-mode backups

When a pull-mode VirtualMachineExport has both internal and external links, backup status previously exposed only one set, losing the other. The old EndpointCert, DataEndpoint, and MapEndpoint fields are removed; each new link entry has its own CA certificate and per-volume data and map URLs.

Evidence“The existing fields (`EndpointCert`, `DataEndpoint`, `MapEndpoint`) are removed. Consumers of pull-mode backups should use `status.links.internal` and/or `status.links.external` instead.” kubevirt/kubevirt/pull/18537 ↗
Show release-note lines
- [PR #18537][davmarro] Add structured `links` field to `VirtualMachineBackup` status exposing both internal and external export endpoints for pull-mode backups. The existing endpoint fields are removed.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

VSOCK feature gate graduated to Beta and enabled by default

Affectsinstallations using or configuring the VSOCK feature gate, and workloads using VSOCK(Inferred)
Show release-note lines
- [PR #19155][0xFelix] The VSOCK feature gate graduated to Beta and is now enabled by default.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

KubeVirt stops using the legacy cpumanager node label

Affectsautomation or scheduling rules that use the legacy cpumanager node label on nodes updated by virt-handler(Inferred)

The kubevirt.io/cpumanager label remains in use for Pods.

Show release-note lines
- [PR #19100][xpivarc] Label "cpumanager" is no longer used
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

CBT dirty-bitmap overhead included in VM memory calculations

AffectsVMs with CBT enabled

Previously, their memory calculations omitted the memory needed for CBT dirty bitmaps, understating the requirement. The calculation now includes overhead for each included disk, accounting for CBT-eligible volumes, active backup trackers, and a buffer for dynamic growth.

Show release-note lines
- [PR #18416][Acedus] VMs with CBT now correctly factor in the required memory overhead for each of their included disks.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Custom seccomp profile installation no longer gated

Affectsclusters using the KubevirtSeccompProfile gate or relying on KubeVirt's custom seccomp profile

Before this release, KubeVirt installed the profile only when KubevirtSeccompProfile was explicitly enabled; it is now installed even when the gate is disabled.

Evidence“**Before:** The `KubevirtSeccompProfile` feature gate is at Beta. The custom seccomp profile is only installed when the feature gate is explicitly enabled, and operator tests verify configuration statically (file presence, pod annotation). **After:** The `KubevirtSeccompProfile` feature gate graduates to GA. The custom seccomp profile is always installed, the feature gate check is removed, and three hardening improvements are included:” kubevirt/kubevirt/pull/18888 ↗
Show release-note lines
- [PR #18888][dankenigsberg] Graduate the KubevirtSeccompProfile feature gate to GA. The custom seccomp profile is now always installed. Tighten profile file permissions to 0600, and write it atomically.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Network resource injection is always on through Network Resources Injector

Affectsinstallations using network resource injection for NetworkAttachmentDefinition-backed interfaces

The ExternalNetResourceInjection feature gate had been enabled by default since v1.9, but installations that disabled it can no longer opt out. virt-controller no longer queries NetworkAttachmentDefinition objects or injects network resource requests into launcher pods, and its ClusterRole no longer grants get access to k8s.cni.cncf.io network-attachment-definitions.

Evidence“The `ExternalNetResourceInjection` FG has been Beta since v1.8.0 and enabled by default since v1.9. It disables virt-controller's query of `NetworkAttachmentDefinition` objects and the deployment of NAD RBAC rules by virt-operator. This PR graduates it to GA, making this behavior always on. virt-controller no longer queries `NetworkAttachmentDefinition` objects, injects network resource requests into the launcher pod, or holds the `k8s.cni.cncf.io network-attachment-definitions` get permission.” kubevirt/kubevirt/pull/18497 ↗
Show release-note lines
- [PR #18497][orelmisan] ExternalNetResourceInjection graduated to GA. virt-controller no longer queries NetworkAttachmentDefinition objects or injects network resource requests into the launcher pod. The k8s.cni.cncf.io network-attachment-definitions get rule is
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

VM migration now uses hashed interface names

AffectsVMs with ordinal network or tap interface names, and automation using --upgrade-ordinal-ifaces
Action requiredAffected VMs are converted during live migration; no manual intervention is required.

Previously, migration targets could retain the source pod’s ordinal interface names, and the pre-migration hook was gated. The --upgrade-ordinal-ifaces flag is no longer available.

Evidence“Migration targets will no longer preserve ordinal pod interface names from the source pod - the hashed scheme is always used. The pre-migration hook that converts ordinal tap names to hashed equivalents now runs unconditionally” kubevirt/kubevirt/pull/18317 ↗
Show release-note lines
- [PR #18317][orelmisan] Graduate the PodSecondaryInterfaceNamingUpgrade feature gate to GA. The pre-migration hook that converts ordinal network interface names to hashed equivalents now runs unconditionally.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

QEMU overhead estimate increased for VMI memory requests

AffectsVMI pods using the KVM or MSHV hypervisor backend

The QEMU process overhead estimate rises from 30Mi to 50Mi, adding 20Mi to each VMI pod memory request.

Show release-note lines
- [PR #18388][dasionov] Bumped QEMU process memory overhead from 30Mi to 50Mi, increasing VMI pod memory requests by 20Mi to reflect actual QEMU RSS requirements with current QEMU versions.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Node hooks now honor plugin-level conditions

Affectsnode hooks configured with a plugin-level Spec.Condition(Inferred)

This brings their condition handling in line with domain hooks.

Show release-note lines
- [PR #18414][iholder101] Fix CallNodeHooks to evaluate plugin-level Spec.Condition, ensuring consistent behavior between domain hooks and node hooks.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Global -v registration removed from kubevirt.io/client-go/log

Affectscode importing kubevirt.io/client-go/log

Importing the package used to panic when another imported package, such as glog or klog, had already registered -v on flag.CommandLine. The flag is now kept in a package-private FlagSet, so flag.CommandLine.Lookup("v") no longer returns it; log.VerbosityFlag() exposes it instead.

Evidence“The `-v` flag is registered on a package-private `FlagSet` instead of the global `flag.CommandLine`. A new `VerbosityFlag()` function is exported so that consumers can bridge it into pflag without going through `flag.CommandLine`. All 8 internal call sites are updated. Importing `kubevirt.io/client-go/log` no longer registers any flags on the global `flag.CommandLine`, eliminating the conflict entirely regardless of `init()` ordering.” kubevirt/kubevirt/pull/18294 ↗
Show release-note lines
- [PR #18294][guzalv] client-go/log: The `-v` verbosity flag is no longer registered on `flag.CommandLine` during `init()`. External consumers that used `flag.CommandLine.Lookup("v")` to obtain the verbosity flag must switch to `log.VerbosityFlag()`. This eliminates panics when importing `kubevirt.io/client-go` alongside packages that also register a `-v` flag (e.g. glog, klog).
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Memory dumps now use VMI utility volumes

Affectssetups using memory dumps

Previously, a dump added a MemoryDump volume to both the VM template and vmi.spec.volumes; it now attaches its PVC to the VMI without changing the template. If the VMI stops or restarts during a dump, the dump fails rather than continuing on the new VMI; dumps already in progress during the upgrade finish and are then detached.

Evidence“A memory dump request attaches its PVC to the VMI as a utility volume of type `MemoryDump`, nothing is written to the VM template. A dump still in progress when its VMI stops or restarts fails instead of dumping the new VMI. Dumps that were in progress on it during the upgrade finish, then it's detached.” kubevirt/kubevirt/pull/19550 ↗
Show release-note lines
- [PR #19550][Acedus] Memory dumps are attached as utility volumes and require the UtilityVolumes feature gate, which is promoted to Beta and enabled by default. VM snapshots and exports no longer include the memory dump PVC.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

VGPULiveMigration renamed to MDevVGPULiveMigration for mdev-based vGPU live migration

Affectssetups enabling the Alpha feature gate for mdev-based vGPU live migration
Evidence“Mdev-based vGPU live migration uses `MDevVGPULiveMigration`.” kubevirt/kubevirt/pull/19546 ↗
Show release-note lines
- [PR #19546][dasionov] Renamed the alpha feature gate for mdev-based vGPU live migration from VGPULiveMigration to MDevVGPULiveMigration.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Removal of domainSpec from launcher hook conditions

Affectslauncher hook condition expressions that reference domainSpec(Inferred)

Previously, hook conditions could reference both the VMI and domainSpec. Conditional domain mutation can still use CEL's has() operator.

Evidence“In addition, Launcher hook `condition` expressions could also reference `domainSpec` in addition to the VMI, which both complicated the code and was wrong because on certain situations the domain did not exist yet, it is not relevant for most hook points and it's a low-level libvirt-coupled variable which we don't want to commit to.” kubevirt/kubevirt/pull/19403 ↗
Show release-note lines
- [PR #19403][iholder101] Add PreBoot and PreMigrationSource sidecar launcher hook points for plugins.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Preparation-time live migration aborts now cancel the migration

Affectslive migrations

Previously, an abort during domain preparation or a PreMigrationSource hook reported AbortFailed and the migration continued; it now cancels the migration and reports AbortSucceeded. During the short interval after hand-off but before libvirt's migration job is observable, aborts still report AbortFailed and virt-handler retries.

Evidence“Also, there's a small behavior change for all migrations (with or without plugins): an abort that arrives while the migration is being prepared (domain preparation or `PreMigrationSource` hooks) now cancels it and reports `AbortSucceeded`, where it previously reported `AbortFailed` and the migration continued. A short window remains between the hand-off and libvirt's migration job becoming observable; an abort landing there still reports `AbortFailed`, and virt-handler retries.” kubevirt/kubevirt/pull/19403 ↗
Show release-note lines
- [PR #19403][iholder101] Add PreBoot and PreMigrationSource sidecar launcher hook points for plugins.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

VM/VMI admission rejection of new ContainerPath use with ContainerPathVolume disabled

AffectsVM/VMI workloads using ContainerPath while the ContainerPathVolume feature gate is disabled

Before this change, VM/VMI admission did not check the gate for new usage, though a controller-side check remained for VMIs admitted before the gate was disabled. Updates to objects already using ContainerPath remain allowed.

Evidence“Rejects new ContainerPath usage at VM/VMI admission when the feature gate is disabled, while allowing updates to objects already using it.” kubevirt/kubevirt/pull/19251 ↗
Show release-note lines
- [PR #19251][mhenriks] Check ContainerPathVolume feature gate at admission time.  Reject /run/kubevirt* and /run/libvirt* paths.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

DRA ResourceClaim VMIs marked non-migratable

AffectsVMIs with DRA networks backed by ResourceClaim while NetworkDevicesWithDRA is enabled

A ResourceClaim is bound to a specific allocation, which the migration target pod cannot reserve again.

Evidence“VerifyVMIMigratable now rejects the former. The check is guarded by the NetworkDevicesWithDRA feature gate, threaded in from virt-handler, so behavior is unchanged when the gate is disabled.” kubevirt/kubevirt/pull/19468 ↗
Show release-note lines
- [PR #19468][orelmisan] VMI whose DRA network is backed by a ResourceClaim (rather than a ResourceClaimTemplate) are now reported as non-migratable.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

KubeVirt infrastructure containers now use read-only root filesystems

AffectsKubeVirt infrastructure containers other than virt-handler and the virt-launcher init container
Action requiredNo writable /tmp volume is required; certificates are loaded directly from mounted Secret paths.

Before this release, the included containers ran without readOnlyRootFilesystem: true, and virt-api created an unused temporary certificate directory. Certificates are loaded directly from mounted Secret paths, and no writable /tmp volume is added.

Evidence“KubeVirt containers (`virt-operator`, `virt-api`, `virt-controller`, `virt-exportproxy`, and `virt-synchronization-controller`) run without `readOnlyRootFilesystem: true`, triggering compliance scan findings.” kubevirt/kubevirt/pull/18853 ↗
Show release-note lines
- [PR #18853][davmarro] Enable readOnlyRootFilesystem for all KubeVirt infrastructure containers
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Deprecated virtctl create vm volume flags removed

AffectsInvocations of virtctl create vm using --volume-blank, --volume-datasource, or --volume-clone-pvc(Inferred)

Volume creation now uses --volume-import with type:blank, type:ds, or type:pvc in place of the removed flags.

Show release-note lines
- [PR #19362][NoamBerkoLaor] Removed deprecated virtctl create vm flags --volume-blank, --volume-datasource, and --volume-clone-pvc. Use --volume-import with type:blank, type:ds, or type:pvc instead.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

New virt-export Services use headless port 8443

Affectssetups creating new VMExports

Links for new exports use :8443, while existing ClusterIP exports continue to use :443. Clients that hardcode https://virt-export-*.svc:443 break for new exports; clients that follow status.links continue to work.

Evidence“New exports are not ClusterIP on `:443`. Clients that hardcode `https://virt-export-*.svc:443` will break for those. Clients that follow `status.links` should be fine. Leftover ClusterIP exports stay on `:443`.” kubevirt/kubevirt/pull/18606 ↗
Show release-note lines
- [PR #18606][OOsemka] Make new virt-export Services headless on port 8443 so virt-exportproxy can reach exporters across isolated networks. Existing ClusterIP/443 export Services are left in place. Internal VMExport links include the Service dial port (:8443 or :443).
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Plugin hooks move to spec.launcherHooks

AffectsPlugin objects using spec.domainHooks or PreVMStop(Inferred)

Previously, spec.domainHooks did not require explicit hook points, and the stop hook point was named PreVMStop; launcher hooks now require explicit hook points and use OnVMStop.

Show release-note lines
- [PR #19160][iholder101] Plugin's spec.domainHooks is renamed to spec.launcherHooks. Launcher hooks now require explicit hook points. PreVMStop is renamed to OnVMStop.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

virt-handler /v1/vmstats switches from GET to POST

Affectsclients calling virt-handler's /v1/vmstats endpoint(Inferred)

Previously, one VMStatsRequest applied to every VMI on the node, with stats categories selected through query parameters. Requests now use a JSON body to specify stats categories for each VMI.

Evidence“virt-handler GetVMStats accepts a per-VMI VMStatsRequest body, allowing the caller to filter which VMIs to collect from and specify the stats categories it needs on a per-VMI basis, rather than one set applied to every VMI on the node, so it can collect different data for different VMIs in a single call.” kubevirt/kubevirt/pull/18938 ↗
Show release-note lines
- [PR #18938][machadovilaca] Accept a per-VMI VMStatsRequest body in virt-handler GetVMStats
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

GPU memory-copy recording rule renamed to vmi:kubevirt_vmi_gpu_mem_copy_utilization_ratio:sum

Affectsmonitoring queries and dashboards using vmi:kubevirt_vmi_gpu_mem_copy_util:sum(Inferred)

The previous recording-rule name was vmi:kubevirt_vmi_gpu_mem_copy_util:sum.

Evidence“-| vmi:kubevirt_vmi_gpu_mem_copy_util:sum | Recording rule | Gauge | Memory utilization (ratio, 0-1) of the GPU passed through to a virtual machine instance. |” kubevirt/kubevirt/pull/19144 ↗
Show release-note lines
- [PR #19144][machadovilaca] Add GPU utilization time and active engine time recording rules
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

client-go KubeVirt subresource client helpers removed

Affectsclient-go applications or tools calling GetKubevirtSubresourceClient or GetKubevirtSubresourceClientFromFlags(Inferred)

The functions provided a way to construct and return a KubeVirt subresource client.

Show release-note lines
- [PR #18874][xpivarc] client-go: GetKubevirtSubresourceClient is removed
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

DRA networks reject SR-IOV binding

AffectsDRA networks configured with SR-IOV interfaces

Previously, SR-IOV binding with DRA networks could be used, with virt-launcher resolving PCI addresses from DRA device metadata for passthrough. These interfaces must now use binding plugins.

Evidence“It is no longer possible to use SR-IOV binding with DRA networks - the network admitter rejects them and only allows interfaces using binding plugins.” kubevirt/kubevirt/pull/18451 ↗
Show release-note lines
- [PR #18451][orelmisan] SR-IOV interfaces are no longer supported with DRA networks.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

LibvirtHooksServerAndClient graduates to GA and is always enabled

Affectssetups configuring LibvirtHooksServerAndClient or using its domain-mutation hooks for live migration

Previously, the domain-mutation hook mechanism was a Beta feature that had to be explicitly enabled; the hooks adjust tap device names during migration.

Evidence“Graduate the `LibvirtHooksServerAndClient` feature gate (VEP-141) to GA.” kubevirt/kubevirt/pull/18687 ↗
Show release-note lines
- [PR #18687][Barakmor1] Graduate LibvirtHooksServerAndClient feature gate to GA
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Stall detector API field types changed

Affectsclusters upgrading from v1.9 with MigrationStallDetection enabled, and SDKs importing v1.9 StallDetectorOptions

The four factor fields change from *string to *resource.Quantity, while StallProgressTimeout and SwitchoverTimeout change from *uint64 to *int64. These changes can break cluster upgrades with MigrationStallDetection enabled and cause compile-time errors in SDKs importing the v1.9 type.

Evidence“**Backward compatibility note:** These changes are NOT strictly backward compatible. At the API level, these changes break API SDK since anyone importing kubevirt.io/api/core/v1 from v1.9 and using StallDetectorOptions would see compile-time breakage when upgrading (e.g. *string -> *resource.Quantity). But at the serialization/upgrade level for API they ARE compatible. On the wire, MigrationOptions changes are breaking and thus this will break cluster upgrades if someone has the FG enabled when upgrading 1.9->1.10.” kubevirt/kubevirt/pull/18303 ↗
Show release-note lines
- [PR #18303][Aseeef] BREAKING CHANGE: Modifies internal on-the-wire API fields for the stall detector feature; MigrationStallDetection FG must be disabled for cluster upgrades to succeed.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

PCI root ports for non-NIC devices made non-hotpluggable

AffectsVMs with PCI root ports hosting non-NIC devices

Guest OS hotplug mechanisms, such as Windows’ “Safely Remove Hardware” menu, could eject critical devices including disks, the memory balloon, RNG, and watchdog. NIC ports and empty ports reserved for future hotplug remain available.

Show release-note lines
- [PR #17605][dasionov] Bug fix: Prevent guest OS from ejecting critical PCI devices (disks, memory balloon, RNG, watchdog) via hotplug mechanisms like the Windows "Safely Remove Hardware" tray menu. PCI root ports hosting non-NIC devices are now marked as non-hotpluggable, while NIC ports and empty ports reserved for future hotplug remain available.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Slirp network binding plugin sidecar image removed

Affectssetups referencing or using the slirp network binding plugin sidecar image
Show release-note lines
- [PR #18613][orelmisan] Removed the slirp network binding plugin sidecar image. The plugin had no known consumers.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

RamFB display validation rejects templates with multiple vGPUs

AffectsVirtualMachine and VirtualMachineInstanceReplicaSet templates with vGPUs whose ramFB is present and enabled is unset

Previously, a template with more than one such vGPU could be accepted at creation and fail later when its VMI was created.

Show release-note lines
- [PR #18542][thc1006] RamFB display validation now treats a vGPU whose ramFB is present with its enabled field unset as an enabled display, matching the API default. A VirtualMachine or VirtualMachineInstanceReplicaSet template with more than one such vGPU is now rejected at creation instead of being accepted and failing later when its VMI is created.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Deprecations1

Legacy guest-agent SSH-key setting deprecated

AffectsVMs using the legacy guest-agent guest-file-write flow to set SSH keys in ~/.ssh/authorized_keys
Removed innot stated

Previously, this flow wrote the SSH key directly to ~/.ssh/authorized_keys without a deprecation warning. In this release, using it raises a warning in VMI conditions and an event.

Show release-note lines
- [PR #13881][akrejcir] Deprecated old method to set SSH key in a VM.
github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Important fixes74Silent failure4

  • SMMUv3 IOMMU ssidsize handling fixed
    AffectsGrace IOVirtualization VMIs for which guest definition plugin hooks run

    Guest definition plugin hooks now preserve these VMIs' SSID size and IOMMU driver attributes.

    - [PR #19862][kubevirt-bot] Bump libvirtxml to v1.12007.0 and fix the smmuv3 IOMMU ssidsize attribute, so Grace IOVirtualization VMIs get their SSID size and keep their IOMMU driver attributes when guest definition plugin hooks run.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • CBT overlays now distinguish PVCs per volume
    Affectssetups using CBT incremental backups

    Previously, when a volume pointed at a different PVC, its overlay could be reused and produce an incorrect incremental backup. In that situation, the backup is now Full instead.

    - [PR #19688][kubevirt-bot] CBT overlays are now keyed by volume and PVC name. Pointing a volume at a different PVC triggers a Full backup instead of an incorrect incremental.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • OCI export archives preserve Image Indexes on registry push
    AffectsKubeVirt OCI export archives

    When exported archives were pushed with skopeo copy --multi-arch=all, the registry could receive a plain manifest that lost platform information; oras copy --from-oci-layout vm.oci.tar:latest could also fail to resolve latest. Archives now store the Image Index as a blob and reference it from index.json with ref.name: latest, so pushes produce an Image Index in the registry.

    - [PR #19485][0xFelix] Exported OCI archives now contain the Image Index as a blob referenced from index.json with ref.name "latest", so pushing them creates an Image Index in the registry
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Dedicated-CPU VM host CPU reservation overcount fixedSilent failure
    AffectsDedicated-CPU VMIs combining supplementalPool IO threads with EmulatorThreadCompleteToEvenParity

    An odd IO-thread count could silently reserve one extra host CPU; the example requested 11 instead of the correct 10. The reservation now counts guest vCPUs, IO threads, and the emulator thread once.

    - [PR #19228][Sreeja1725] Alpha: Add CPUsWithDRA to provision dedicated VMI CPUs via a DRA CPU driver instead of kubelet's CPU manager.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • virt-handler preserves externally managed mediated devices
    Affectssetups with externally created mediated devices, including DRA-owned vfio-ap devices and devices supplied by a GPU operator

    When mediatedDeviceTypes was empty, virt-handler's periodic sweep could delete unknown mediated devices, leaving the guest AP bus empty while the VMI stayed Ready. It now preserves externally created devices, while clearing mediatedDeviceTypes still removes KubeVirt-created types.

    - [PR #19099][HarshithaMS005] virt-handler no longer deletes mediated devices it did not create, so DRA-owned vfio-ap devices are not torn out from under running VMs
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Incremental pull-mode backup maps include previously skipped changed blocksSilent failure
    Affectsincremental pull-mode backups on fragmented disks

    When block-allocation and dirty-bitmap ranges ended at different offsets, the merge could skip changed extents between them, leaving backups incomplete without reporting an error. The map-generation loop now resumes from the offset it emitted, so those skipped ranges are requested and included.

    - [PR #19315][Acedus] Fix: incremental pull-mode backups no longer silently leave out changed blocks from the backup map on fragmented disks.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Common-instancetypes version label preserved in captured ControllerRevisions
    Affectsreferenced instancetype or preference objects with the instancetype.kubevirt.io/common-instancetypes-version label

    When one of these objects was captured into a ControllerRevision, its label was dropped. Captured revisions now retain the label, including across upgrades.

    - [PR #19006][lyarwood] Propagate the `instancetype.kubevirt.io/common-instancetypes-version` label from referenced instancetype and preference objects to their captured `ControllerRevision` metadata labels.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • virt-launcher resets guest-agent VMStats caches on domain reboot
    AffectsVMStats collection with the VMStatsCollector feature gate and guest-agent data

    After a guest OS reboot, VMStats could return stale hostname, OS, or network-interface data until the cache TTL expired. When libvirt reports a domain reboot, the next VMStats request fetches fresh guest-agent data.

    - [PR #19169][0xFelix] VMStats guest agent data is refreshed after a guest OS reboot instead of being served from cache until its TTL expires
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Invalid container disk image errors surfaced on VMs and VMIs
    AffectsVMs configured with containerDisk.image

    When containerDisk.image has an incorrect image reference and the virt-launcher init container enters InvalidImageName, the VM previously stayed in Starting without reflecting the error on the VMI. The VMI now reports reason InvalidImageName, the VM displays ErrImagePull, and VM pool autoheal may apply in this condition.

    - [PR #18872][ameya-keskar] Report InvalidImageName container disk errors on the VMI and surface ErrImagePull on the VM instead of leaving the VM stuck in Starting. Pool autoheal for VM's may apply, on the error condition, where it did not before.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Guest clock synchronization fixed for repeated unpauses and migrations
    AffectsVMIs that undergo repeated pause/unpause cycles or migration finalization

    The one-time sync.Once guard meant setGuestTime() ran only once per VMI lifetime, leaving later unpauses or migration finalization without time synchronization.

    - [PR #19089][jean-edouard] Guest clock now properly syncs after multiple pause/unpause
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Single attachment pod for utility and hotplug volumes
    AffectsVMs using both utility volumes and hotplug volumes

    Using both volume types could create two hotplug attachment pods. The single pod contains the appropriate mounts and devices for the volumes used.

    - [PR #18843][awels] BugFix: Prevent duplicate attachment pods when both utility volumes and hotplug volumes are used in a single VM
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • VMBackup status loss on finalizer addition fixed
    AffectsVMBackup resources whose controller adds a finalizer(Inferred)
    - [PR #18843][awels] BugFix: Prevent duplicate attachment pods when both utility volumes and hotplug volumes are used in a single VM
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Migration failure status race fixedSilent failure
    Affectsmigrations during source ownership transfer

    When SourceNode was set before TargetNode, a race could mark a migration as failed even though it was fine. The ownership-transfer logic now waits for the domain-migrated condition before taking the unknown-host failure path.

    - [PR #18604][awels] BugFix: Fixed race condition where target node and source fields were racing which could cause a migration failed.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • virt-handler honors --kubelet-root for CPU Manager detection
    Affectsclusters with a non-default kubelet root directory, including k3s, k0s, and MicroK8s

    Previously, virt-handler ignored --kubelet-root when checking whether CPU Manager was enabled and looked for cpu_manager_state at the default path, causing incorrect node labeling.

    - [PR #16346][ram2valar] Fixed a bug where virt-handler ignored the --kubelet-root flag when detecting whether CPU Manager is enabled, causing incorrect node labeling on clusters with a non-default kubelet root directory (e.g. k3s, k0s, MicroK8s).```
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Suspected orphaned storage recording rule metric reference fixed
    Affectsinstallations using the pvc:kubevirt_suspected_orphaned_storage_bytes:info recording rule

    The rule referenced kube_pod_spec_volumes_persistentvolumeclaims, which does not exist, so that input could not contribute to its result. It now uses kube_pod_spec_volumes_persistentvolumeclaims_info to calculate suspected orphaned storage bytes.

    - [PR #18986][Ronilerr] Changing recording rule expression
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • virt-handler unresponsive socket handling fixed
    Affectsvirt-handler's unresponsive domain socket handling(Inferred)

    Multiple unresponsive sockets can now be cleaned up in one pass, including when sockets switch between responsive and unresponsive states. Untracking one unresponsive socket no longer blocks another's expiration.

    - [PR #18970][xpivarc] Bug fix: unresponsive sockets are not correctly accounted
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Same-name VM and VMI time-series reuse fixed with UID labels
    Affectsinstallations scraping or querying kubevirt_vm_info or kubevirt_vmi_info(Inferred)

    Previously, deleting and recreating an object with the same name and namespace reused its Prometheus time series. The uid label now makes the recreated object a distinct series; VM UIDs stay stable across stop/start, while VMI UIDs change on each start.

    - [PR #18854][sradco] Add uid label (Kubernetes object UID) to kubevirt_vm_info and kubevirt_vmi_info
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Stopped VM status corrected for RunStrategyRerunOnFailure
    AffectsVMs using RunStrategyRerunOnFailure

    When one of these VMs was manually stopped while its PVC was unbound, it could show WaitingForVolumeBinding even though the controller had not created a VMI. It now reports Stopped regardless of PVC state.

    - [PR #18787][davmarro] Fixed a bug where a VM with RunStrategyRerunOnFailure incorrectly showed WaitingForVolumeBinding status after being manually stopped when its PVC was unbound.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Host NUMA distances passed through to guest NUMA cells
    AffectsVMs on multi-NUMA hosts with host distance data available(Inferred)

    For VMs spanning three or more NUMA nodes, remote nodes previously appeared equidistant, limiting scheduling decisions. The guest OS now sees the host NUMA distance matrix, with host node IDs mapped to sequential guest IDs.

    - [PR #18829][omastama-spec] Added NUMA node distance passthrough from host topology to guest VMs, enabling performance-sensitive applications to make optimal scheduling decisions on multi-NUMA systems.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • VM alert evaluation restored to cluster/node scope
    Affectsthe OrphanedVirtualMachineInstances or VirtLauncherPodsStuckFailed alert rules

    Previously, OrphanedVirtualMachineInstances could fire once per VM namespace even when virt-handler was ready, and VirtLauncherPodsStuckFailed applied its 200-launcher threshold within a single namespace. The namespace label now identifies the KubeVirt install namespace instead of coming from virt-launcher series.

    - [PR #18822][sradco] Fix OrphanedVirtualMachineInstances false positives and VirtLauncherPodsStuckFailed per-namespace threshold by restoring cluster-scoped evaluation with a static install-namespace label
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Sidecar hooks preserve QEMU command-line arguments across XML round-tripsSilent failure
    Affectssidecar hooks carrying QEMU qemu:commandline arguments through XML round-trips(Inferred)

    During this round-trip, the arguments could be silently dropped.

    - [PR #18460][dasionov] Fix sidecar hooks silently dropping QEMU command-line arguments (qemu:commandline) during XML round-trip
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Preferred panic device creation fixed
    AffectsVMs using a VirtualMachinePreference with PreferredPanicDeviceModel set

    Previously, the preference was silently ignored when the VMI had no panic device, leaving it without the device it was meant to ensure. KubeVirt now creates a panic device with the preferred model in that situation.

    - [PR #18314][lyarwood] Bug fix: PreferredPanicDeviceModel now creates a panic device when none exist on the VMI, instead of silently ignoring the preference.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • SR-IOV, GPU and PCI host-device VM start failure fixed
    AffectsVMIs using SR-IOV, GPU or PCI host devices in clusters with the Plugins feature gate enabled and at least one Plugin

    Before this fix, those VMIs failed to start in that setup. They can now start, with subsystem mode added to the generated host-device entries.

    - [PR #19771][kubevirt-bot] Fix VMIs with SR-IOV, GPU or PCI host devices failing to start when the Plugins feature gate is enabled and any Plugin exists in the cluster.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Node hooks inherit the Plugin-level failureStrategy
    AffectsPlugins with node hooks that omit their own failureStrategy

    When a Plugin has spec.failureStrategy: Ignore, a failing node hook without its own strategy no longer blocks VM start, stop, or migration. If neither level sets a strategy, the hook defaults to Fail; a hook-level strategy takes precedence.

    - [PR #19863][kubevirt-bot] Node hooks now fall back to the Plugin-level failureStrategy when they do not set their own, like launcher hooks. Plugins with spec.failureStrategy: Ignore no longer block VM start, stop or migration when one of their node hooks without its own failureStrategy fails.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • virt-handler panic on device-plugin restart fixed
    Affectsnodes with host devices

    Restarting a device plugin could panic virt-handler; on nodes with host devices, this happened on every kubelet restart.

    - [PR #19743][kubevirt-bot] Fixed a virt-handler panic when a device plugin is restarted, which on nodes with host devices happened on every kubelet restart.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Live migration targeting fixed for virt-handler upgrades
    Affectslive migrations during rolling upgrades(Inferred)

    A migration from an updated virt-handler node could be scheduled onto a node that had not yet been updated and get stuck. The fix restricts targets to nodes running the desired virt-handler image.

    - [PR #19732][stu-gott] Live migrations are no longer scheduled from a node running an updated virt-handler onto a node that has not yet been updated, preventing migrations from getting stuck during a rolling upgrade.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • virt-handler gRPC connection leak fixed
    Affectsvirt-handler client initialization(Inferred)

    When newClientWithInfoClient failed during NewClient initialization, the gRPC connection could remain open. The connection is now closed on that path, while the error is still returned.

    - [PR #19492][caxu-rh] Fixed a bug that caused a gRPC connection to leak when virt-handler client initialization fails
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • VM startup recovers overlays after External snapshot crashes
    AffectsVMs using External snapshots

    If virt-launcher crashes during an External snapshot and leaves the VM's disks on overlays, startup previously stopped with ManualRecoveryRequired; recovering writes required manual overlay commits or restoring a snapshot. On start, the replacement VMI now boots on the remaining overlays and commits their writes live, clearing the startup block and releasing the scratch volume after the commit is verified; recovery is still refused if the volume or scratch state fails checks.

    - [PR #19574][noamasu] Guest writes are recovered when a VM starts after a virt-launcher crash during an External mode snapshot.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Hotplug mount teardown now preserves PVC files
    AffectsVM workloads using hotplug volumes mounted through the hotplug mount root(Inferred)

    When kubelet cleanup ran before virt-handler unmounted a utility volume, it could delete files on that volume’s PVC. Teardown now unmounts the memory-backed root instead, preserving files on mounted PVCs.

    - [PR #19520][noamasu] Use a memory-backed emptyDir for the hotplug mount root to support mount propagation.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Orphaned CBT overlay cleanup on disable and disk hot-unplug
    Affectssetups using CBT with retained backend PVCs or hot-unplugged disks

    Hot-unplugging a disk in certain circumstances or disabling CBT could leave orphaned overlays. These overlays are now removed; after CBT is re-enabled, the next backup falls back to a full backup instead of failing checkpoint redefinition.

    - [PR #19435][awels] Cleanup CBT overlays when disabling CBT
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • VirtualMachineExport volume-name collisions fixed
    AffectsVirtualMachineExports for VMs with claims whose names differ only by dots or collide with fixed exporter-pod volume names

    Sanitizing claim names made dot-differing names such as my.disk and my-disk produce duplicate volume names, so the API server rejected the exporter pod and the export never completed. The pod now uses unique index-based volume names, allowing the export to complete.

    - [PR #19064][0xFelix] Fixed a bug where a VirtualMachineExport of a VM with two claims whose names differ only in dots would never complete
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • InjectNotify closes the listener before returning errors
    Affectsuse of InjectNotify with a Unix socket

    When the socket path was invalid or setting its file ownership failed, InjectNotify returned an error but could leave the listener open.

    - [PR #19534][caxu-rh] Fixed a bug where a Unix socket listener may be left open if an error occurs while setting file ownership on the socket
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Backups now fail promptly when their VMI is deleted
    Affectsbackups of VMIs

    When a VMI was deleted during a backup without a status change, the backup previously remained pending until its TTL. It now fails with SourceLost, and pull-mode exports are removed.

    - [PR #19484][Acedus] Backups whose VMI is deleted mid-backup now fail immediately, and pull-mode backups remove their export.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • GetVMStats preserves successful statistics when a sub-command fails
    Affectssetups that collect VMStats through GetVMStats(Inferred)

    Previously, one failed sub-command caused virt-handler to discard data returned by the others; failures are now recorded in the VMStats.Errors map.

    - [PR #19192][machadovilaca] Keep partial VMStats when a sub-command fails
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Duplicate-PVC export failures now report status
    AffectsVirtualMachineExports from VM, VMSnapshot, or VMTemplate sources that reference the same PVC in multiple volumes

    Previously, the exporter pod was rejected for duplicate volume names before status was written, leaving the export with an empty phase, no conditions, and endless backoff. Now it reports Pending with a DuplicatePVC ready condition naming the claims, and creates no exporter pod until the duplicate references are fixed.

    - [PR #19057][0xFelix] Fixed a bug where a VirtualMachineExport of a source referencing the same PVC from more than one volume would never complete
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • SeaBIOS now honors the PCI-hole setting
    AffectsVMs using SeaBIOS with the kubevirt.io/disablePCIHole64 annotation

    Previously, SeaBIOS ignored QEMU’s setting and programmed its own 64-bit PCI hole, so guests with more than 4Gi of memory could still have the hole. It now leaves that hole alone, allowing legacy guests such as Windows Server 2003 to run with 4Gi of memory or more.

    - [PR #18941][0xFelix] The kubevirt.io/disablePCIHole64 annotation now also stops SeaBIOS from programming a 64-bit PCI hole, allowing legacy guests like Windows Server 2003 to run with 4Gi of memory or more.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Velero post-backup unfreeze timeout extended to 60 seconds
    AffectsVelero backups with post-backup unfreeze hooks

    Previously, the internal gRPC timeout could fail unfreeze when Windows guest thaw took longer than 20 seconds, regardless of the post-hook timeout annotation. Unfreeze can now run for up to 60 seconds, and generated post-backup hooks set post.hook.backup.velero.io/timeout to 60s.

    - [PR #19166][alromeros] Bugfix: Increase timeout for velero post-backup hook
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Online file-backed disk expansion now uses PVC capacity
    AffectsVMs with PVC-backed file disks undergoing online expansion(Inferred)

    During I/O on filesystem volumes, changing free space could repeatedly trigger BlockResize attempts.

    - [PR #19120][akalenyu] BugFix: blockresize spam when doing I/O for filesystem volumes
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Online BlockResize now prevents guest disk shrinking
    AffectsVMs using online disk resizing(Inferred)

    When the newly observed capacity is less than or equal to the tracked size, KubeVirt skips the resize rather than shrinking the guest disk.

    - [PR #19120][akalenyu] BugFix: blockresize spam when doing I/O for filesystem volumes
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Restored /dev/urandom access across cgroup rebuilds
    AffectsVMIs without a virtio-rng device

    During block-volume hotplug or live migration, rebuilding the cgroup allow list could remove /dev/urandom access; on s390x, this crashed virtqemud and could cause sync or migration failures. The default device rules now always allow /dev/urandom across cgroup rebuilds on cgroups v1 and v2, regardless of VMI configuration or architecture.

    - [PR #19131][vishnubijukumar] Fixed a bug where hotplugging a block volume or triggering a live migration on s390x crashed virtqemud due to /dev/urandom being removed from the cgroup device allow list. /dev/urandom (char 1:9) is now unconditionally included in the default cgroup device rules, consistent with the OCI runtime specification. This also fixes a latent bug on x86_64 where /dev/urandom was incorrectly revoked but masked by the RDRAND hardware entropy fallback.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • OCI exports skip non-disk backend directories
    AffectsOCI VirtualMachineExports of VMs with persistent TPM or EFI backend storage

    The digest pass tried to open disk.img in backend state directories, leaving exports Pending and serving no disks or manifests. It now skips those directories and serves the export contents.

    - [PR #19085][0xFelix] Fixed a bug where an OCI VirtualMachineExport of a VM with a persistent TPM or EFI never became ready
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Centos Stream 10 socket-path compatibility fixed for KubeVirt images
    AffectsCentos Stream 10-based deployments using the virt-handler or vm-killer images(Inferred)

    Centos Stream 10 creates sockets in /run/, while KubeVirt expects them in /var/run/; this prevented vm-killer from resolving the dbus socket and virt-handler from mounting the multipathd socket. The images now include a /var/run -> ../run symlink, so /var/run/ resolves to /run/.

    - [PR #18951][dsanatar] image changes for Centos Stream 10 compatibility, notably adds /var/run -> ../run symlink to virt-handler image layer due to how CS10 creates sockets in /run/ but kubevirt expects them to exist in /var/run/
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Vera Rubin GPU passthrough configuration fixed
    AffectsVMs passing through NVIDIA Vera Rubin GPUs (10de:3041) with GraceIOVirtualization

    Previously, virt-handler did not recognize the GPU as a Grace GPU, so virt-launcher skipped the required domain configuration. The launcher now configures a 2 TiB pcihole64 aperture and the arm-smmuv3 IOMMU model for it.

    - [PR #19070][lyarwood] Vera Rubin GPU (10de:3041) is now recognised as a Grace GPU, enabling GraceIOVirtualization for VMs with a passthrough Vera Rubin GPU.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Terminated launcher pod UIDs pruned from VMI active-pod status
    AffectsVMIs with hotplug volume reconciliation

    After successful live migration, terminated source launcher pods in Succeeded or Failed phase could remain alongside the target UID in VMI.status.activePods, causing findVirtlauncherUID() to return an empty UID and hotplug reconciliation to loop with SyncFailed. Those terminated pods are now excluded, leaving the running target UID so hotplug reconciliation can proceed.

    - [PR #18287][dasionov] Ensure terminated launcher pods are pruned from VMI status.activePods after live migration
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Prometheus EndpointSlice discovery permission fixed
    AffectsPrometheus target discovery through EndpointSlices in the KubeVirt namespace

    When the Prometheus CR sets serviceDiscoveryRole to EndpointSlice, Prometheus can list those EndpointSlices for target discovery.

    - [PR #19041][machadovilaca] Allow Prometheus to list EndpointSlices in the KubeVirt namespace
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Offline PVC expansion now checks actual preallocation status
    Affectsthin-provisioned PVC/DataVolume-backed disks(Inferred)

    During offline PVC expansion, a full thin-provisioned disk could be mistaken for preallocated based on its virtual and allocated sizes, causing the expanded space to be unnecessarily preallocated.

    - [PR #18827][germanovm] Fix PVC expansion preallocating new space on full thin provisioned disks
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Stale CA fixed in export manifest ConfigMaps
    AffectsVirtualMachineExport manifests used for CDI disk imports

    After export CA rotation and exporter Pod recreation, an existing manifest ConfigMap could retain the old CA, causing CDI imports using it to fail TLS verification. The controller now updates the existing ConfigMap with the new CA.

    - [PR #18965][lukashes] Fixed VirtualMachineExport manifests retaining stale CA certificates when exporter Pods are recreated after CA rotation, which could cause CDI disk imports to fail TLS verification
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Source ghost record leak during decentralized live migration fixed
    Affectsdecentralized live migration where a later same-name VMI may be scheduled on the same node

    On a busy source node, cleanup could miss the brief Shutoff+Migrated state, leaving a ghost record that blocked a later same-name VMI from registering and starting and could cause the migration to time out. Once the source is terminal, virt-handler now continues through sync() to delete the source ghost record, allowing a same-name, new-UID receiver on that node to register and start.

    - [PR #18988][davmarro] Fixed a source-side ghost record leak on decentralized live migration that could prevent a subsequent same-name VirtualMachineInstance from starting on the same node.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • False GuestFilesystemAlmostOutOfSpace alerts for Windows UDF media fixed
    AffectsWindows VMs with a UDF CDROM/ISO attached and monitored by GuestFilesystemAlmostOutOfSpace

    The QEMU Guest Agent reports attached optical media with 0 bytes free, and the case-sensitive filesystem-type exclusion missed uppercase UDF, causing the alert to fire. The exclusion is now case-insensitive, so the alert no longer fires for UDF CDROM/ISO media.

    - [PR #18994][avlitman] Fix GuestFilesystemAlmostOutOfSpace firing on Windows VMs when a UDF CDROM/ISO is attached.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • NoReady alerts corrected to avoid firing with Down alerts
    AffectsKubeVirt VirtController, VirtHandler, or API NoReady and Down monitoring alerts(Inferred)

    Previously, the Down and NoReady alerts could fire simultaneously. Now, NoReady alerts fire only for pods that are running but not ready.

    - [PR #18942][Ronilerr] Fix no ready alerts
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • PCI passthrough startup failure fixed
    AffectsVMs using PCI host-device passthrough on hosts without CONFIG_VFIO_DEVICE_CDEV support

    These VMs failed to start even when the IOMMUFD feature gate was disabled. On kernels without IOMMUFD support, nonexistent cdev devices are skipped and passthrough uses /dev/vfio/<group>; kernels with IOMMUFD support retain cdev behavior.

    - [PR #18905][fossedihelm] Fix PCI passthrough regression on kernels without CONFIG_VFIO_DEVICE_CDEV support. VMs with GPU/PCI host devices now correctly fall back to legacy VFIO group interface when IOMMUFD cdev is unavailable.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Memory overcommit bypassed for hugepages-enabled VMIs
    AffectsVMIs configured to use hugepages

    Previously, applying memory overcommit to these VMIs produced an unaligned memory value. They now use their memory value without overcommit.

    - [PR #18880][jean-edouard] Memory overcommit is now ignored for VMIs with hugepages
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • VFIO device ownership error handling fixed
    Affectssetups that use VFIO device ownership preparation

    When resolving the launcher mount root failed during VFIO device ownership preparation, a nil pointer dereference could terminate virt-handler and stop VM reconciliation on that node. It now returns errors other than os.ErrNotExist to its caller, which propagates them into a SyncFailed event instead of terminating virt-handler.

    - [PR #18867][cwedgwood] Fix a virt-handler crash that could occur when preparing VFIO device ownership fails.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Atomic disk writes for virt-handler ghost and mount records
    Affectssetups where virt-handler writes ghost or mount records to disk

    If virt-handler restarted while writing records, the implementation could lose data or produce corrupt records.

    - [PR #18716][xpivarc] Bug fix: Ensuring that records (ghost records, mount records) are written atomically to disk
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Premature domain undefine during slow QEMU startup fixed
    AffectsVMs using hotplug(Inferred)

    During slow QEMU startup, premature domain undefine left VMs transient and broke hotplug. After the upgrade, this premature undefine is fixed.

    - [PR #18545][amasolov] Fix premature domain undefine during slow QEMU startup that left VMs transient and broke hotplug
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • CBT backend PVC request increased by 1Gi
    AffectsVMs with CBT enabled that require a backend persistent-state PVC

    Previously, these PVCs requested only 10Mi, which was insufficient for most CBT use cases.

    - [PR #18470][Acedus] Backend storage PVC size is increased by 1Gi for VMs with CBT enabled.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Domain stats collection no longer blocks on locked domains
    Affectslive migration with domain stats collection

    During live migration, GetDomainStats() could wait up to 30 seconds on the migration-held libvirt job lock, time out, log errors, and disrupt upgrade flows monitoring virt-launcher health. It now skips locked domains and serves cached values; stats collection continues for other cases, though skipped domains can still produce an empty DomainStats error log about every 3.25 seconds during migration.

    - [PR #18362][iholder101] Bug fix: During live migration, domain stats collection no longer blocks on the libvirt job lock for up to 30 seconds. The NOWAIT flag is used to skip locked domains instead of waiting, avoiding lock contention and disruptive error logs.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • vmexport proxy file descriptor leak fixed
    Affectssetups using the vmexport proxy(Inferred)

    Before this fix, the vmexport proxy leaked file descriptors.

    - [PR #18400][awels] BugFix: file descriptor leak in vmexport proxy
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • client-go AsyncSubresourceHelper leak fixed
    AffectsAsyncSubresourceHelper StreamInterface consumers using AsConn()

    Using AsConn() instead of Stream() leaked a goroutine and connection resource. The AsConn() path no longer has this leak.

    - [PR #18410][vikin91] Fix a goroutine (and connection resource) leak in client-go's AsyncSubresourceHelper when its StreamInterface is consumed via AsConn() instead of Stream() (affects VSOCK, PortForward TCP/UDP, and similar consumers).
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Running VMIs get a 3-minute launcher reconnection grace period
    Affectsrunning VMIs

    When virt-handler restarted and temporarily lost the launcher socket connection, a running VMI was immediately marked Failed. It now remains within the 3-minute reconnection grace period before it can transition to Failed.

    - [PR #18453][iholder101] Bug fix: Running VMIs are no longer immediately marked as Failed when virt-handler restarts and temporarily loses the launcher socket connection. A 3-minute grace period (matching the existing Scheduled VMI behavior) now allows the launcher client to reconnect before transitioning the VMI to Failed.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Invalid network interface bindings rejected at admission
    AffectsVMs or VMIs with a network interface configured with no binding or more than one binding

    Previously, these interfaces were not rejected at admission and failed silently at runtime.

    - [PR #18374][orelmisan] Fixed missing validation for network interface bindings: interfaces with no binding or multiple bindings are now rejected at admission instead of failing silently at runtime.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • VFIO cdev devices exposed to virt-launcher containers
    AffectsARM64 systems with SMMUv3 using IOMMUFD-based GPU passthrough

    This fixes IOMMUFD-based GPU passthrough on ARM64 systems with SMMUv3.

    - [PR #18300][lyarwood] Bug fix: Expose VFIO cdev devices (/dev/vfio/devices/vfioN) to virt-launcher containers, fixing IOMMUFD-based GPU passthrough on ARM64 systems with SMMUv3.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • VMI owner resolution fallback for hotplug attachment pods
    Affectshotplug attachment pods

    If an attachment-pod event was processed after the virt-launcher pod had been deleted, owner resolution could fail and the VMI was not notified. The attachment pod's owner name and UID annotations now provide a fallback when the owner-reference chain cannot resolve the VMI.

    - [PR #18222][lukashes] Fixed VMI owner resolution when an attachment pod is deleted while the virt-launcher pod is gone
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Hotplug volume detach deadlock fixed
    Affectshotplug volume detachment

    Detaching a hotplug volume that had already been removed could deadlock.

    - [PR #18044][maxwmsft] BugFix: hotplug volume detach deadlock for already removed volumes.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Hotplug volume detach deadlock fixed
    AffectsVMIs exchanging RWO PVCs between attachment pods

    Hotplug volume detachment could deadlock during these exchanges.

    - [PR #18045][maxwmsft] BugFix: hotplug volume detach deadlock when VMIs exchange RWO PVCs between attachment pods.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Session-mode memlock calculation fixed for memory-locked VMs
    AffectsVMs requiring memory locking for VFIO, realtime, SEV, or explicit memlock, running in session mode

    Libvirt's memlock calculation could fail for these VMs. The memlock prlimit is now unlimited, so the calculation succeeds.

    - [PR #17857][lyarwood] Set unlimited memlock prlimit for VMs requiring memory locking (VFIO, realtime, SEV, explicit memlock), ensuring libvirt's memlock calculation always succeeds in session mode.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • NAD changes on non-migratable VMs now require restart
    AffectsNAD references on non-migratable VMs

    When a NAD reference changed, it was synced to the VMI spec and triggered a MigrationRequired condition; because the VM could not migrate, the condition persisted and the change never applied. The changed reference is now withheld from the VMI spec.

    - [PR #18194][frenzyfriday] Require restart for NAD swap for non-migratable VMs
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Low virt count alerts now use the running rule
    Affectssetups that consume low virt count alerts(Inferred)

    Previously, these alerts used the up rule instead of the running rule.

    - [PR #18380][Ronilerr] Low virt count alerts are using running rule intead of up rule
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Incorrect restarts of NFS-backed VMs fixed
    AffectsVMs with NFS-backed storage

    During temporary NFS unavailability, such as an NFS server failover, these VMs could be restarted incorrectly. That unavailability no longer causes the incorrect restart.

    - [PR #17752][iholder101] Bug fix: VMs with NFS-backed storage are no longer incorrectly restarted during temporary NFS unavailability (e.g., NFS server failover).
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • VM restore handling for backend storage fixed
    AffectsVMs using a VMStateStorageClass without snapshot support

    When VMStateStorageClass lacked snapshot support, the backend PVC could not be included in the snapshot, causing restore issues. Restore now skips reconciliation for a backend volume absent from snapshot contents and reuses the existing backend PVC.

    - [PR #17286][alromeros] Bugfix: Fix VM restore when backend storage is not snapshottable
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • kubevirt-plugin-sidecar-subpath-policy importer-pod rejection fixed
    Affectsinstallations using the kubevirt-plugin-sidecar-subpath-policy(Inferred)

    Importer pods could be rejected when the policy’s matchConditions evaluated them. The policy now selects virt-launcher pods with an objectSelector before CEL evaluation.

    - [PR #18392][akalenyu] BugFix: Importer pod rejected by ValidatingAdmissionPolicy 'kubevirt-plugin-sidecar-subpath-policy'
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • hugetblfs-dir EmptyDir hugepage backing fixed
    AffectsVMs using the hugetblfs-dir EmptyDir(Inferred)

    When QEMU needed hugepages via -mem-path, this volume masked the parent hugetlbfs mount at /dev/hugepages, preventing allocation. The EmptyDir is now explicitly hugepage-backed, fixing that problem.

    - [PR #18272][laxmi-333] Bug fix: Fixed hugetblfs-dir EmptyDir volume masking the parent hugetlbfs mount at /dev/hugepages, which prevented QEMU from allocating hugepages via -mem-path. The EmptyDir is now explicitly hugepage-backed.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • VMI controller retries sync after expectations timeout
    AffectsVM/VMI deletion involving pod, VMI, or PVC expectations

    When no pod event woke the controller while expectations were unmet, deletion could wait for the next informer resync, which was hours away by default. The retry now occurs after the expectations timeout, five minutes by default.

    - [PR #18206][lukashes] Fixed a delay in VM/VMI deletion that could happen when the VMI controller missed a pod event.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • ClusterConfig CRD delete-handler tombstone panic fixed
    Affectsinstallations using the ClusterConfig CRD

    After a missed CRD delete event, the informer could deliver a cache.DeletedFinalStateUnknown tombstone instead of the CRD, causing the handler to panic. The handler now extracts the CRD from the tombstone, and logs an error and returns if it cannot unwrap the tombstone or it does not contain a CRD.

    - [PR #17880][Shreesha001] Fix panic in ClusterConfig CRD delete handler when the informer delivers a tombstone object instead of the deleted CRD.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Enhancements39

  • IncrementalBackup feature gate promoted to Beta
    - [PR #19690][kubevirt-bot] Beta: IncrementalBackup, and introduce backup.kubevirt.io/v1beta1
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Backup API backup.kubevirt.io/v1beta1 introduced
    - [PR #19690][kubevirt-bot] Beta: IncrementalBackup, and introduce backup.kubevirt.io/v1beta1
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Incremental backups for stopped VMs

    To use OfflineIncrementalBackup feature gate, disabled by default and requiring IncrementalBackup

    - [PR #19294][alromeros] Offline incremental backup
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • External-mode VirtualMachineSnapshot snapshots use QCOW2 overlays

    To use The ExternalVMSnapshot feature gate (Alpha) must be enabled to use External mode.

    - [PR #19360][noamasu] VEP 321: add External mode VirtualMachineSnapshot
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Alpha UEFI Secure Boot for ARM64 guests

    To use Both ARM64SecureBoot and FirmwareAutoSelection feature gates, plus CentOS Stream 10 virt-launcher images with suitable QEMU, libvirt, and edk2 firmware.

    - [PR #17135][lyarwood] Add Alpha UEFI Secure Boot support for ARM64 guests through the ARM64SecureBoot and FirmwareAutoSelection feature gates. Requires CentOS Stream 10 virt-launcher images with suitable QEMU, libvirt, and edk2 firmware. Supports persistent EFI state through existing backend storage.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Alpha DRA allocation for dedicated VMI CPUs

    To use Enable the CPUsWithDRA feature gate

    - [PR #19228][Sreeja1725] Alpha: Add CPUsWithDRA to provision dedicated VMI CPUs via a DRA CPU driver instead of kubelet's CPU manager.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • VMI pod-status reporting for ready network interfaces

    To use NetworkDevicesWithDRA feature gate must be enabled

    - [PR #19572][orelmisan] The pod-status VMI network interface info source is now reported for interfaces whose device is ready in the pod (DRA-backed, and Multus-backed secondary interfaces), when the NetworkDevicesWithDRA feature gate is enabled.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Declarative VM-state PVC selection and creation

    To use DeclarativeVMState feature gate

    - [PR #19173][alromeros] Declarative VirtualMachineState
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Multiple I/O threads for virtio-scsi controllers

    To use The SCSIMultiIOThread feature gate enabled and an IOThreadsPolicy assigned to the VMI

    - [PR #18249][dsanatar] IOThread Virtqueue Mapping for virtio-scsi
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • virtio-blk auto IOThread policy gains pool allocation

    To use Enable the MultiIOThreadAutoPolicy configuration toggle together with the SCSIMultiIOThread feature gate.

    - [PR #18249][dsanatar] IOThread Virtqueue Mapping for virtio-scsi
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Panic-device label added to kubevirt_vmi_info metric
    - [PR #19470][avlitman] Added a has_panic_device label (true/false) to the kubevirt_vmi_info metric
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Sidecar plugin PreBoot launcher hook
    - [PR #19403][iholder101] Add PreBoot and PreMigrationSource sidecar launcher hook points for plugins.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Sidecar PreMigrationSource hook for libvirt migration parameters
    - [PR #19403][iholder101] Add PreBoot and PreMigrationSource sidecar launcher hook points for plugins.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • pkg/render adds cluster-free VM-to-Pod rendering
    - [PR #19234][vladikr] Add pkg/render for rendering Pod specs from VM/VMI definitions without a running cluster
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Configurable TLS key exchange groups for virt pod endpoints

    To use Enable the TLSGroupPreferences feature gate and configure TLSConfiguration.Groups with the desired groups. The gate is Alpha and disabled by default.

    - [PR #19215][Barakmor1] Add TLSGroupPreferences feature gate and Groups field to TLSConfiguration, enabling cluster administrators to configure TLS supported groups (elliptic curves) across all virt pod endpoints for Post-Quantum Cryptography readiness
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Proxy-mode migration endpoint discovery from labeled Routes, Ingresses, and Services

    To use Proxy mode enabled, no cross-cluster network configured, and a Route, Ingress, or Service with the appropriate endpoint-discovery label

    - [PR #19351][awels] Decentralized live migration using the proxy dataPath supports Route/Ingress/Service endpoints
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • virt-handler downtime gauge for latest successful VMI migrations
    - [PR #17974][bxuan1999] virt-handler now exposes a per-VMI gauge containing the downtime reported for the latest successful live migration.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Container waiting reasons added to Virt*Down alerts
    - [PR #17985][sradco] Virt*Down alerts include container waiting reason when the component is fully unavailable
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • VM guest memory opt-out from kernel merging

    To use Set the kubevirt.io/mergeable-memory annotation to false on the VMI to opt out of kernel memory merging.

    - [PR #19033][michalskrivanek] adds kubevirt.io/mergeable-memory annotation to opt out the guest memory from kernel memory merging
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • GPU utilization and graphics-engine activity recording rules added
    - [PR #19144][machadovilaca] Add GPU utilization time and active engine time recording rules
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • TCP proxy support for decentralized live migration

    To use DecentralizedLiveMigration feature gate

    - [PR #17922][awels] Decentralized live migration can now use a proxy to reduce the number of ip addresses required
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • VMI GPU recording rules for DCGM metrics
    - [PR #18962][machadovilaca] Add VMI GPU usage recording rules correlating DCGM metrics
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • VM disks gain the directsync cache mode

    To use Configure cache=directsync for the VM disk.

    - [PR #17718][michalskrivanek] Added support for "directsync" disk cache modes Directsync is similar to "none" + "writethrough" combined, the host page cache is bypassed and there is also no caching on the guest side, all writes go directly to storage. This offers better performance than "writethrough" with lower host memory overhead since the host page cache is bypassed.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • VSOCK transport for virtctl port-forward, virtctl ssh, and virtctl scp

    To use Set --vsock to use VSOCK transport. For virtctl port-forward, --vsock-tls controls the TLS handshake and defaults to true.

    - [PR #18274][ksimon1] virtctl: add vsock ssh proxy command
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Guest device payload forwarding through VMStatsCollector
    - [PR #19007][codingben] Expose guest device info via VMStatsCollector
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • GetVMStats adds guest filesystem information

    To use GuestGetFsInfo in the GetVMStats request

    - [PR #19002][machadovilaca] Add guest-get-fsinfo to GetVMStats
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • DRA network claims reach binding sidecars and migration targets
    - [PR #18741][frenzyfriday] Network Binding Plugins sidecars receive DRA resource claims for device metadata access
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • KubeVirt recording rule for suspected orphaned PVC storage
    - [PR #18521][Ronilerr] Add recording rule for report suspected orphaned PVCs
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Dynamic live-migration downtime tuning

    To use Alpha MigrationDowntimeTuning feature gate and opt-in through .spec.experimental.downtimeTuning in MigrationPolicy

    - [PR #17480][michalskrivanek] Live migration downtime can now be dynamically tuned by using .spec.experimental.downtimeTuning field in MigrationPolicy. When enabled, QEMU's max_downtime is gradually increased from an initial value (default 150ms) to a configurable ceiling (default 1050ms), helping migrations converge with bounded sub-second switchover downtime.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • ImageVolume containerDisk support for OCI artifacts and root-level disks

    To use For non-container OCI artifacts, set the VMI annotation kubevirt.io/image-volume-skip-digest-resolution: "true" to skip incompatible digest-resolving init containers.

    - [PR #18491][vladikr] Add support for OCI artifacts (e.g. raw disk images pushed with ORAS) as containerDisk sources via the ImageVolume path. Set the annotation `kubevirt.io/image-volume-skip-digest-resolution: "true"` on the VMI to skip the digest-resolving init containers that are incompatible with non-container OCI artifacts. The disk file discovery now also supports images with the disk at the root directory, not just under /disk.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Namespace labels added to KubeVirt alerts
    - [PR #17995][sradco] Add namespace label to all KubeVirt alerts for proper OpenShift
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Network binding plugin sidecar registration-name inference

    To use NETWORK_BINDING_PLUGIN_NAME environment variable

    - [PR #18435][orelmisan] Network binding plugin sidecars can now infer their registration name using the `NETWORK_BINDING_PLUGIN_NAME` environment variable.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • KubeVirt emits the kubevirt_vmi_guest_os_panic_total metric
    - [PR #18370][michalskrivanek] The `kubevirt_vmi_guest_os_panic_total` metric is now emitted
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Separate disk and source volume names in virtctl addvolume

    To use --disk-name on virtctl addvolume

    - [PR #17936][dsanatar] virtctl: addvolume optional --disk-name flag
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Snapshot-backed inferFromVolume support

    To use inferFromVolume configured for a snapshot-backed DataVolume, DataVolumeTemplate, or DataSource

    - [PR #18337][0xFelix] Support inferFromVolume for VolumeSnapshot-backed DataVolumes, DataVolumeTemplates, and DataSources
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • KubeVirt adds a leading virt-controller recording rule and alert
    - [PR #18154][Ronilerr] Adding NoLeadingVirtController alert
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Built-in KubeVirt roles gain VM memory-dump removal permission
    - [PR #17775][akalenyu] BugFix: admin can remove memory dump from their VM
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Optional zstd compression for live migration streams

    To use AdvancedLiveMigration feature gate

    - [PR #17509][michalskrivanek] Live migration data stream can be compressed now by using .spec.experimental.compression field in MigrationPolicy applied to a set of VMs. Currently only "zstd" algorithm is supported.
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0
  • Local-namespace VSOCK dialing in virt-handler

    To use ns_mode set to local

    - [PR #17955][akrejcir] Add namespace-aware VSOCK dialing support in virt-handler (VEP 222)
    github.com/kubevirt/kubevirt/releases/tag/v1.10.0

Dependency updates7

6 more, none mentioning security
  • - [PR #19521][kubevirt-bot] Updated common-instancetypes bundles to v1.8.0
  • - [PR #19388][0xFelix] Updated virt-template to v0.3.0
  • - [PR #19048][michalskrivanek] Libvirt updated to 12.5.0-4.el10
  • - [PR #18908][kubevirt-bot] Updated virt-template to v0.2.3
  • - [PR #18315][alancaldelas] Kubernetes dependencies have been updated to v0.36.4 (Kubernetes 1.36)
  • - [PR #18761][lentzi90] Build KubeVirt with go 1.26.6
Other changes31

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.