From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36989) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wsk9A-0005fg-Tf for qemu-devel@nongnu.org; Thu, 05 Jun 2014 22:44:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wsk94-0005aQ-Ph for qemu-devel@nongnu.org; Thu, 05 Jun 2014 22:44:48 -0400 Received: from mail-qg0-x232.google.com ([2607:f8b0:400d:c04::232]:42520) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wsk94-0005aM-L9 for qemu-devel@nongnu.org; Thu, 05 Jun 2014 22:44:42 -0400 Received: by mail-qg0-f50.google.com with SMTP id z60so3165571qgd.23 for ; Thu, 05 Jun 2014 19:44:42 -0700 (PDT) Date: Thu, 5 Jun 2014 22:44:39 -0400 From: "Gabriel L. Somlo" Message-ID: <20140606024438.GB5772@crash.ini.cmu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140605222643.4583.85001.malonedeb@soybean.canonical.com> Subject: Re: [Qemu-devel] [Bug 1326986] [NEW] e1000 - no link detected by List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: mgamble@mgamble.ca Matthew Gamble wrote: > I'm trying to get a VXWorks image running inside a qemu guest. I have > the machine running, however, the vxworks image only has support for the > 82544EI device so I had to change the device ID in e1000.c to get the > device even recognized so I'm not sure if this is a bug or an issue for > the development list. > > After changing e1000.c, the device is now seen by the guest OS, however, it never gets a link. I've attached the e1000 debug logs in the hopes that someone can help me understand where to start looking into why this guest won't get a link. > > I tested the updated e1000 driver with a debian live CD and the card > works under it, so it doesn't appear that the issue is with the driver > string change but rather something in the e1000 driver itself. > > Here is the command I'm using to start QEMU: > > /opt/qemu/bin/qemu-system-i386 -cpu coreduo -hda /root/vxworks_test -m > 2048 -netdev tap,ifname=tap0,id=net0 -netdev tap,ifname=tap1,id=net1 > -device e1000,netdev=net0,mac=00:00:e8:01:02:03 -device > e1000,netdev=net1,mac=00:00:e8:01:02:04 -boot c -curses -no-kvm -D > /tmp/qemu.log 2>/tmp/e1000.log Can you try this: Add "-monitor stdio" to your qemu command line, and give an id to at least one of your e1000 devices, like so: "-device e1000,netdev=net0,mac=00:00:e8:01:02:03,id=eth0" Then after the guest is finished booting (with no link on the e1000 interfaces), from the qemu monitor prompt issue these two commands: set_link eth0 off set_link eth0 on I'd be curious to find out if this causes the guest to see a link become available... Thanks, --Gabriel