[one-users] write changes using "save as" and qcow2

[Andreas Calvo]

I does not get to the EPILOG state, so it's is not saving changes.
Do I have to enable the qcow driver in the datastore drivers?
-- 
Andreas Calvo Gómez
Systems Engineer
Scytl Secure Electronic Voting
Plaça Gal·la Placidia, 1-3, 1st floor · 08006 Barcelona
Phone: + 34 934 230 324
Fax:   + 34 933 251 028
http://www.scytl.com

NOTICE: The information in this e-mail and in any of its attachments is
confidential and intended solely for the attention and use of the named
addressee(s). If you are not the intended recipient, any disclosure,
copying,
distribution or retaining of this message or any part of it, without the
prior
written consent of Scytl Secure Electronic Voting, SA is prohibited and
may be
unlawful. If you have received this in error, please contact the sender
and
delete the material from any computer. 

On Fri, 2012-05-04 at 14:03 -0400, Shankhadeep Shome wrote:
> No you don't have to change image to persistent, it wouldn't change
> the running vm anyways. After the shutdown there are two more states,
> EPILOG and DONE. EPILOG is reached after the VM is completely shutdown
> and reported back, DONE is after the VM files are deleted from the
> system datastore, you should see both steps in the vm log. Maybe you
> can post the last few lines of the vm log, just go
> to /var/log/one/<vm#>.log on the opennebula server and post the last
> 20 lines.
> 
> On Fri, May 4, 2012 at 5:07 AM, Andreas Calvo
> <andreas.calvo at scytl.com> wrote:
>         What I see when I run the SHUTDOWN command is:
>         Fri May  4 11:03:11 2012 [LCM][I]: New VM state is SHUTDOWN
>         
>         Is there something else I should do?
>         Image is not marked as persistent, should it be changed?
>         
>         On Thu, 2012-05-03 at 23:51 -0400, Shankhadeep Shome wrote:
>         > If you use a qcow backing store this is what happens in the
>         background
>         >
>         > qemu-img create -backing_store (your original image) -f
>         qcow2 (running
>         > image)
>         >
>         > when you save as its
>         >
>         > qemu-img convert (running image + backing store) -O qcow2
>         (new base
>         > image)
>         >
>         > The vm log should look like this... check to see if you have
>         errors.
>         > How big is your source image? Conversion can take a while
>         depending on
>         > your image size and backing store.
>         >
>         > Thu May  3 23:41:28 2012 [LCM][I]: New VM state is SHUTDOWN
>         > Thu May  3 23:41:48 2012 [VMM][I]: ExitCode: 0
>         > Thu May  3 23:41:48 2012 [VMM][I]: Successfully execute
>         virtualization
>         > driver operation: shutdown.
>         > Thu May  3 23:41:48 2012 [VMM][I]: ExitCode: 0
>         > Thu May  3 23:41:48 2012 [VMM][I]: Successfully execute
>         network driver
>         > operation: clean.
>         > Thu May  3 23:41:49 2012 [LCM][I]: New VM state is EPILOG
>         > Thu May  3 23:42:42 2012 [TM][I]: mvds:
>         > Moving /var/lib/one/datastores/0/88/disk.0 to datastore
>         >
>         as /var/lib/one/datastores/101/4f062daaf6ad2f47fd36c6b35a0bd56c
>         > Thu May  3 23:42:42 2012 [TM][I]: ExitCode: 0
>         > Thu May  3 23:42:43 2012 [TM][I]: delete:
>         > Deleting /var/lib/one/datastores/0/88
>         > Thu May  3 23:42:43 2012 [TM][I]: ExitCode: 0
>         > Thu May  3 23:42:43 2012 [DiM][I]: New VM state is DONE
>         >
>         > On Thu, May 3, 2012 at 2:44 PM, Andreas Calvo
>         > <andreas.calvo at scytl.com> wrote:
>         > >
>         > > Hi all,
>         > > What is the procedure to save a running VM as an image if
>         it's
>         > running
>         > > with QCOW2?
>         > >
>         > > As per the documentation, I've used shutdown after issuing
>         save as,
>         > but
>         > > the image gets in a LOCKED stated and do not progress.
>         > > If the VM gets deleted, the image changes to READY but I
>         think it's
>         > just
>         > > a link to the old image used by the VM. Trying to start a
>         new
>         > template
>         > > using this new image throws an error.
>         > >
>         > > Tried with SHUTDOWN and STOP without luck.
>         > >
>         > > I guess I'm missing something, does anyone how to do it?
>         > >
>         > > Thanks in advance
>         > >
>         > > _______________________________________________
>         > > Users mailing list
>         > > Users at lists.opennebula.org
>         > >
>         http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>         >
>         
>         
>