Enabling shared/clustered disks within DomU's

• A shared clustered filesystem is needed between DomU's
• DomU cluster nodes needs access to a physical disk

• Used the virt-manager program or YaST to add any other virtual disks
• Used the vrit-manager program or YaST to change CPU or memory allocations
• Changed the disk allocation on the command line
• Changed the CPU or memory allocations on the command line.

After the initial install, if any post configuration of the guest outside the DomU (i.e., done by commands run in Dom0) then the virtual machine must be configured via xm commands. If any of the above conditions are true, using Method 1 will produce undesirable effects. For these reasons, SUSE recommends using the Python files (Method 2 or Method 3).

1. Go to /etc/xen/vm
2. Locate the line reading

   disk = [...
3. For each shared disk that you will be adding, append 'phy:/,,w!', before the closing , ] .
4. For example, to add a LVM backed devce in the System VG, named test, to be the second virtual disk would be:

   'phy:/dev/system/test,xvdb,w!'

   A complete example would be

   disk = ['file:/var/lib/xen/images/test/test,xvda,w','phy:/dev/system/test,xvdb,w!', ]
5. Save the file
6. Import the new file

   xm new -f sles10
7. Start the Xen VM
   xm start sles10

1. Export the Python configuration for the Xen DomU

   xm list -l SLES10 > sles10.py
2. Save a backup of the file Inca's something goes wrong
3. Open sles10.py for editing
4. After the last device listing for a vbd device, add the following:
   (device

   (vbd

   (driver paravirtualised)

   (dev xvdb:disk)

   (uname phy:/dev/system/test)

   (mode 'w!')

   (type disk)

   (backend 0)

   )

   )
5. Save and close the file
6. Import the new file

   xm new -F sles10.py
7. Start the Xen guest

   xm start sles10