Migrating a virtual machine instance to another node
- Initiating live migration of a virtual machine instance in the web console
- Initiating live migration of a virtual machine instance in the CLI
Manually initiate a live migration of a virtual machine instance to another node using either the web console or the CLI.
Initiating live migration of a virtual machine instance in the web console
Migrate a running virtual machine instance to a different node in the cluster.
The Migrate Virtual Machine action is visible to all users but only admin users can initiate a virtual machine migration. |
Procedure
In the OKD Virtualization console, click Workloads → Virtualization from the side menu.
Click the Virtual Machines tab.
You can initiate the migration from this screen, which makes it easier to perform actions on multiple virtual machines in the one screen, or from the Virtual Machine Overview screen where you can view comprehensive details of the selected virtual machine:
Click the Options menu at the end of virtual machine and select Migrate Virtual Machine.
Click the virtual machine name to open the Virtual Machine Overview screen and click Actions → Migrate Virtual Machine.
Click Migrate to migrate the virtual machine to another node.
Initiating live migration of a virtual machine instance in the CLI
Initiate a live migration of a running virtual machine instance by creating a VirtualMachineInstanceMigration
object in the cluster and referencing the name of the virtual machine instance.
Procedure
Create a
VirtualMachineInstanceMigration
configuration file for the virtual machine instance to migrate. For example,vmi-migrate.yaml
:apiVersion: kubevirt.io/v1
kind: VirtualMachineInstanceMigration
metadata:
name: migration-job
spec:
vmiName: vmi-fedora
Create the object in the cluster by running the following command:
$ oc create -f vmi-migrate.yaml
The VirtualMachineInstanceMigration
object triggers a live migration of the virtual machine instance. This object exists in the cluster for as long as the virtual machine instance is running, unless manually deleted.
Additional resources: