From: Avi Kivity <avi@redhat.com>
To: Guido Winkelmann <guido-kvml@thisisnotatest.de>
Cc: Brian Jackson <iggy@theiggy.com>, kvm@vger.kernel.org
Subject: Re: I/O errors in guest OS after repeated migration
Date: Thu, 18 Oct 2012 18:05:39 +0200 [thread overview]
Message-ID: <508028D3.1070002@redhat.com> (raw)
In-Reply-To: <3011167.xvxMQSrSK0@pc10>
On 10/18/2012 05:50 PM, Guido Winkelmann wrote:
> Am Mittwoch, 17. Oktober 2012, 13:25:45 schrieb Brian Jackson:
>> On Wednesday, October 17, 2012 10:45:14 AM Guido Winkelmann wrote:
>> > vda1, logical block 1858771
>> > Oct 17 17:12:04 localhost kernel: [ 212.070600] Buffer I/O error on
>> > device
>> > vda1, logical block 1858772
>> > Oct 17 17:12:04 localhost kernel: [ 212.070602] Buffer I/O error on
>> > device
>> > vda1, logical block 1858773
>> > Oct 17 17:12:04 localhost kernel: [ 212.070605] Buffer I/O error on
>> > device
>> > vda1, logical block 1858774
>> > Oct 17 17:12:04 localhost kernel: [ 212.070607] Buffer I/O error on
>> > device
>> > vda1, logical block 1858775
>> > Oct 17 17:12:04 localhost kernel: [ 212.070610] Buffer I/O error on
>> > device
>> > vda1, logical block 1858776
>> > Oct 17 17:12:04 localhost kernel: [ 212.070612] Buffer I/O error on
>> > device
>> > vda1, logical block 1858777
>> > Oct 17 17:12:04 localhost kernel: [ 212.070615] Buffer I/O error on
>> > device
>> > vda1, logical block 1858778
>> > Oct 17 17:12:04 localhost kernel: [ 212.070617] Buffer I/O error on
>> > device
>> > vda1, logical block 1858779
>> >
>> > (I was writing a large file at the time, to make sure I actually catch I/O
>> > errors as they happen)
>>
>> What about newer versions of qemu/kvm? But of course if those work, your
>> next task is going to be git bisect it or file a bug with your distro that
>> is using an ancient version of qemu/kvm.
>
> I've just upgraded both hosts to qemu-kvm 1.2.0 (qemu-1.2.0-14.fc17.x86_64,
> built from spec files under http://pkgs.fedoraproject.org/cgit/qemu.git/).
>
> The bug is still there.
>
If you let the guest go idle (no I/O), then migrate it, then restart the
I/O, do the errors show?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-10-18 16:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 16:33 I/O errors in guest OS after repeated migration Guido Winkelmann
2012-10-16 17:44 ` Brian Jackson
2012-10-17 11:54 ` Guido Winkelmann
2012-10-17 18:24 ` Brian Jackson
2012-10-17 15:45 ` Guido Winkelmann
2012-10-17 18:25 ` Brian Jackson
2012-10-18 15:50 ` Guido Winkelmann
2012-10-18 16:05 ` Avi Kivity [this message]
2012-10-19 12:55 ` Guido Winkelmann
2012-10-29 11:29 ` Stefan Hajnoczi
2012-11-06 11:07 ` Guido Winkelmann
2012-11-08 8:23 ` 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=508028D3.1070002@redhat.com \
--to=avi@redhat.com \
--cc=guido-kvml@thisisnotatest.de \
--cc=iggy@theiggy.com \
--cc=kvm@vger.kernel.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.