From: Avi Kivity <avi@qumranet.com>
To: david ahern <daahern@cisco.com>
Cc: kvm-devel@lists.sourceforge.net,
Eckersid SIlapaswang <esila@guardiandigital.com>
Subject: Re: still seeing network freezes with rtl8139 nic
Date: Wed, 05 Mar 2008 19:14:35 +0200 [thread overview]
Message-ID: <47CED4FB.8050508@qumranet.com> (raw)
In-Reply-To: <47CEB685.10308@cisco.com>
david ahern wrote:
> Try adding the noapic option to your guest kernel. I re-ran that test on kvm-62
> and my VM was able to run under load for more than 3-1/2 days (the network never
> locked up; I stopped the test to try other variations).
>
> One side effect of the noapic option is that irq balancing is disabled -- all
> interrupts are delivered via CPU 0. I ran a few tests earlier this week without
> the noapic option (hence with the apic) but with irq balancing disabled and
> still had the lockups. It seems to be something specific to the apic.
>
>
I got good results with apic and e1000. Can you try it?
May be a guest driver bug.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
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/
next prev parent reply other threads:[~2008-03-05 17:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 18:33 still seeing network freezes with rtl8139 nic david ahern
2008-02-24 10:14 ` Avi Kivity
2008-02-24 19:49 ` david ahern
2008-02-25 8:54 ` Avi Kivity
2008-02-25 16:11 ` david ahern
2008-02-25 17:06 ` david ahern
2008-02-25 17:19 ` Avi Kivity
2008-02-26 4:57 ` david ahern
2008-02-26 9:19 ` Avi Kivity
2008-02-26 14:41 ` Avi Kivity
2008-02-26 14:55 ` david ahern
2008-02-26 14:50 ` david ahern
2008-02-26 15:07 ` Avi Kivity
2008-03-04 18:05 ` Eckersid SIlapaswang
2008-03-05 15:04 ` david ahern
2008-03-05 17:14 ` Avi Kivity [this message]
2008-03-05 18:33 ` david ahern
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=47CED4FB.8050508@qumranet.com \
--to=avi@qumranet.com \
--cc=daahern@cisco.com \
--cc=esila@guardiandigital.com \
--cc=kvm-devel@lists.sourceforge.net \
/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