From: Hollis Blanchard <hollisb@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [kvm-ppc-devel] virtio network traffic issues
Date: Tue, 25 Mar 2008 13:52:07 +0000 [thread overview]
Message-ID: <1206453127.1022.1.camel@basalt> (raw)
In-Reply-To: <47E9020B.3080705@linux.vnet.ibm.com>
On Tue, 2008-03-25 at 14:45 +0100, Christian Ehrhardt wrote:
>
> => from one not yet defined point our guest seems to receive
> absolutely nothing
> => when the guest is hanging it sends nfs requests which are seen
> externally, but it does not seem to get the respones
> => the arp requests for the guest are repeated - maybe we can add some
> very verbose debug in the guest virtio code and activate it when we
> see that it is already hanging
> => ideas:
> - maybe some buffer/memory runs out and so incoming packets won't be
> received anymore
> - we break something in virtio / incoming interrupts (or maybe a
> lock) and from that point no receive is possible
>
Could we be missing interrupts? Can you add a guest kernel timer that
calls virtio_poll() regularly?
>
--
Hollis Blanchard
IBM Linux Technology Center
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel
next prev parent reply other threads:[~2008-03-25 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 13:45 [kvm-ppc-devel] virtio network traffic issues Christian Ehrhardt
2008-03-25 13:52 ` Hollis Blanchard [this message]
2008-03-26 16:07 ` Christian Ehrhardt
2008-03-26 16:07 ` Christian Ehrhardt
2008-03-26 17:03 ` Dor Laor
2008-03-26 17:03 ` Dor Laor
2008-03-26 16:06 ` Christian Ehrhardt
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=1206453127.1022.1.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=kvm-ppc@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.