From: Anthony Liguori <aliguori@cs.utexas.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Create the VMDK snapshot from the QEMU monitor.
Date: Tue, 26 Dec 2006 11:24:52 -0600 [thread overview]
Message-ID: <45915AE4.8050005@cs.utexas.edu> (raw)
In-Reply-To: <64F9B87B6B770947A9F8391472E0321609AB06E3@ehost011-8.exch011.intermedia.net>
Hi Igor,
Out of curiousity, why didn't you use the new snapshot infrastructure
that Fabrice introduced in CVS? Shouldn't the CID just map directly to
a snapshot tag?
Regards,
Anthony Liguori
Igor Lvovsky wrote:
>
> Hi,
>
> This patch completes the previous one and allows the snapshot (VMDK
> style) creation from the QEMU monitor (Ctrl+Alt+2).
>
>
>
> To clarify, the previous patch implements the snapshot capabilities
> according to the "Virtual Disk Format 1.0" document.
>
> http://lists.gnu.org/archive/html/qemu-devel/2006-12/msg00311.html
>
>
>
> Implemented features:
>
> 1. Create snapshot.
> 2. CID concept to prevent snapshots chain inconsistency.
> 3. Snapshots read/write capabilities.
>
>
>
> The whole chain (base image and snapshots) created by QEMU can be
> loaded from the VMware workstation and vice versa.
>
>
>
> Igor Lvovsky.
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
next prev parent reply other threads:[~2006-12-26 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-26 15:49 [Qemu-devel] [PATCH] Create the VMDK snapshot from the QEMU monitor Igor Lvovsky
2006-12-26 17:24 ` Anthony Liguori [this message]
2007-01-09 10:28 ` [Qemu-devel] [PATCH] Create the VMDK snapshot from the QEMUmonitor Igor Lvovsky
2007-01-09 16:20 ` Anthony Liguori
2007-01-09 19:40 ` Fabrice Bellard
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=45915AE4.8050005@cs.utexas.edu \
--to=aliguori@cs.utexas.edu \
--cc=qemu-devel@nongnu.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.