https://bugzilla.novell.com/show_bug.cgi?id=777387 https://bugzilla.novell.com/show_bug.cgi?id=777387#c2 --- Comment #2 from James Fehlig 2012-09-27 21:51:14 UTC --- (In reply to comment #0)

If I choose to manually create a qcow2 image, the option I would always pass (in combination with others) to qemu-image to avoid performance issues would be "preallocation=metadata". The option to create a qcow2 image with virsh or virt-manager with this option is simple not available.

Right. You can only specify allocation size. See http://libvirt.org/formatstorage.html#StorageVolFirst And, as you said, that seems to be ignored when the format type is qcow2: # cat dir-pool-vol.xml <volume type="file"> <name>full-alloc.img</name> <allocation unit="G">2</allocation> <capacity unit="G">2</capacity> <target> <path>/var/lib/libvirt/images/full-alloc.img</path> <format type='qcow2'/> ... # virsh vol-create default dir-pool-vol.xml # qemu-img info /var/lib/libvirt/images/full-alloc.img image: /var/lib/libvirt/images/full-alloc.img file format: qcow2 virtual size: 2.0G (2147483648 bytes) disk size: 136K cluster_size: 65536 But you can use your manually created images right?

I believe this is an upstream limitation rather than one specifically in the openSUSE virsh/libvirtd packages. I have no upstream issue # at the moment as I'm still wading through libvirt ML backlog.

Yes, AFAICT nothing has changed upstream. And I haven't seen any patches wrt this issues posted to the list. Woud you be interested in driving this upstream? libvirt is a friendly and helpful community :). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=777387 https://bugzilla.novell.com/show_bug.cgi?id=777387#c4 James Fehlig changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #4 from James Fehlig 2013-01-08 18:28:41 UTC --- Hi Graham, Seems someone beat you to this upstream http://libvirt.org/git/?p=libvirt.git;a=commit;h=1c9a2fb1aef1729ac86cd6648b5... http://libvirt.org/git/?p=libvirt.git;a=commit;h=790dfee5eaf8600282da5a3d61b... libvirt 1.0.1, which is now in Factory, contains these commits. Closing as fixed in 12.3. Thanks for the report. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.