From: Shu Ming <shuming@linux.vnet.ibm.com>
To: ¤終於aware <250716708@qq.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [help] QEMUFile's format
Date: Fri, 23 Dec 2011 13:32:50 +0800 [thread overview]
Message-ID: <4EF41282.4010603@linux.vnet.ibm.com> (raw)
In-Reply-To: <tencent_37EF499B2FBF40764715DEA6@qq.com>
Do you mean the file format? qcow2, qed, raw? Or the content layout in
the file image?
On 2011-12-23 13:17, ¤終於aware wrote:
> Hi,
> Is anyone clear about the format of qemu file for savevm or loadvm?
> bruce
--
Shu Ming<shuming@linux.vnet.ibm.com>
IBM China Systems and Technology Laboratory
next prev parent reply other threads:[~2011-12-23 5:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 5:17 [Qemu-devel] [help] QEMUFile's format ¤終於aware
2011-12-23 5:32 ` Shu Ming [this message]
2011-12-23 6:03 ` 陳韋任
2011-12-23 6:05 ` 陳韋任
2011-12-23 6:09 ` Dong Xu Wang
2011-12-30 11:16 ` Stefan Hajnoczi
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=4EF41282.4010603@linux.vnet.ibm.com \
--to=shuming@linux.vnet.ibm.com \
--cc=250716708@qq.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xensource.com \
/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;
as well as URLs for NNTP newsgroup(s).