Implementing live migration for virtual machine availability

A virtual machine (VM) can be migrated from one host to another host. This migration can be a live migration or pause migration. You can initiate the migration using:

If virtual machine migration is initiated outside VCS (either using the virsh commands or the RHEV-M web interface), VCS monitors the migrated guest and can detect the migration process. VCS changes the resource state according to the virtual machine state, i.e. if the guest is live-migrated from one host to another host, the associated KVMGuest resource is brought online on the host where the guest is migrated and on the source node the KVMGuest resource state is reported as OFFLINE (Intentional OFFLINE).

For the KVM environment, Veritas recommends the use of CVM and CFS for live migration where a virtual image needs to be simultaneously accessible on a source and destination node.

See Sample configuration in a KVM environment.

Cluster Server (VCS) has introduced a new migrate operation for initiating service group migration. The KVMGuest agent has implemented a "migrate" entry point to initiate virtual machine migration in KVM and RHEV environment. You can initiate a virtual machine live migration using the hagrp -migrate command.

The syntax for the command is:

#hagrp -migrate service_group_name -to destination_node_name

To verify the password-less SSH requirement for live migration

To configure VCS to initiate virtual machine migration

  1. To prepare for initiating a virtual machine live migration using hagrp -migrate command, you must configure the PhysicalServer attribute (system level) of VCS using following command:
    # hasys -modify  sys_name PhysicalServer physical_server_name

    For example:

    # haconf -makerw
    # hasys -modify sys_name PhysicalServer "'hostname'"

    The PhysicalServer name is used while initiating the migration.

  2. If PhysicalServer attribute is not configured, then the target node name passed to the migrate entry point is used for initiating the migration.

    The KVMGuest Agent migrate entry point:

    • For the KVM environment: Agent uses the virsh migrate command to initiate virtual machine migration.

    • For the RHEV environment: Agent uses REST APIs to initiate virtual machine migration. It also checks whether the virtual machine migration is allowed or not.

See About the KVMGuest agent.


When a virtual machine is configured for disaster recovery, the virtual machine cannot be migrated across sites.

See Sample configurations for a Red Hat Enterprise Virtualization (RHEV) environment.