2
0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-06-13 09:50:19 +00:00

fix some typo

This commit is contained in:
immarvin
2015-11-16 08:20:04 -05:00
parent 0021222f52
commit ce2054c596
3 changed files with 10 additions and 9 deletions

View File

@ -39,7 +39,7 @@ After the VM object is created, several key attributes need to be specified with
**Note**: For diskless node, the **vmmemory** should be at least 2048 MB, otherwise the node cannot boot up.
4. the hardware management module, "kvm" for powerKVM: ::
4. the hardware management module, "kvm" for PowerKVM: ::
chdef vm1 mgt=kvm
@ -174,7 +174,7 @@ When the VM has been created and powered on, please choose one of the following
wvid vm1
* For powerKVM, **kimchi** on the kvm hypervisor can be used to monitor and access the VM.
* For PowerKVM, **kimchi** on the kvm hypervisor can be used to monitor and access the VM.
Remove the virtual machine

View File

@ -1,4 +1,4 @@
Set Up the Management Server for KVM
Set Up the Management Node for KVM
====================================
@ -28,4 +28,4 @@ The easiest shared file system is ``/install`` directory on the management node,
echo "/install/vms *(rw,no_root_squash,sync,fsid=0)" >> /etc/exports
exportfs -r
**Note**: make sure the root permission is turned on for nfs clients (i.e. use the ``no_root_squash`` option). Otherwise, the virtual disk file can not work. The option ``fsid=0`` is useful for NFSv4.
**Note**: make sure the root permission is turned on for nfs clients (i.e. use the ``no_root_squash`` option). Otherwise, the virtual disk file can not work.

View File

@ -31,7 +31,7 @@ To demonstrate the brief steps on hypervisor provision, take **ibm-powerkvm-3.1.
#. Customize the hypervisor node definition to create network bridge
xCAT ships a postscript **xHRM** to create a network bridge on kvm host during installation/netbooting. Please specify the **xHRM** with appropraite parameters in **postscripts** attibute. Here is some examples on this:
xCAT ships a postscript **xHRM** to create a network bridge on kvm host during installation/netbooting. Please specify the **xHRM** with appropriate parameters in **postscripts** attibute. Here is some examples on this:
To create a bridge with default name 'default' against the installation network device which was specified by **installnic** attribute ::
@ -45,18 +45,19 @@ To demonstrate the brief steps on hypervisor provision, take **ibm-powerkvm-3.1.
chdef kvmhost1 -p postscripts="xHRM bridgeprereq eth0:br0"
**Note**: The network bridge name you specified should avoid ``virbr0,virbr1...``, which might have beem taken on the PowerKVM installation [1]_.
**Note**: The network bridge name you use should not be the virtual bridges created by libvirt installation [1]_.
#. Customize the hypervisor node definition to mount the shared kvm storage directory on management node(optional)
#. Customize the hypervisor node definition to mount the shared kvm storage directory on management node **(optional)**
If the shared kvm storage directory on the management node has been exported, it can be mounted on powerKVM hypervisor for virtual machines hosting.
If the shared kvm storage directory on the management node has been exported, it can be mounted on PowerKVM hypervisor for virtual machines hosting.
An easy way to do this is to create another postscript named "mountvms" which creates a directory **/install/vms** on hypervisor and then mounts **/install/vms** from the management node, the content of "mountvms" can be: ::
logger -t xcat "Install: setting vms mount in fstab"
mkdir -p /install/vms
echo "$MASTER:/install/vms /install/vms nfs rsize=8192,wsize=8192,timeo=14,intr,nfsvers=2 1 2" >> /etc/fstab
echo "$MASTER:/install/vms /install/vms nfs \
rsize=8192,wsize=8192,timeo=14,intr,nfsvers=2 1 2" >> /etc/fstab
Then set the file permission and specify the script in **postscripts** attribute of hypervisor node definition: ::