From: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: KVM management and API
Date: Sun, 29 Apr 2007 10:46:50 -0500 [thread overview]
Message-ID: <4634BDEA.1020809@codemonkey.ws> (raw)
In-Reply-To: <4634515B.6020301-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Avi Kivity wrote:
> Anthony Liguori wrote:
>> 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.
>>
>
> How does that work when you have two qcow2 images attached to a guest?
The first disk that supports snapshots is used to store the CPU state.
All disks that can be snapshotted are snapshotted with the same tag.
Regards,
Anthony Liguori
-------------------------------------------------------------------------
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-29 15:46 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
[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 [this message]
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=4634BDEA.1020809@codemonkey.ws \
--to=anthony-rdkfgonbjusknkdkm+me6a@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.