diff --git a/docs/source/guides/admin-guides/manage_clusters/common/kvm/manage_vm.rst b/docs/source/guides/admin-guides/manage_clusters/common/kvm/manage_vm.rst index 4c61f1dc4..273307a5b 100644 --- a/docs/source/guides/admin-guides/manage_clusters/common/kvm/manage_vm.rst +++ b/docs/source/guides/admin-guides/manage_clusters/common/kvm/manage_vm.rst @@ -234,3 +234,15 @@ Clone a VM "vm3" from the VM master "vm6" in detaching mode: :: #clonevm vm3 -b vm6 -d vm3: Cloning vm6.sda.qcow2 (currently is 1042.21875 MB and has a capacity of 4096MB) +Migrate Virtual Machines +------------------------ + +Virtual machine migration is a process that moves the virtual machines (guests) between different hypervisors (hosts). + +Note: The VM storage directory should be accessible from both hypervisors (hosts). + +Migrate the VM "kvm1" from hypervisor "hyp01" to hypervisor "hyp02": :: + + #rmigrate kvm1 hyp02 + kvm1: migrated to hyp02 + diff --git a/docs/source/guides/admin-guides/manage_clusters/ppc64le/virtual_machines/FAQ.rst b/docs/source/guides/admin-guides/manage_clusters/ppc64le/virtual_machines/FAQ.rst index cbc01fcd0..394c42664 100644 --- a/docs/source/guides/admin-guides/manage_clusters/ppc64le/virtual_machines/FAQ.rst +++ b/docs/source/guides/admin-guides/manage_clusters/ppc64le/virtual_machines/FAQ.rst @@ -11,8 +11,8 @@ VNC client complains the credentials are not valid **Solution**: Check whether the clocks on the hypervisor and headnode are synced -rpower fails with "qemu: could not open disk image /var/lib/xcat/pools/2e66895a-e09a-53d5-74d3-eccdd9746eb5/vmXYZ.sda.qcow2: Permission denied" ------------------------------------------------------------------------------------------------------------------------------------------------ +rpower fails with "Error: internal error Process exited while reading console log qemu: could not open disk image /var/lib/xcat/pools/2e66895a-e09a-53d5-74d3-eccdd9746eb5/vmXYZ.sda.qcow2: Permission denied" +-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- **Issue**: :: @@ -30,6 +30,21 @@ rpower fails with "qemu: could not open disk image /var/lib/xcat/pools/2e66895a- **Note**: For stateless hypervisor, please purge the VM by ``rmvm -p vm1``, reboot the hypervisor and then create the VM. +rpower fails with "Error: internal error: process exited while connecting to monitor qemu: could not open disk image /var/lib/xcat/pools/c7953a80-89ca-53c7-64fb-2dcfc549bd45/vmXYZ.sda.qcow2: Permission denied" +----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- + + **Issue**: :: + + #rpower vm1 on + vm1: Error: internal error: process exited while connecting to monitor: 2016-02-03T08:28:54.104601Z qemu-system-ppc64: -drive file=/var/lib/xcat/pools/c7953a80-89ca-53c7-64fb-2dcfc549bd45/vm1.sda.qcow2,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none: Could not open '/var/lib/xcat/pools/c7953a80-89ca-53c7-64fb-2dcfc549bd45/vm1.sda.qcow2': Permission denied + + **Solution**: + Usually caused by SELinux policies. The solution is simply to disable SELinux on the vmhost/hypervisor by editing "/etc/selinux/config" and change the SELINUX line to SELINUX=disabled: :: + + SELINUX=disabled + + Then reboot the hypervisor... + "Error: Cannot communicate via libvirt to kvmhost1" --------------------------------------------------- diff --git a/docs/source/guides/admin-guides/references/man1/rmigrate.1.rst b/docs/source/guides/admin-guides/references/man1/rmigrate.1.rst index 63e42c57e..f119cf28d 100644 --- a/docs/source/guides/admin-guides/references/man1/rmigrate.1.rst +++ b/docs/source/guides/admin-guides/references/man1/rmigrate.1.rst @@ -34,7 +34,7 @@ For zVM: ******************* -\ **rmigrate**\ requests that a guest VM be moved from the current entity hosting it to another. It requests a live migration be done, if possible. +\ **rmigrate**\ requests that a guest VM to be moved from the current hypervisor to another. It will request a live migration if possible. The vmstorage directory should be shared between the source and destination hypervisors. For zVM: ======== @@ -95,11 +95,13 @@ This is used to determine the current host to migrate from. **************** +1. To migrate kvm guest "kvm1" from hypervisor "hyp01" to hypervisor "hyp02", run: -.. code-block:: perl +\ **rmigrate**\ \ *kvm1*\ \ *hyp02*\ - rmigrate v1 n2 +2. To migrate kvm guest "kvm1" to hypervisor "hyp02", which is already on host "hyp02", enter: +\ **rmigrate**\ \ *kvm1*\ \ *hyp02*\ zVM specific: ============= diff --git a/xCAT-client/pods/man1/rmigrate.1.pod b/xCAT-client/pods/man1/rmigrate.1.pod index 29d969a91..083d2f9e9 100644 --- a/xCAT-client/pods/man1/rmigrate.1.pod +++ b/xCAT-client/pods/man1/rmigrate.1.pod @@ -12,7 +12,7 @@ B I [BI] [BI] [ =head1 B -B requests that a guest VM be moved from the current entity hosting it to another. It requests a live migration be done, if possible. +B requests that a guest VM to be moved from the current hypervisor to another. It will request a live migration if possible. The vmstorage directory should be shared between the source and destination hypervisors. =head2 For zVM: @@ -52,7 +52,13 @@ This is used to determine the current host to migrate from. =head1 B - rmigrate v1 n2 +1. To migrate kvm guest "kvm1" from hypervisor "hyp01" to hypervisor "hyp02", run: + +B I I + +2. To migrate kvm guest "kvm1" to hypervisor "hyp02", which is already on host "hyp02", enter: + +B I I =head2 zVM specific: