xCAT/xcat-core
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-05-22 11:42:05 +00:00
Code Issues Releases Wiki Activity

improve document quality about the kvm

Browse Source
This commit is contained in:
penguhyang 2016-02-16 22:02:13 -05:00
parent b778331823
commit fb13e598f9
4 changed files with 13 additions and 42 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/source/guides/admin-guides/manage_clusters/common/kvm/manage_vm.rst
View File

@ -234,20 +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 the virtual machine
---------------------------
Migrate Virtual Machines
------------------------
**Migrate** is an operation that executing migration of a guest VM between hosts/hypervisors.
Virtual machine migration is a process that moves the virtual machines (guests) between different hypervisors (hosts).
Note: The directory used for storing disk images has to be mounted from shared storage on both vmhosts/hypervisors.
Note: The VM storage directory should be accessible from both hypervisors (hosts).
Migrate the VM "kvm1" to hypervisor "hyp02", which is managed by hypervisor "hyp01": ::
Migrate the VM "kvm1" from hypervisor "hyp01" to hypervisor "hyp02": ::
#rmigrate kvm1 hyp02
kvm1: migrated to hyp02
Migrate the VM "kvm1" to hypervisor "hyp02", which is already on host "hyp02": ::
#rmigrate kvm1 hyp02
kvm1: Guest is already on host hyp02

8
docs/source/guides/admin-guides/manage_clusters/ppc64le/virtual_machines/FAQ.rst
View File

@ -30,20 +30,20 @@ rpower fails with "Error: internal error Process exited while reading console lo
**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/2e66895a-e09a-53d5-74d3-eccdd9746eb5/vmXYZ.sda.qcow2: Permission denied"
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/kvm106.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/kvm106.sda.qcow2': Permission denied
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 policy in SELinux configuration. The solution is simply to disable SELinux on the vmhost/hypervisor by editing "/etc/selinux/config" and change the SELINUX line to SELINUX=disabled: ::
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 system and try to power on the VM again...
Then reboot the hypervisor...
"Error: Cannot communicate via libvirt to kvmhost1"
---------------------------------------------------

20
docs/source/guides/admin-guides/references/man1/rmigrate.1.rst
View File

@ -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. The directory used for storing disk images has to be mounted from shared storage on both vmhosts/hypervisors.
\ **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,30 +95,14 @@ This is used to determine the current host to migrate from.
****************
1. To migrate kvm guest "kvm1" to hypervisor "hyp02", which is managed by hypervisor "hyp01", enter:
1. To migrate kvm guest "kvm1" from hypervisor "hyp01" to hypervisor "hyp02", run:
\ **rmigrate**\ \ *kvm1*\ \ *hyp02*\
Output is similar to:
.. code-block:: perl
kvm1: migrated to hyp02
2. To migrate kvm guest "kvm1" to hypervisor "hyp02", which is already on host "hyp02", enter:
\ **rmigrate**\ \ *kvm1*\ \ *hyp02*\
Output is similar to:
.. code-block:: perl
kvm1: Guest is already on host hyp02
zVM specific:
=============

12
xCAT-client/pods/man1/rmigrate.1.pod
View File

@ -12,7 +12,7 @@ B<rmigrate> I<noderange> [B<destination=>I<target_host>] [B<action=>I<action>] [
=head1 B<Description>
B<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. The directory used for storing disk images has to be mounted from shared storage on both vmhosts/hypervisors.
B<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.
=head2 For zVM:
@ -52,22 +52,14 @@ This is used to determine the current host to migrate from.
=head1 B<Examples>
1. To migrate kvm guest "kvm1" to hypervisor "hyp02", which is managed by hypervisor "hyp01", enter:
1. To migrate kvm guest "kvm1" from hypervisor "hyp01" to hypervisor "hyp02", run:
B<rmigrate> I<kvm1> I<hyp02>
Output is similar to:
kvm1: migrated to hyp02
2. To migrate kvm guest "kvm1" to hypervisor "hyp02", which is already on host "hyp02", enter:
B<rmigrate> I<kvm1> I<hyp02>
Output is similar to:
kvm1: Guest is already on host hyp02
=head2 zVM specific:
=over 4