From: "David S. Ahern" <daahern@cisco.com>
To: xming <xmingske@gmail.com>
Cc: Nikola Ciprich <extmaillist@linuxbox.cz>, KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] 8139cp problems - steps to reproduce
Date: Mon, 15 Sep 2008 09:45:56 -0600 [thread overview]
Message-ID: <48CE8334.3060802@cisco.com> (raw)
In-Reply-To: <519a8b110809121437h752927e8t4711526b1d828a11@mail.gmail.com>
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
>
next prev parent reply other threads:[~2008-09-15 15:46 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 [this message]
2008-09-16 0:11 ` xming
2008-09-16 6:34 ` Nikola Ciprich
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=48CE8334.3060802@cisco.com \
--to=daahern@cisco.com \
--cc=extmaillist@linuxbox.cz \
--cc=kvm@vger.kernel.org \
--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