v1.8.1

Changelog v1.8.1

Fixes

• [module] Added missing RBAC permissions for virtualization resources, including virtual machine MAC addresses, snapshot operations, and node USB devices. #2276
• [vd] Fixed a potential issue where a virtual disk could get stuck in the Provisioning state when using a storage class with the WaitForFirstConsumer mode. #2292

For more information, see the changelog and minor version release changes.

v1.8.0

Changelog v1.8.0

Features

• [vm] Added the progress field to the status of VirtualMachineOperation resources with the Evict and Migrate types to show operation progress. The corresponding PROGRESS column is displayed when running d8 k get vmop #2182
• [vm] Added the ability to change the number of CPUs in a virtual machine without manually stopping it. The new value is applied via live migration. To enable this functionality, add HotplugCPUWithLiveMigration to .spec.settings.featureGates in the ModuleConfig of the virtualization module. #2147
• [vm] Added initial support for changing virtual machine memory without manually stopping the virtual machine. The new .spec.memory value is applied via live migration. To enable this functionality, add HotplugMemoryWithLiveMigration to .spec.settings.featureGates in the ModuleConfig of the virtualization module. #2110

Fixes

• [api] When uploading disks and images with the Upload type, the WaitForUserUpload phase no longer occurs prematurely while the resource is not yet ready for upload. #2178
• [core] Added automatic cleanup of NodeUSBDevice resources that are absent on the node and are not assigned to a namespace or project. #2220
• [vm] Fixed an issue with an unfrozen filesystem during virtual machine snapshot creation if the freeze occurred during migration. #2225
• [vm] Fixed removal of the Main network from a virtual machine: the virtual machine no longer uses an IP address from the virtualization CIDR after the network is removed. #2185
• [vm] Optimized virtual machine migration: it now uses hostNetwork, allowing the host MTU to be used instead of the pod MTU. #2174
• [vmsnapshot] Fixed snapshot creation for a virtual machine without the Main network. #2176

Chore

• [core] Fix vulnerability CVE-2026-39883. #2200
• [core] Fixed vulnerabilities CVE-2026-32280, CVE-2026-32281, CVE-2026-32282, CVE-2026-32283, CVE-2026-32288, CVE-2026-32289 #2196
• [core] Fixed vulnerabilities CVE-2026-34986. #2188
• [core] Fixed vulnerabilities CVE-2026-25679, CVE-2026-27142, CVE-2026-27139, CVE-2026-33186, CVE-2026-34040, CVE-2026-33997. #2175

For more information, see the changelog and minor version release changes.

v1.7.1

Changelog v1.7.1

Know before update

• Action is required to update the firmware on virtual machines with a connected USB device (a corresponding migration prompt will appear in the VM status):

  • either disconnect the USB device and migrate the virtual machine;
  • or restart the virtual machine.

  Until the action is taken, the virtual machine will continue running, but it cannot be migrated.
  After completing the action, the virtual machine will be updated to the current firmware version and will be ready for migration again.

Fixes

• [vm] Action is required to update the firmware on virtual machines with a connected USB device. #2166

Chore

• [core] Fixed vulnerability:
  • CVE-2026-32283
  • CVE-2026-27139
  • CVE-2026-32289
  • CVE-2026-32288
  • CVE-2026-32281
  • CVE-2026-27142
  • CVE-2026-33997
  • CVE-2026-33726
  • CVE-2026-32282
  • CVE-2026-32280
  • CVE-2026-25679
  • CVE-2026-34040
  • CVE-2026-34986
  • CVE-2026-39883
  • CVE-2026-33186 #2219

For more information, see the changelog and minor version release changes.

v1.6.3

Changelog v1.6.3

Chore

• [core] Fixed vulnerabilities:
  • CVE-2026-32283
  • CVE-2026-27139
  • CVE-2026-32289
  • CVE-2026-32288
  • CVE-2026-32281
  • CVE-2026-27142
  • CVE-2026-33997
  • CVE-2026-33726
  • CVE-2026-32282
  • CVE-2026-32280
  • CVE-2026-25679
  • CVE-2026-34040
  • CVE-2026-34986
  • CVE-2026-39883
  • CVE-2026-33186 #2218

For more information, see the changelog and minor version release changes.

v1.7.0

Changelog v1.7.0

Features

• [vm] Reduced USB device downtime during virtual machine migration. #2098
• [vm] Added a garbage collector for completed and failed virtual machine pods:
  • Pods older than 24 hours are deleted.
  • No more than 2 completed pods are retained. #2091

Fixes

• [core] Fixed validation for the AlwaysForced virtual machine migration policy: VirtualMachineOperation resources with the Evict or Migrate type without explicit force=true are now rejected for this policy. #2120
• [core] Fixed the creation of block devices from VMDK files (especially for VMDKs in the streamOptimized format used in exports from VMware). #2065
• [vm] Block devices can now be attached and detached even if the virtual machine is running on a cordoned node. #2163
• [vm] Fixed virtual machine eviction during node drain: pods responsible for block device attachments are no longer removed from a cordoned node before virtual machine migration is complete. #2153
• [vm] Fixed double storage quota consumption during migration of a virtual machine with local storage. #2148
• [vm] Fixed an issue where a virtual machine could get stuck in the Maintenance state during restore from a snapshot. #2144
• [vm] Stabilized the operation of USB devices for virtualization on Deckhouse version ≥1.76 and Kubernetes version ≥1.33. #2137
• [vm] Fixed the detection of USB devices on the host: previously, there was a possibility of duplicate USB devices appearing. #2122

For more information, see the changelog and minor version release changes.

v1.6.2

Changelog v1.6.2

Fixes

• [module] The virtualization module requires Deckhouse Kubernetes Platform version 1.74.2 or later. This version includes a fix for quota validation when creating disks. #2133

For more information, see the changelog and minor version release changes.

v1.6.1

Changelog v1.6.1

Fixes

• [module] Fixed vulnerabilities CVE-2026-24051 and CVE-2025-15558. #2057
• [observability] Restored the previous placement of virtual machine dashboards due to a validation issue that could block the Deckhouse queue. #2063
• [vm] Fixed USB device discovery on nodes: corresponding NodeUSBDevice resources might not have been created. #2085
• [vm] Fixed cloning of a virtual machine with connected USB devices when using VirtualMachineOperation with the Clone type in BestEffort mode. #2076

For more information, see the changelog and minor version release changes.

v1.5.2

Changelog v1.5.2

Fixes

• [core] Fixed a potential OOMKill during virtual disk creation on NFS. #2029

For more information, see the changelog and minor version release changes.

v1.6.0

Changelog v1.6.0

New features

• [vm] Added support for attaching USB devices to virtual machines via .spec.usbDevices.
• [usb] Added NodeUSBDevice and USBDevice resources to manage USB devices in the cluster:
  • NodeUSBDevice (cluster-scoped): Represents a USB device discovered on a specific node. Allows assigning a USB device for use in a specific namespace.
  • USBDevice (namespace-scoped): Represents a USB device available for attachment to virtual machines in a given namespace.
• [observability] Added the Virtualization / Overview dashboard with an overview of the virtualization platform status.
• [observability] Added information about virtual machine pods to the virtual machine dashboard.
• [dvcr] Enabled DVCR cleanup in clusters by default: daily at 02:00. You can override the schedule via dvcr.gc.schedule in the virtualization module ModuleConfig.

Fixes

• [vd] Fixed virtual disks hanging during creation in WaitForFirstConsumer mode on nodes with taints.
• [vm] If only the Main network is specified in .spec.networks, the sdn module is no longer required.
• [vm] Fixed virtual machine migration with disks attached via VirtualMachineBlockDeviceAttachment (hotplug): the target pod could exceed memory limits (OOMKilled).
• [vmbda] Fixed an incorrect Pending phase for the VirtualMachineBlockDeviceAttachment resource during virtual machine migration.
• [vmbda] To remove disks and images attached to a virtual machine via VirtualMachineBlockDeviceAttachment (hotplug), you must first detach them from the virtual machine by deleting the corresponding vmbda. This information has been added to the vmbda status.

Other

• [vm] Added the --from-file flag to the vlctl utility for viewing domain information from a local libvirt XML file.

v1.5.1

Changelog v1.5.0

Fixes

[vd] Fixed an issue with creating a virtual disk from a virtual image stored on a PersistentVolumeClaim (with .spec.storage set to PersistentVolumeClaim). #1983