[one-users] qcow2 image virtual size

Tobias Honacker t.honacker at googlemail.com
Tue May 14 11:06:32 PDT 2013


Hi guys,


the virtual size doesn't show up at the sunstone frontend while creating an
image with qcow2 format to LVM.


[oneadmin at xxx ~]$ onedatastore show 100

WARNING: Nokogiri was built against LibXML version 2.9.0, but has
dynamically loaded 2.9.1

DATASTORE 100 INFORMATION

ID             : 100

NAME           : production

USER           : oneadmin

GROUP          : oneadmin

CLUSTER        : -

TYPE           : IMAGE

DS_MAD         : lvm

TM_MAD         : lvm

BASE PATH      : /var/lib/one/datastores/100

DISK_TYPE      : FILE


I did the following steps:


1. [oneadmin at xxx iso]# qemu-img create –f qcow2 data.img 100G


2. [oneadmin at xxx iso]# qemu-img info data.img

image: data.img

file format: qcow2

virtual size: 100G (107374182400 bytes)

disk size: 136K

cluster_size: 65536


3. Login to Sunstone and create an image and provide the path from the
qcow2 file (data.img) + Advanced options and add driver qcow2


At the Dashboard the Storage doesn't grow up because the disk size of qcow2
images is 136K.

With raw files (qemu-img create –f raw data.img 100G) the disk size is 100G
and it works.

The qcow2 image was added successfully but the size is not 100G.



Any hints?



Best regards,

Tobias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20130514/d25bcf66/attachment.htm>


More information about the Users mailing list