From: david ahern <daahern@cisco.com>
To: Eckersid SIlapaswang <esila@guardiandigital.com>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: still seeing network freezes with rtl8139 nic
Date: Wed, 05 Mar 2008 08:04:37 -0700 [thread overview]
Message-ID: <47CEB685.10308@cisco.com> (raw)
In-Reply-To: <loom.20080304T180204-782@post.gmane.org>
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.
david
Eckersid SIlapaswang wrote:
> david ahern <daahern <at> cisco.com> writes:
>
>> I know this issue has been discussed on this list before, but I am still
>> experiencing network freezes in a guest that requires a restart to clear. When
>> the network freezes in the guest I no longer see the network interrupts counter
>> incrementing (i.e., the eth0 counter in /proc/interrupts in the guest). Using
>> the crash utility, I verified that the interrupt is still enabled on the guest
>> side and that no interrupts are pending. This suggests that the interrupts are
>> not getting delivered to the VM.
>
> I just wanted to let the developers know that I'm having similar problems
> concerning interrupts with networking dying as well.
>
> Running a stress test of kvm using an EnGarde Secure Linux 1.5 guest OS.
> Under a heavy network email load, the guest OS networking gets knocked out
> - unable to ping, ssh, etc. Can only get things started again by going
> into vncviewer and restarting the networking services from there.
>
> CPUs: 8 x Intel(R) Xeon(R) CPU E5335 @ 2.00GHz
> KVM 52-1
> Host Kernel: 2.6.25-rc2
> Kernel Arch: x86_64
> Guest OS: EnGarde Secure Linux 32bit i686, 2.4.31-1.5.60
>
> Command Line:
> /usr/bin/qemu-system -hda /root/images/bwimail01.img -boot c -m 384 -smp 4
> -std-vga -net nic,vlan=0,macaddr=52:54:00:12:34:6F -net
> tap,ifname=tap1,script=/etc/qemu-ifup -vnc 192.168.1.57:1 &
>
> Please let me know if you need anymore information and if I could be of any
> assistance in providing information to have this issue resolved.
>
>
>
> -------------------------------------------------------------------------
> 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-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
-------------------------------------------------------------------------
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 15:04 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 [this message]
2008-03-05 17:14 ` Avi Kivity
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=47CEB685.10308@cisco.com \
--to=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