Choosing Live Migration vs Cold Migration in Harvester: A Decision Guide
Decide between Harvester live migration and cold migration by reviewing storage, CPU, network constraints, trade‑offs, and a step‑by‑step validation guide.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Decide between Harvester live migration and cold migration by reviewing storage, CPU, network constraints, trade‑offs, and a step‑by‑step validation guide.
Live migration in Harvester is a storage and capacity decision before it is a UI action. Learn the Longhorn prerequisites, KubeVirt migration checks, and a repeatable node-maintenance runbook.
Learn how Harvester uses Longhorn to provide distributed block storage for VMs, ensuring high availability through synchronous replication and dynamic volume expansion.
Need to patch a Harvester node without killing VMs? Live migration moves VM memory between nodes using KubeVirt and shared storage, but only with compatible CPUs and no device passthrough.
Identify why Harvester isn’t sending logs to Loki or Elasticsearch and follow ordered checks to resolve connection, auth, or config issues.
Use Rook‑Ceph RBD with Harvester to give VMs distributed, highly available block storage. This guide walks through deployment, provisioning, and trade‑offs.
Harvester live migration moves running VMs between nodes using Longhorn storage and Calico networking, but device passthrough, hostPath volumes, and custom CPU models block it. Learn how to check eligibility, trigger migration, and verify zero‑downtime success.
An architecture note covering Harvester’s integrated KubeVirt and Longhorn design: requirements, minimal viable layout, trust boundaries, operational checks, failure modes, and redesign triggers.
Learn how Harvester uses KubeVirt and Longhorn to build a resilient HCI. This guide covers the 3-node minimum design, trust boundaries, and how to verify storage failover.