From: Emmanuel Lacour <elacour@easter-eggs.com>
To: kvm@vger.kernel.org
Subject: Re: virtio_net hang
Date: Thu, 20 Nov 2008 12:36:50 +0100 [thread overview]
Message-ID: <20081120113650.GE3717@easter-eggs.com> (raw)
In-Reply-To: <1227121389.3698.136.camel@blaa>
On Wed, Nov 19, 2008 at 07:03:09PM +0000, Mark McLoughlin wrote:
>
> I had a look at Emmanuel's strace log and it shows that qemu isn't
> selecting on the tapfd, presumably because virtio_net_can_receive() sees
> that we've exhausted all available receive buffers.
>
> When qemu does poll the tapfd (after an ifdown/ifup in the guest), there
> are a load of packets waiting in the queue and things proceed as normal.
>
> That still jives with the theory that we're somehow getting into a state
> where NAPI polling is de-scheduled while guest rx interrupts are also
> disabled.
>
> > Is it possible for you to try a newer guest kernel?
>
> If you can try a newer kernel, or even try some debugging patches, that
> would help a lot.
>
The difficulty is that I can not always reproduce the bug.
But another interesting think is that I switched to e1000 and I had
another lock after that with same symptoms :(
Like answered a few minutes ago, I will try a 2.6.27.6 in the guest
today and let you know on the first problem I encounter if any ;)
next prev parent reply other threads:[~2008-11-20 11:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 12:27 virtio_net hang Emmanuel Lacour
2008-11-13 13:04 ` Daniel P. Berrange
2008-11-13 13:15 ` Emmanuel Lacour
2008-11-13 15:12 ` Mark McLoughlin
2008-11-13 15:24 ` Emmanuel Lacour
2008-11-14 9:23 ` Emmanuel Lacour
2008-11-14 18:26 ` Mark McLoughlin
2008-11-18 18:37 ` Emmanuel Lacour
2008-11-18 18:48 ` Emmanuel Lacour
2008-11-19 13:13 ` Mark McLoughlin
2008-11-19 19:03 ` Mark McLoughlin
2008-11-20 11:36 ` Emmanuel Lacour [this message]
2008-11-21 8:38 ` Emmanuel Lacour
2008-11-22 14:20 ` Emmanuel Lacour
2008-11-21 14:44 ` Guido Günther
2008-11-20 11:34 ` Emmanuel Lacour
2008-11-13 18:27 ` Fabio Coatti
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=20081120113650.GE3717@easter-eggs.com \
--to=elacour@easter-eggs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox