From: Jim Paris <jim-XrPbb/hENzg@public.gmane.org>
To: Joris <joris-3CvOTOCK0fQ@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: possible bug: VM drops incoming network packets (tap)
Date: Mon, 22 Oct 2007 02:02:06 -0400 [thread overview]
Message-ID: <20071022060206.GA13651@jim.sh> (raw)
In-Reply-To: <6b9952490710210140j13c7ada7n7fa4e8286977a44d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Joris wrote:
> Both changing the nic (to rtl8139) and rebooting the host solved the
> issue for me.
> My VM's have now survived over 12 hours of intense activity without a glitch.
>
> To be clear: soly changing the nic without rebooting the host worked;
> after rebooting the host the default nic works again.
I rebooted the host (and upgraded to 2.6.23.1), but the default
ne2k-pci nic still had the same problems. I switched my guests all to
rtl8139 and they seem to be working much better.
Seems that ne2k-pci has had some bugs introduced between kvm-36 and kvm-46.
-jim
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
prev parent reply other threads:[~2007-10-22 6:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-20 6:14 possible bug: VM drops incoming network packets (tap) Joris
[not found] ` <6b9952490710192314q10541f44l8b0c9f61d80859c8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-10-20 6:59 ` Jim Paris
[not found] ` <20071020065908.GA17990-lSbMZ+N7itA@public.gmane.org>
2007-10-20 7:15 ` Joris
[not found] ` <6b9952490710200015u3f199c78v6910c10d55f0db7c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-10-21 8:40 ` Joris
[not found] ` <6b9952490710210140j13c7ada7n7fa4e8286977a44d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-10-22 6:02 ` Jim Paris [this message]
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=20071022060206.GA13651@jim.sh \
--to=jim-xrpbb/henzg@public.gmane.org \
--cc=joris-3CvOTOCK0fQ@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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