From: Paolo Bonzini <bonzini@gnu.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] save/restore broken?
Date: Tue, 11 Aug 2009 18:39:47 +0200 [thread overview]
Message-ID: <h5s6sk$ema$1@ger.gmane.org> (raw)
Hi all,
if I try to save and restore an image using current qemu and current
libvirt, the load fails. Comparing a preexisting save file and the new
save file generated by QEMU master, I get differences in an ide block
like this (cmp output):
67500802 0 20
67500803 20 0
67500808 0 1
67500809 1 0
67500812 0 10
67500813 10 47
67500814 47 374
67500815 374 232
67500816 232 0
67500821 0 360
67500822 360 120
67500823 120 0
67500828 0 20
67500830 20 0
67500832 0 1
67500833 0 300
67500834 1 205
67500835 300 0
67500836 205 0
The IDE section starts at 67499922 (this is where the 0x00000004
signature is, so the error is 880 bytes inside the IDE block including
the section headers).
I could not pinpoint any obvious culprit in the log. Hope this helps.
Paolo
next reply other threads:[~2009-08-11 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 16:39 Paolo Bonzini [this message]
2009-08-13 18:48 ` [Qemu-devel] save/restore broken? Luiz Capitulino
2009-08-13 18:59 ` Anthony Liguori
2009-08-13 19:55 ` Gleb Natapov
2009-08-13 20:08 ` Luiz Capitulino
2009-08-13 19:23 ` [Qemu-devel] " Juan Quintela
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='h5s6sk$ema$1@ger.gmane.org' \
--to=bonzini@gnu.org \
--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.