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.0VirtualMachineBackup 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.0VirtualMachineBackup 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.0io.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.0User-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.0virt-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.0Persistent-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.0Software 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.0Istio 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.0Separate 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.0VSOCK 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.0KubeVirt 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.0CBT 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.0Custom 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.0Network 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.0VM 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.0QEMU 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.0Node 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.0Global -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.0Memory 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.0VGPULiveMigration 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.0Removal 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.0Preparation-time live migration aborts now cancel the migration
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.0VM/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.0DRA 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.0KubeVirt 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.0Deprecated 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.0New 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.0Plugin 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.0virt-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.0GPU 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.0client-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.0DRA 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.0LibvirtHooksServerAndClient 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.0Stall 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.0PCI 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.0Slirp 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.0RamFB 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