SUSE Ships Harvester v1.9.1: Bare-Metal Workloads Go GA

SUSE’s Harvester project has shipped Harvester v1.9.1. The release was published on GitHub on November 10, 2026 and, as of November 13, is no longer flagged as a pre-release: the project’s “latest release” link now points to v1.9.1, which replaces v1.9.0 (September 16, 2026) as the current version in our VMware alternatives tracker. SUSE sells it as SUSE Virtualization, with support subscriptions and no per-CPU or per-VM fees.

Three features reach general availability in this point release: container workloads running directly on bare-metal Harvester nodes alongside VMs (through a Rancher feature flag), the LVM CSI driver for node-local storage, and Virtual Machine Auto Balance, which uses the Kubernetes Descheduler to move VMs off busy nodes. A new rancher-k3k add-on, still experimental, replaces the deprecated rancher-vcluster add-on for running Rancher inside the Harvester cluster.

Who this affects

Teams running Harvester as a VMware exit, and anyone evaluating it against Proxmox or the other KVM-based options in our KVM vs VMware guide. The upgrade note matters most: since v1.7.0, Harvester shut down any VM that could not be live-migrated during a node upgrade. v1.9.1 adds a shutdownVMOnMigrationFailure field to the upgrade-config setting, and the default is now false, so a VM that fails to migrate keeps running and the upgrade waits instead.

What to do now

  • Decide the migration-failure behavior before you upgrade. The new default pauses the upgrade on a stuck VM. If you want the old behavior, set the field to true with kubectl first; the Harvester UI does not expose it yet.
  • Check your LVM volumes. Pre-GA LVM volumes are incompatible with the GA driver and cannot be recovered after the upgrade, so back up and delete them first. VMs on node-local LVM volumes cannot live-migrate.
  • Plan the rancher-vcluster move. The add-on is deprecated in v1.9.1 and will be removed in v1.10.0. Harvester does not migrate its data to rancher-k3k, so you re-import the cluster and rebuild the Rancher configuration.
  • Schedule the upgrade for the security fixes. The base image picks up two kernel fixes in IPv4 networking, one of which the notes say could allow an escape from a KVM guest to the host.

Key details

ItemHarvester v1.9.0Harvester v1.9.1
Published on GitHubSeptember 16, 2026November 10, 2026 (pre-release flag removed by November 13)
Bare-metal container workloadsNot GAGeneral availability (Rancher feature flag)
LVM CSI driverPre-GA add-onGeneral availability; striped volumes deprecated
VM Auto BalancePre-GA add-onGeneral availability
Rancher inside Harvesterrancher-vcluster add-onrancher-k3k (experimental); rancher-vcluster deprecated, removed in v1.10.0
VM that fails live migration during upgradeShut down automaticallyKeeps running by default (shutdownVMOnMigrationFailure false)
Kernel security fixesn/aCVE-2026-99999 and CVE-2026-98432 (IPv4 networking)
LicensingOpen source; paid SUSE subscription for support, no per-CPU or per-VM fees (unchanged)

Source

Checked against the Harvester v1.9.1 release notes and the GitHub releases API on November 13, 2026.