This content has been marked as final. Show 3 replies
First of all, OVMM won't recognize any disk as a physical disk, that has any kind of partitioning - just straight LUNs. That said, if you select the server in question and change the perspective on the right to "Physical disks", OVMM will show you what disks it has discovered on that server. If there are the disks/LUNs in your case, present, you can then start by creating a server pool, which will also some small LUN - depending on your needs, you could downsize it so as low as 10 GB.
So, to get started you will need at least 3 LUNs on your system:
a) LUN0 -> 20 GB for the OS
b) LUN1 -> 10 GB for the server pool fs
c) LUN2 -> ??? GB for the storage pool
If you should not see any physical disks on your server, it might be, that OVMM doesn't support the PERC controller. Please, also make sure, that your LUNs do appear on your VM server under /dev/mapper, since this is where OVMM actually scans for disks.
I have a VM manager on a LUN that is on a separate computer (which shouldn't matter). On the other computer I have 3 LUNs. One LUN is for the OS has the server pool OS and the other two are the data LUNs. And in the /dev/mapper directory, I see the two data LUNs:
[root@newora xen]# ls -l /dev/mapper/
brw-rw---- 1 root disk 252, 1 Oct 19 09:18 3690b11c005c83d00181424360e7323aa
brw-rw---- 1 root disk 252, 0 Oct 19 09:18 3690b11c005ce2f0017f550ce14db35e3
crw------- 1 root root 10, 236 Oct 19 09:18 control
But they still don't show up under the storage tab. So what now?
Turns out that there is a check box called "Clustered Server Pool". Once that was unchecked, I could continue with the install.