Relocating virtual disks to file systems other than dom0:/OVS/running_pool

Question

It looks like the best approach for having multiple large file systems mounted within a domU is by:
1.) Use VM Mgr to create dummy virtual disk (within dom0:/OVS/running_pool/domU)
2.a) if size of dummy is large enough, cp it to a different file system within domU
2.b) if size of dummy is too small, create a new file on different file system within domU using dd
3.) Replace dummy virtual disk file (within dom0:/OVS...) with symbolic link that reference the new replacement file.
Are others doing this? Is there a better way?
Does it cause problems?
is there a way to update VM Mgr to show the correct size if the virt disk is enlarged from the size of the original dummy virtual disk?
Thx...
Edited by: twtuck on Mar 9, 2009 8:29 AM

Answer 1

You can use the /usr/lib/ovs/ovs-makerepo script to add additional repositories under the /OVS mount point. The script takes a block device as a parameter. For example, to create a new shared location on /dev/mapper/mpath1p1, you would run:
# /usr/lib/ovs/ovs-makerepo /dev/mapper/mpath1p1 1 "Shared Storage"
These repositories are then visible to Oracle VM and VM Manager. It will use the repository with the most amount of available space to create your guests for you.