From: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
To: "Daniel P. Berrange" <berrange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: KVM management and API
Date: Fri, 27 Apr 2007 17:23:31 -0500 [thread overview]
Message-ID: <463277E3.5070305@codemonkey.ws> (raw)
In-Reply-To: <20070427220657.GB8384-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Daniel P. Berrange wrote:
>> 5. Snapshots : where are snapshots saved ? I tried savevm with /tmp/x, I was expecting a
>> file containing memory image... do these work differrently ?
>> Also, when one does loadvm, is the snapshot gone ? I mean can one restore the same
>> snapshot multiple times ?
>>
>
> libvirt has APIs for snapshotting, but we've not implement them for QEMU
> or KVM yet. You can save the file to any location you have write permissions
> for. Its not a plain memory image because it also contains info about the
> state of all the various virtual devices.
>
> The snapshot doesn't deal with changes in state on your disks. So if you restored
> a snapshot, ran it for a while doing disk IO and then quit & tried to restore the
> snapshot again your disks would be out of sync.
>
> That said if one could take snapshots of the disks (eg with LVM, or QCOW) then
> it ought to be possible to use a snapshot multiple times over.
>
With QEMU 0.9.0 (and by extension, KVM), snapshots are actually stored
as part of the disk image with qcow2. This allows you to have a
consistent snapshot that includes CPU state and disk state.
Regards,
Anthony Liguori
> Dan.
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-04-27 22:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 21:29 KVM management and API jd
[not found] ` <798858.14143.qm-sSuf+AbrE5qvuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2007-04-27 22:06 ` Daniel P. Berrange
[not found] ` <20070427220657.GB8384-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-04-27 22:23 ` Anthony Liguori [this message]
[not found] ` <463277E3.5070305-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-04-29 8:03 ` Avi Kivity
[not found] ` <4634515B.6020301-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-29 15:46 ` Anthony Liguori
2007-05-01 7:31 ` Dor Laor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=463277E3.5070305@codemonkey.ws \
--to=anthony-rdkfgonbjusknkdkm+me6a@public.gmane.org \
--cc=berrange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox