Hi,
On 2013-07-15 14:35, Ruben S. Montero wrote:
Hi Rolandas
So the problem is how to update the version of an image, right? We are
currently copying the new file to the SOURCE of the image something like:
cp debian_new.qcow2 `oneimage show debian | | grep SOURCE | cut -d':' -f2`
This way you do not need to modify the qcow driver.
As I wrote in http://mif.vu.lt/~rolnas/stsc/qcow2.txt we cannot simple
replace qcow2 image with cp or mv, because original image could still be
in use by some VM (referenced as backed file in snapshot qcow2). Until
VM is running it is OK, because original file is still open by kvm, but
when VM is stopped or turned off (power off), kvm process is terminated
and original file is deleted, but snapshot qcow2 is still referencing
original file by pathname.
Regards
Rolandas Naujikas
Does it make sense in your setup?
Cheers
Ruben
On Fri, Jul 5, 2013 at 9:42 AM, Rolandas Naujikas
<[email protected] <mailto:[email protected]>> wrote:
Hi,
For management of master images in qcow2 format we created a
solution described here http://mif.vu.lt/~rolnas/stsc/__qcow2.txt
<http://mif.vu.lt/%7Erolnas/stsc/qcow2.txt>. Hope it could solve
some management troubles and we are looking for improvements in
OpenNebula also.
Regards, Rolandas Naujikas
_________________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opennebula.org/__listinfo.cgi/users-opennebula.__org
--
<http://lists.opennebula.org/listinfo.cgi/users-opennebula.org>
--
Join us at OpenNebulaConf2013 in Berlin, 24-26 September, 2013
--
Ruben S. Montero, PhD
Project co-Lead and Chief Architect
OpenNebula - The Open Source Solution for Data Center Virtualization
<http://lists.opennebula.org/listinfo.cgi/users-opennebula.org>www.OpenNebula.org
<http://www.OpenNebula.org> | [email protected]
<mailto:[email protected]> | @OpenNebula
_______________________________________________
Users mailing list
[email protected]
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
