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 <jingjie.jiang(a)oracle.com
<mailto:jingjie.jiang@oracle.com> wrote:
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
/rhev/data-center/mnt/blockSD/eaa6f641-6b36-4c1d-bf99-6ba77df3156f/images/8d3b455b-1da4-49f3-ba57-8cda64aa9dc9/949fa315-3934-4038-85f2-08aec52c1e2b
image:
/rhev/data-center/mnt/blockSD/eaa6f641-6b36-4c1d-bf99-6ba77df3156f/images/8d3b455b-1da4-49f3-ba57-8cda64aa9dc9/949fa315-3934-4038-85f2-08aec52c1e2b
file format: raw
virtual size: 10G (10737418240 bytes)
disk size: 0
I tried on iscsi and same result.
Is the behaviour expected?
It is expected in a way. Disk size is the amount of storage actually
used, and block devices has no way to tell that.
oVirt report the size of the block device in this case, which is more
accurate than zero.
However the real size allocated on the undrelying storage is somewhere
between zero an device size, and depends on the imlementation of the
storage. Nither qemu-img nor oVirt can tell the real size.
Nir
Thanks,
Jingjie
_______________________________________________
Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
To unsubscribe send an email to users-leave(a)ovirt.org
<mailto:users-leave@ovirt.org>
Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/TSXP7RENWIF...