[ovirt-users] Re: qemu-img info showed iscsi/FC lun size 0

On Wed, Mar 13, 2019 at 8:40 PM Jingjie Jiang wrote: > Hi Nir, > > I had qcow2 on FC, but qemu-img still showed size is 0. > > # qemu-img info > /rhev/data-center/mnt/blockSD/eaa6f641-6b36-4c1d-bf99-6ba77df3156f/images/38cdceea-45d9-4616-8eef-966acff2f7be/8a32c5af-f01f-48f4-9329-e173ad3483b1 > >

[ovirt-users] Re: qemu-img info showed iscsi/FC lun size 0

Hi Nir, I had qcow2 on FC, but qemu-img still showed size is 0. # qemu-img info /rhev/data-center/mnt/blockSD/eaa6f641-6b36-4c1d-bf99-6ba77df3156f/images/38cdceea-45d9-4616-8eef-966acff2f7be/8a32c5af-f01f-48f4-9329-e173ad3483b1 image:

[ovirt-users] Re: qemu-img info showed iscsi/FC lun size 0

On Fri, Feb 22, 2019 at 7:14 PM Nir Soffer wrote: > On Fri, Feb 22, 2019 at 5:00 PM Jingjie Jiang > wrote: > >> What about qcow2 format? >> > qcow2 reports the real size regardless of the underlying storage, since qcow2 manages the allocations. However the size is reported in qemu-img check in

[ovirt-users] Re: qemu-img info showed iscsi/FC lun size 0

On Fri, Feb 22, 2019 at 5:00 PM Jingjie Jiang wrote: > What about qcow2 format? > > Is there a choice to create vm disk with format qcow2 instead of raw? > Not for LUNs, only for images. The available formats in 4.3 are documented here:

[ovirt-users] Re: qemu-img info showed iscsi/FC lun size 0

Hi Nir, Thanks for your reply. What about qcow2 format? Is there a choice  to create vm disk with format qcow2 instead of raw? Thanks, Jingjie On 2/21/19 5:46 PM, Nir Soffer wrote: On Thu, Feb 21, 2019, 21:48 wrote: Hi, Based on oVirt 4.3.0,

[ovirt-users] Re: qemu-img info showed iscsi/FC lun size 0

On Thu, Feb 21, 2019, 21:48 Hi, > Based on oVirt 4.3.0, I have data domain from FC lun, then I create new vm > on the disk from FC data domain. > After VM was created. According to qemu-img info, the disk size is 0. > # qemu-img info >