build the chvm manpage according to the pod changes

docs/source/guides/admin-guides/references/man1/chvm.1.rst

@@ -49,6 +49,12 @@ PPC (using Direct FSP Management) specific:
                [\ **del_physlots=drc_index1,drc_index2...**\ ]
                [\ **del_vadapter=slotid**\ ]
 
+\ **chvm**\  \ *noderange*\  [\ **--cpupin**\  \ *hostcpuset*\ ]
+
+\ **chvm**\  \ *noderange*\  [\ **--membind**\  \ *numanodeset*\ ]
+
+\ **chvm**\  \ *noderange*\  [\ **--devpassthru**\  \ *pcidevice*\ ...]
+
 
 VMware/KVM specific:
 ====================
@@ -297,6 +303,34 @@ PPC (using Direct FSP Management) specific:
  
 
 
+\ **--cpupin hostcpuset**\ 
+ 
+ To pin guest domain virtual CPUs to physical host CPUs specified with \ *hostcpuset*\ .
+ \ *hostcpuset*\  is a list of physical CPU numbers. Its syntax is a comma separated list and a special
+ markup using '-' and '^' (ex. '0-4', '0-3,^2') can also be allowed. The '-' denotes the range and
+ the '^' denotes exclusive.
+ 
+ Note: The expression is sequentially evaluated, so "0-15,^8" is identical to "9-14,0-7,15" but not
+ identical to "^8,0-15".
+ 
+
+
+\ **--membind numanodeset**\ 
+ 
+ It is possible to restrict a guest to allocate memory from the specified set of NUMA nodes \ *numanodeset*\ . 
+ If the guest vCPUs are also pinned to a set of cores located on that same set of NUMA nodes, memory
+ access is local and improves memory access performance.
+ 
+
+
+\ **--devpassthru pcidevice1,pcidevice2...**\ 
+ 
+ The PCI passthrough gives a guest VM direct access to I/O devices \ *pcidevice1,pcidevice2...*\ . 
+ The PCI devices are assigned to a virtual machine, and the virtual machine can use this I/O exclusively.
+ The devices list are a list of comma separated PCI device names delimited with comma, the PCI device names can be obtained by running \ **virsh nodedev-list**\  on the host.
+ 
+
+
 
 VMware/KVM specific:
 ====================