Should we add 'cow' format disk in file domains in frontend UI ?
Hello, We had experience that if we clone vm from snapshot with sprase raw disk in file domains, the process would get very slow if the disk defined virtual size is big but actual size is small, so i popose the frontend UI to be able to add caw disk in file domains. And I'm happy to implement it. I want to know if there is any problem with my theory, I'm not so experienced in storage. And I created a more detailed expanation to address this problem: https://bugzilla.redhat.com/show_bug.cgi?id=1117219 thanks.
IMHO definitely! I use qcow2 since years and consider it the superior format for most use cases; esp. when I run in export times for disk images of about 4h/TB of raw disk space with less then 5GB consumed actually. I would consder this as a big step forward for a ovit production installation. Thanks! On 01.09.2014 12:01, plysan wrote:
Hello,
We had experience that if we clone vm from snapshot with sprase raw disk in file domains, the process would get very slow if the disk defined virtual size is big but actual size is small, so i popose the frontend UI to be able to add caw disk in file domains.
And I'm happy to implement it. I want to know if there is any problem with my theory, I'm not so experienced in storage. And I created a more detailed expanation to address this problem: https://bugzilla.redhat.com/show_bug.cgi?id=1117219
thanks.
-- Daniel Helgenberger m box bewegtbild GmbH P: +49/30/2408781-22 F: +49/30/2408781-10 ACKERSTR. 19 D-10115 BERLIN www.m-box.de www.monkeymen.tv Geschäftsführer: Martin Retschitzegger / Michaela Göllner Handeslregister: Amtsgericht Charlottenburg / HRB 112767
Offhand, sounds both useful and easy to do. I marked the BZ with 3.6.0, and we'll revisit when we plan the 3.6.0 version. Of course, if someone wants to contribute patches *wink wink, hint hint*. ----- Original Message -----
From: "Daniel Helgenberger" <daniel.helgenberger@m-box.de> To: "Users@ovirt.org List" <users@ovirt.org> Sent: Monday, September 1, 2014 6:11:00 PM Subject: Re: [ovirt-users] Should we add 'cow' format disk in file domains in frontend UI ?
IMHO definitely!
I use qcow2 since years and consider it the superior format for most use cases; esp. when I run in export times for disk images of about 4h/TB of raw disk space with less then 5GB consumed actually.
I would consder this as a big step forward for a ovit production installation.
Thanks!
On 01.09.2014 12:01, plysan wrote:
Hello,
We had experience that if we clone vm from snapshot with sprase raw disk in file domains, the process would get very slow if the disk defined virtual size is big but actual size is small, so i popose the frontend UI to be able to add caw disk in file domains.
And I'm happy to implement it. I want to know if there is any problem with my theory, I'm not so experienced in storage. And I created a more detailed expanation to address this problem: https://bugzilla.redhat.com/show_bug.cgi?id=1117219
thanks.
-- Daniel Helgenberger m box bewegtbild GmbH
P: +49/30/2408781-22 F: +49/30/2408781-10
ACKERSTR. 19 D-10115 BERLIN
www.m-box.de www.monkeymen.tv
Geschäftsführer: Martin Retschitzegger / Michaela Göllner Handeslregister: Amtsgericht Charlottenburg / HRB 112767
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (3)
-
Allon Mureinik -
Daniel Helgenberger -
plysan