Hi! I'm just in process of setting up an ovirt environment again. Using ovirt node HV 2.3.0, on fibre channel storage. I'm forced to use Fedora 16, since Fedora 17 doesn't work with fibre channel storage or at least not with Qlogic HBA's. I've allready told the list and Fedora forum that. I asked some related questions before around fc storage with oVirt, and I will be back with more. Anyway, I set up the oVirt node HV on a single LUN of 2 Gb, I've done it before on 1 Gb, and I tried it on 200 Mb. 200 Mb was too small, because it stopped at 25% and didn't want to go further. But the installation started without reporting it beeing too small, which is a bit odd, isn't it? Anyway, 1 or 2 Gb works fine! When I enter the shell in the HV and run pvs the first time, I see this: [root@node1 admin]# pvs  PV                                              VG     Fmt  Attr PSize   PFree  /dev/mapper/3600144f0e03a46000000501798dd0001p4 HostVG lvm2 a--  288.00m    0 PSize say's 288.00m. LUN is a thin provisioned LUN made from qcow2 zfs, so maybe it only reports the size that are used? Anyway, I just added a second LUN, for using as VM storage. Here you can see: [root@node1 admin]# cat /proc/scsi/scsi Attached devices: Host: scsi1 Channel: 00 Id: 00 Lun: 00  Vendor: HL-DT-ST Model: RW/DVD GCC-T10N  Rev: 1.00  Type:   CD-ROM                           ANSI  SCSI revision: 05 Host: scsi2 Channel: 00 Id: 00 Lun: 00  Vendor: OI       Model: COMSTAR          Rev: 1.0   Type:   Direct-Access                    ANSI  SCSI revision: 05 Host: scsi2 Channel: 00 Id: 00 Lun: 01  Vendor: OI       Model: COMSTAR          Rev: 1.0   Type:   Direct-Access                    ANSI  SCSI revision: 05 [root@node1 admin]# But when I run pvs again in the HV, the new LUN doesn't show up. Note that I restarted the HV, because I ran pvs also before restarting it, and thought I needed to restart it for beeing able to see it through LVM. But LVM haven't yet touched it, or perhaps not seen it? Is it so that LVM on the HV doesn't see other LUN's than the first LUN, if it is not there during installation? Last time I installed, I did the opposite, I installed with system LUN and with data LUN, and then LVM could see both LUN's, though I couldn't use the data LUN for storage. I've allready reported that. So I wonder what is the right way of doing it, install with only system LUN and than add data LUN after, or install with both system LUN and data LUN? I suppose it would be the best if both way's worked? I get back with more info later, when I tried to connect the storage LUN through the engine... Rgrds Johan