From mboxrd@z Thu Jan 1 00:00:00 1970 From: "David S. Ahern" Subject: Re: [Qemu-devel] 8139cp problems - steps to reproduce Date: Mon, 15 Sep 2008 09:45:56 -0600 Message-ID: <48CE8334.3060802@cisco.com> References: <20080908075759.GA27882@develbox.linuxbox.cz> <20080910065526.GA6863@develbox.linuxbox.cz> <20080910093527.GB6863@develbox.linuxbox.cz> <519a8b110809121437h752927e8t4711526b1d828a11@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Nikola Ciprich , KVM list To: xming Return-path: Received: from sj-iport-3.cisco.com ([171.71.176.72]:34897 "EHLO sj-iport-3.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753270AbYIOPqF (ORCPT ); Mon, 15 Sep 2008 11:46:05 -0400 In-Reply-To: <519a8b110809121437h752927e8t4711526b1d828a11@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: 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 >