[Bug 777387] New: virsh / virt-manager: lacking qcow2 image preallocation options
https://bugzilla.novell.com/show_bug.cgi?id=777387 https://bugzilla.novell.com/show_bug.cgi?id=777387#c0 Summary: virsh / virt-manager: lacking qcow2 image preallocation options Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: graham@andtech.eu QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1226.0 Safari/537.4 SUSE/22.0.1226.0 It is not currently possible to create a KVM volume in the qcow2 image format with full metadata preallocation via virt-manager GUI app or the virsh shell/command line. 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. In practical terms, if you wish not to have very poorly performing disk IO in any KVM guest domain, you must choose a raw image format and something like an LVM storage pool. A directory based pool is not an option if you wish to also snapshot your guests. 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. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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#c Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse-beta@cboltz.de AssignedTo|bnc-team-screening@forge.pr |carnold@suse.com |ovo.novell.com | -- 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#c2 --- Comment #2 from James Fehlig <jfehlig@suse.com> 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#c3 --- Comment #3 from Graham Anderson <graham@andtech.eu> 2012-10-05 21:28:00 UTC --- (In reply to comment #2)
But you can use your manually created images right?
Yep, without issue.
Would you be interested in driving this upstream?
Sure, but I'm right in the middle of relocating country and traveling so I'll likely not pick this up for a couple of weeks. -- 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 <jfehlig@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #4 from James Fehlig <jfehlig@suse.com> 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.
participants (1)
-
bugzilla_noreply＠novell.com