From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: "David S. Ahern" <daahern@cisco.com>
Cc: xming <xmingske@gmail.com>, KVM list <kvm@vger.kernel.org>,
nikola.ciprich@linuxbox.cz
Subject: Re: [Qemu-devel] 8139cp problems - steps to reproduce
Date: Tue, 16 Sep 2008 08:34:40 +0200 [thread overview]
Message-ID: <20080916063440.GB7942@localhost.localdomain> (raw)
In-Reply-To: <48CE8334.3060802@cisco.com>
Hi David, well, I tried e1000, but it's actualy much worse for me.
But I'm using much newer (vanilla) kernels, maybe RHEL kernels
contain some patch that prevents the problem? I'll have a look.
BR
nik
On Mon, Sep 15, 2008 at 09:45:56AM -0600, David S. Ahern wrote:
> Last February I dug into where it was getting stuck. See:
>
> http://article.gmane.org/gmane.comp.emulators.kvm.devel/13537/match=pci%5fset%5firq
>
> and follow up posts.
>
> For the past 5-6 months I've been using the e1000 nic in rhel3 and rhel4
> guests without a problem -- and without the need for guest hacks like
> noapic.
>
> david
>
>
>
> xming wrote:
> > hi,
> >
> > I am running kvm-74 and it's getting worse for me (compared to 73, or
> > 70,71 w/o issues), I tried virtio, rtl8139 and e1000,
> > the network will stall. With 8139 it happens very quick (few MB via
> > nfs) and I noticed that I can bring up the network
> > by setting the stalled NIC (in the guest) by setting it to promisc and
> > -promisc repeatably.
> >
> > I can now perfectly reproduced the stall and un-stall.
> >
> > When it's stalled I noticed on the host that the nic is not totally
> > gone, arp broadcast still gets out.
> >
> > Any ideas?
> > --
> > To unsubscribe from this list: send the line "unsubscribe kvm" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
--
-------------------------------------
Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava
tel.: +420 596 603 142
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------
next prev parent reply other threads:[~2008-09-16 6:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 7:57 8139cp problems - steps to reproduce Nikola Ciprich
2008-09-08 9:59 ` Nikola Ciprich
2008-09-08 19:54 ` [Qemu-devel] " Igor Kovalenko
2008-09-10 6:55 ` Nikola Ciprich
2008-09-10 9:35 ` Nikola Ciprich
2008-09-12 21:37 ` xming
2008-09-15 15:45 ` David S. Ahern
2008-09-16 0:11 ` xming
2008-09-16 6:34 ` Nikola Ciprich [this message]
2008-09-16 9:21 ` xming
2008-09-16 6:32 ` Nikola Ciprich
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=20080916063440.GB7942@localhost.localdomain \
--to=extmaillist@linuxbox.cz \
--cc=daahern@cisco.com \
--cc=kvm@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
--cc=xmingske@gmail.com \
/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