From: Stefan Hajnoczi <stefanha@gmail.com>
To: chandra shekar <chandrashekar512@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] snapshots
Date: Fri, 7 Jan 2011 09:54:03 +0000 [thread overview]
Message-ID: <AANLkTi=b1wcSsGcmon8Fo=xSE5Xn0b0heOfscPDAhjHD@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikfR_C4Ww5nuY_Um7jozH2g+8mO4yyHRDe90yen@mail.gmail.com>
On Fri, Jan 7, 2011 at 4:37 AM, chandra shekar
<chandrashekar512@gmail.com> wrote:
> hi everyone i have got snapshot out of the image file now i would like to
> analyze the snapshot
> like opening it or identifying the fields in it can anyone suggest any
> softwares which i can use
> to open the snapshot analyze it,thanks
I'm not sure what format your snapshot data is in. What exactly did you do?
qemu-img and qemu-io can be used to manipulate image data.
Check what format the data is in:
qemu-img info <snapshot-file>
Read first sector (for debugging):
qemu-io -c 'read -v 0 512' <snapshot-file>
Convert to raw image (suitable for dd, fdisk, hex editor, etc):
qemu-img convert <snapshot-file> raw-data.img
If you want to inspect savevm data (saved device state) then you're on
your own. AFAIK there isn't an external tool to dissect it. It would
be quickest to add some code into QEMU to dump out the info you need.
Stefan
next prev parent reply other threads:[~2011-01-07 9:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 4:37 [Qemu-devel] snapshots chandra shekar
2011-01-07 9:54 ` Stefan Hajnoczi [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-14 10:22 chandra shekar
2010-10-14 16:51 ` Mulyadi Santosa
2010-10-12 9:13 chandra shekar
2010-10-12 9:46 ` Stefan Hajnoczi
2010-10-04 4:56 chandra shekar
2010-10-05 4:44 ` Mulyadi Santosa
2010-09-27 5:47 chandra shekar
2010-09-28 2:03 ` edison
2005-05-23 8:04 Pascal Terjan
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='AANLkTi=b1wcSsGcmon8Fo=xSE5Xn0b0heOfscPDAhjHD@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=chandrashekar512@gmail.com \
--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 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).