From: Kevin Wolf <kwolf@suse.de>
To: Jamie Lokier <jamie@shareable.org>
Cc: qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] qcow2 corruption observed, fixed by reverting old change
Date: Wed, 11 Feb 2009 10:57:28 +0100 [thread overview]
Message-ID: <4992A108.8070304@suse.de> (raw)
In-Reply-To: <20090211070049.GA27821@shareable.org>
Jamie Lokier schrieb:
> Although there are many ways to make Windows blue screen in KVM, in
> this case I've narrowed it down to the difference in
> qemu/block-qcow2.c between kvm-72 and kvm-73 (not -83).
This must be one of SVN revisions 5003 to 5008 in upstream qemu. Can you
narrow it down to one of these? I certainly don't feel like reviewing
all of them once again.
Do I understand correctly that your image fails with the kvm-73 version
of block-qcow2.c and afterwards boots with kvm-72? So the image is not
really corrupted but it's more likely an IO error which brings the OS down?
Kevin
next prev parent reply other threads:[~2009-02-11 9:50 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 7:00 qcow2 corruption observed, fixed by reverting old change Jamie Lokier
2009-02-11 7:00 ` [Qemu-devel] " Jamie Lokier
2009-02-11 9:57 ` Kevin Wolf [this message]
2009-02-11 11:27 ` Jamie Lokier
2009-02-11 11:27 ` Jamie Lokier
2009-02-11 11:41 ` Jamie Lokier
2009-02-11 11:41 ` Jamie Lokier
2009-02-11 12:41 ` Kevin Wolf
2009-02-11 12:41 ` Kevin Wolf
2009-02-11 16:48 ` Jamie Lokier
2009-02-11 16:48 ` Jamie Lokier
2009-02-12 22:57 ` Consul
2009-02-12 22:57 ` [Qemu-devel] " Consul
2009-02-12 23:19 ` Consul
2009-02-12 23:19 ` [Qemu-devel] " Consul
2009-02-13 7:50 ` Marc Bevand
2009-02-16 12:44 ` [Qemu-devel] " Kevin Wolf
2009-02-17 0:43 ` Jamie Lokier
2009-02-17 0:43 ` Jamie Lokier
2009-03-06 22:37 ` Filip Navara
2009-03-06 22:37 ` Filip Navara
2009-02-12 5:45 ` Chris Wright
2009-02-12 5:45 ` Chris Wright
2009-02-12 11:08 ` Johannes Schindelin
2009-02-12 11:08 ` Johannes Schindelin
2009-02-13 6:41 ` Marc Bevand
2009-02-13 11:16 ` Kevin Wolf
2009-02-13 11:16 ` [Qemu-devel] " Kevin Wolf
2009-02-13 16:23 ` Jamie Lokier
2009-02-13 16:23 ` Jamie Lokier
2009-02-13 18:43 ` Chris Wright
2009-02-13 18:43 ` Chris Wright
2009-02-14 6:31 ` Marc Bevand
2009-02-14 22:28 ` Dor Laor
2009-02-14 22:28 ` Dor Laor
2009-02-15 2:27 ` Jamie Lokier
2009-02-15 7:56 ` Marc Bevand
2009-02-15 7:56 ` Marc Bevand
2009-02-15 2:37 ` Jamie Lokier
2009-02-15 10:57 ` Gleb Natapov
2009-02-15 10:57 ` [Qemu-devel] " Gleb Natapov
2009-02-15 11:46 ` Marc Bevand
2009-02-15 11:46 ` [Qemu-devel] " Marc Bevand
2009-02-15 11:54 ` Marc Bevand
2009-02-15 11:54 ` [Qemu-devel] " Marc Bevand
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=4992A108.8070304@suse.de \
--to=kwolf@suse.de \
--cc=jamie@shareable.org \
--cc=kvm@vger.kernel.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.