Open Stack

On Thu, Jun 30, 2011 at 07:32:38PM +0900, masumotok at nttdata.co.jp wrote:
> 
> > I'm afraid we are not on same page. What API layer are you talking about?
> > I suppose we're talking about totally different thing.
> > 
> > What I ment by qemu savevm is the command which is typed on qemu command line.
> > Whose prompt is "(qemu)". qemu savevm doesn't terminates the instance, and
> > the guest continues executing after savevm.
> > By looking at libvirt code I confirmed that libvirt API
> > virDomainSnapshotCreateXML() eventually issues qemu command, savevm, on the
> > qemu monitor(HMP).
> > 
> 
> Ops. I was thinking you mentioned "virsh save". That's seems to be my misunderstanding. BTW, using virDomainSnapshotCreateXML() is different from current implementation of snapshot() in libvirt driver? 

Really? From nova/virt/libvirt/connection.py

   388      def snapshot(self, instance, image_href):
   389          """Create snapshot from a running VM instance.
...
   430          snapshot_ptr = virt_dom.snapshotCreateXML(snapshot_xml, 0)


-- 
yamahata