xCAT/xcat-core
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-06-13 01:40:26 +00:00
Code Issues Releases Wiki Activity

Remove trailing spaces in file docs/source/guides/admin-guides/manage_clusters/ppc64le/virtual_machines/FAQ.rst

Browse Source
This commit is contained in:
GONG Jie
2017-12-31 23:59:59 +00:00
parent 8fddc1d44e
commit 3eade799ed
1 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -5,13 +5,13 @@ Trouble Shooting
VNC client complains the credentials are not valid
--------------------------------------------------
**Issue**:
**Issue**:
While connecting to the hypervisor with VNC, the vnc client complains "Authentication failed".
**Solution**:
**Solution**:
Check whether the clocks on the hypervisor and headnode are synced
rpower fails with "Error: internal error Process exited while reading console log qemu: Permission denied"
rpower fails with "Error: internal error Process exited while reading console log qemu: Permission denied"
----------------------------------------------------------------------------------------------------------
**Issue**: ::
@ -21,13 +21,13 @@ rpower fails with "Error: internal error Process exited while reading console lo
qemu: could not open disk image /var/lib/xcat/pools/2e66895a-e09a-53d5-74d3-eccdd9746eb5/vm1.sda.qcow2: Permission denied: internal error Process exited while reading console log output: char device redirected to /dev/pts/1
qemu: could not open disk image /var/lib/xcat/pools/2e66895a-e09a-53d5-74d3-eccdd9746eb5/vm1.sda.qcow2: Permission denied
**Solution**:
**Solution**:
Usually caused by incorrect permission in NFS server/client configuration. NFSv4 is enabled in some Linux distributions such as CentOS6 by default. The solution is simply to disable NFSv4 support on the NFS server by uncommenting the following line in "/etc/sysconfig/nfs": ::
RPCNFSDARGS="-N 4"
Then restart the NFS services and try to power on the VM again...
**Note**: For stateless hypervisor, 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: Permission denied"
@ -73,23 +73,23 @@ rmigrate fails with "Error: 38, message: failed to create directory '<dir-name>'
Error: Cannot communicate via libvirt to kvmhost1
-------------------------------------------------
**Issue**:
**Issue**:
The kvm related commands complain "Error: Cannot communicate via libvirt to kvmhost1"
**Solution**:
**Solution**:
Usually caused by incorrect ssh configuration between xCAT management node and hypervisor. Make sure it is possible to access the hypervisor from management node via ssh without password.
Fail to ping the installed VM
-----------------------------
**Issue**:
**Issue**:
The newly installed stateful VM node is not pingable, the following message can be observed in the console during VM booting: ::
ADDRCONF(NETDEV_UP): eth0 link is not ready.
**Solution**:
Usually caused by the incorrect VM NIC model. Try the following steps to specify "virtio": ::
**Solution**:
Usually caused by the incorrect VM NIC model. Try the following steps to specify "virtio": ::
rmvm vm1
chdef vm1 vmnicnicmodel=virtio