From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:55502) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QBCFQ-00034Q-AR for qemu-devel@nongnu.org; Sat, 16 Apr 2011 16:37:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QBCFP-0006j1-AL for qemu-devel@nongnu.org; Sat, 16 Apr 2011 16:37:40 -0400 Received: from isrv.corpit.ru ([86.62.121.231]:54698) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QBCFP-0006ir-2Y for qemu-devel@nongnu.org; Sat, 16 Apr 2011 16:37:39 -0400 Message-ID: <4DA9FE0F.40608@msgid.tls.msk.ru> Date: Sun, 17 Apr 2011 00:37:35 +0400 From: Michael Tokarev MIME-Version: 1.0 References: <4DA6B0E8.2050608@msgid.tls.msk.ru> <1302877041.3110.26.camel@x201> In-Reply-To: <1302877041.3110.26.camel@x201> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] is it just me or is ne2k broken in qemu? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alex Williamson Cc: qemu-devel 15.04.2011 18:17, Alex Williamson wrote: > On Thu, 2011-04-14 at 12:31 +0400, Michael Tokarev wrote: >> The NIC works for a while, but after a few packets, >> or a few 1000s of packets, it stalls. In tcpdump >> on the host I see many ARP requests coming from the >> guest and each has corresponding ARP reply, but >> nothing is actually reaching the guest. > For testing the iPXE ROMs I booted up each NIC, including ne2k_pci, to a > network loaded kernel (~4M) and installation initrd (~8M). I stopped > the test at the point where the installer kernel was able to > successfully DHCP with the boot NIC. ne2k_pci was definitely the > slowest of the cards at loading the images, but I didn't notice any > functionality issues. Maybe I didn't let it run long enough, but the > boot ROM seems ok with it. I'm doing exactly the same here, -- testing iPXE booting, so booting linux kernel over network. I haven't been able to boot linux on ne2k so far, it fails somewhere down the road after loading initrd+kernel - either during initrd run or about after switching to new init (still running off network ofcourse) after mounting nfs root. So when I encountered this issue I tried non-network boot and various versions of (linux) guest and qemu-kvm - and for me, ne2k always fail (stalls) after some time. And Mulyadi Santosa mentioned it's apparently a known issue due to some timer-related problem in the code. /mjt