From: Mark McLoughlin <markmc@redhat.com>
To: Javier Guerra <javier@guerrag.com>
Cc: avi <avi@qumranet.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [ kvm-Bugs-2009439 ] data corruption with virtio-blk
Date: Sat, 05 Jul 2008 11:29:08 +0100 [thread overview]
Message-ID: <1215253748.4394.3.camel@muff> (raw)
In-Reply-To: <90eb1dc70807030758n33f54a00m68ea831d30b30a5b@mail.gmail.com>
On Thu, 2008-07-03 at 09:58 -0500, Javier Guerra wrote:
> On Thu, Jul 3, 2008 at 3:03 AM, Mark McLoughlin <markmc@redhat.com> wrote:
> > I think the below fixes the data corrupter, but I'm still tracking down
> > another issue where the guest is hanging waiting for I/O to complete
> > with the latest virtio-blk backend.
>
> is that a common case? i haven't been able to finish a system install
> on either virtio or scsi block devices. both linux (Ubuntu JeOS 8.04)
> and windows (xp sp2) freeze sometime while writing packages. IDE
> installs work perfectly
It's certainly possible the hangs you're seeing were caused by the
IOAPIC interrupt injection bug I just sent out a fix for - you could try
doing an install either running kvm-qemu -no-kvm-irqchip or booting the
guest with "noapic" on the kernel command line. If the IOAPIC bug is
your issue, you shouldn't see any freezes.
Cheers,
Mark.
next prev parent reply other threads:[~2008-07-05 10:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 5:51 [ kvm-Bugs-2009439 ] data corruption with virtio-blk SourceForge.net
2008-07-03 8:03 ` Mark McLoughlin
2008-07-03 14:06 ` Avi Kivity
2008-07-03 14:58 ` Javier Guerra
2008-07-05 10:29 ` Mark McLoughlin [this message]
2008-07-07 16:10 ` Javier Guerra
-- strict thread matches above, loose matches on Subject: below --
2008-07-07 8:32 SourceForge.net
2008-07-10 14:32 SourceForge.net
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=1215253748.4394.3.camel@muff \
--to=markmc@redhat.com \
--cc=avi@qumranet.com \
--cc=javier@guerrag.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.