From: Stefan Hajnoczi <stefanha@gmail.com>
To: folkert <folkert@vanheusden.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: FAQ on linux-kvm.org has broken link
Date: Tue, 6 Aug 2013 10:13:58 +0200 [thread overview]
Message-ID: <20130806081358.GH27705@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20130805205944.GP8801@belle.intranet.vanheusden.com>
On Mon, Aug 05, 2013 at 10:59:45PM +0200, folkert wrote:
> > Two approaches to get closer to the source of the problem:
> > 1. Try the latest vanilla kernel on the host (Linux 3.10.5). This way
> > you can rule out fixed bugs in vhost_net or tap.
> > 2. Get the system into the bad state and then do some deeper. Start
> > with outgoing ping, instrument guest driver and host vhost_net
> > functions to see what the drivers are doing, inspect the transmit
> > vring, etc.
> >
> > #1 is probably the best next step. If it fails and you still have time
> > to work on a solution we can start digging deeper with #2.
>
> I can upgrade now to 3.10.3 as that is the current version in debian.
Sounds good. That way you'll also have access to the latest perf for
instrumenting vhost_net if it still fails.
Stefan
next prev parent reply other threads:[~2013-08-06 8:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 1:18 FAQ on linux-kvm.org has broken link folkert
2013-07-30 12:25 ` Stefan Hajnoczi
2013-07-30 12:45 ` folkert
2013-07-30 20:45 ` folkert
2013-07-31 8:46 ` Stefan Hajnoczi
2013-08-02 11:37 ` folkert
2013-08-02 15:25 ` Stefan Hajnoczi
2013-08-02 18:06 ` folkert
2013-08-05 11:31 ` Stefan Hajnoczi
2013-08-05 20:59 ` folkert
2013-08-06 8:13 ` Stefan Hajnoczi [this message]
2013-09-03 17:03 ` folkert
2013-08-26 19:50 ` folkert
2013-08-27 7:31 ` Stefan Hajnoczi
2013-10-29 17:18 ` folkert
2013-11-01 9:52 ` 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=20130806081358.GH27705@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=folkert@vanheusden.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