From: "Michael S. Tsirkin" <mst@redhat.com>
To: Soren Hansen <soren@ubuntu.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Symptoms of lost interrupts in virtio?
Date: Mon, 3 Sep 2012 16:37:06 +0300 [thread overview]
Message-ID: <20120903133706.GE3855@redhat.com> (raw)
In-Reply-To: <CAPFUtkZnW_TVevmLd6G9=SmBFX0N-=9ipOkzsZA4hRjHT14GxQ@mail.gmail.com>
On Mon, Sep 03, 2012 at 03:16:00PM +0200, Soren Hansen wrote:
> Michael,
>
> In Ubuntu we're seeing a bug in qemu-kvm 1.0 where networking stops
> working. It's described here:
>
> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/997978
>
> We've not been able to reproduce it ourselves, but the users who are
> experiencing it say that it's fixed in 1.1.
>
> I've found this series of commits:
>
> a821ce5 virtio: order index/descriptor reads
> 92045d8 virtio: add missing mb() on enable notification
> a281ebc virtio: add missing mb() on notification
>
> where particularly the last one looks like a likely fix for the problem.
>
> The commit message isn't entirely clear about the symptoms it's meant
> to fix, even though the behind-the-covers explanation is very
> thorough. It's not clear to me, for instance, if the network would
> stop working or if you'd just lose a couple of network packets?
It can stop working. It's more likely to stop if
event_idx is enabled. Try disabling and see what happens.
> The commit message suggests it only happens on a very specific
> processor type. Do you happen to remember which one? If it matches
> what our affected users see, that could be clue as to whether this is
> the same problem.
I think it was reported on AMD systems.
> Thanks in advance for your time.
>
> --
> Soren Hansen
> Ubuntu Developer http://www.ubuntu.com/
> OpenStack Developer http://www.openstack.org/
prev parent reply other threads:[~2012-09-03 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 13:16 [Qemu-devel] Symptoms of lost interrupts in virtio? Soren Hansen
2012-09-03 13:37 ` Michael S. Tsirkin [this message]
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=20120903133706.GE3855@redhat.com \
--to=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=soren@ubuntu.com \
/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).