user12019148 wrote:Read all about [Preparing External Storage and Storage Repositories|http://download.oracle.com/docs/cd/E15458_01/doc.22/e15444/storage.htm#sthref68] in the Oracle VM manual.
How to add new/more disk to Oracle VM?
user12019148 wrote:Did you run ./repos.py -i to initialize this new repository? What is the output of ./repos.py -l? Once the new repository is visible to Oracle VM, it should allow you to create a new disk. However, there is a limitation: if you want to create a new 500GB disk, but the filesystem on which your guest is installed doesn't have that much space available, it will fail. The workaround is to create the disk as a "Shared Virtual Disk" (which can exist in any repository), but only assign it to a single guest.
NOw Since I am using iscsi I need to create new repository. I created New storage and new repository using fdisk and mkfs.ocfs2 and repos.py ....
user12019148 wrote:Yes, and yes.
I can add disks to Vm but limited to free disk available in same repository where Vm is Installed.
Or I can add new repository and then create virtual machine with disk size 500GB . In this case, it will create new virtual machine in new repository.
Also does /etc/ovs/ovsrepositorities exists?Not on Oracle VM 2.2 any more.
Isn't it possible to add new disk to same repository?No. Each disk that is presented to Oracle VM has to be created as a single repository. This includes NFS mounts, SAN LUNs or iSCSI volumes. But, you can have multiple repositories on a single server or across a pool of servers.
user12019148 wrote:I'm not sure, to be honest. It may be in My Oracle Support, which requires a subscription for access. I'll make a note of this thread and fling it to our documentation author with the hope of getting it added when the documentation is reviewed.
Is there any guide where it says limitation of creating repositories/disks/files?
user4806362 wrote:The document talks about external storage, which is most often used for shared/HA configurations. However, you just need to follow the documentation as if you were creating shared storage but you only do it for your single server. There is no way currently to view/manage repository information from within the Manager utility.
I'm not getting it either. I'm on 2.2, not using HA, don't need anything shared, just one single host where I want to create some VMs. The doc isn't clear at all and is aimed at people who want shared storage or HA.
During the installation, do I want to make these for LUNs available to Server, or not?Yes or no, but probably not: you don't mention if your server has any local storage or not. If it does, you'd only want to use that local storage during installation. This will ensure your server can at least boot if your SAN is offline. If you have no local storage, you're in SAN boot territory and would need to only use a single LUN during installation. Once you've finished the installation, you can then chose what to do with the additional LUNs: the installer does not automatically create repositories for them.
In /proc/partitions I see many sd* devices as well as dm-0 through dm-3. ll /dev/mapper shows mpath0 through mpath3 as well as four VG_XenStorage--... entries. Which do I want?I'm curious as to why you have four VG_XenStorage entries. Those look like LVM volume groups/logical volumes and should not have been created by the installer. Did you configure LVM manually during install? Most often, you'd use the /dev/mapper/mpathX devices, though. You would however need to partition them using fdisk so that you see /dev/mapper/mpath0p0 for example.
If I install them as unavailable then try to mkfs.ocfs2 /dev/dm-0 or /dev/sdp, it reports that it's apparently in use. I can use -F to force it, then /opt/ovs-agent-2.3/utils/repos.py -i works. But there's nothing under /OVS.The process to add /dev/mapper/mpath0 would be:
user4806362 wrote:There should be four UUID directories under /var/ovs/mount, one for each LUN: Oracle VM does not group LUNs together by default. If you did this manually with LVM, then you would need to remove all the LVM components to see the four individual LUNs again. Once you do that, you can add and initialise each LUN.
I now see that the hypervisor automatically grouped the four LUNs into one metaLUN at /var/ovs/mount/BE9.... Is there a way to break this metaLUN out into the four separate LUNs so I can pick and choose which VMs reside on which LUNs?