[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [Bug 1326986] [NEW] e1000 - no link detected by
From: |
Gabriel L. Somlo |
Subject: |
Re: [Qemu-devel] [Bug 1326986] [NEW] e1000 - no link detected by |
Date: |
Thu, 5 Jun 2014 22:44:39 -0400 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
Matthew Gamble <address@hidden> 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
- [Qemu-devel] [PATCH v3 0/9] virtio-blk: Converge VirtIOBlockRequest into VirtIOBlockReq, Fam Zheng, 2014/06/05
- [Qemu-devel] [PATCH v3 1/9] virtio-blk: Move VirtIOBlockReq to header, Fam Zheng, 2014/06/05
- [Qemu-devel] [PATCH v3 2/9] virtio-blk: Convert VirtIOBlockReq.elem to pointer, Fam Zheng, 2014/06/05
- [Qemu-devel] [PATCH v3 3/9] virtio-blk: Drop bounce buffer from dataplane code, Fam Zheng, 2014/06/05
- [Qemu-devel] [PATCH v3 4/9] virtio-blk: Drop VirtIOBlockRequest.read, Fam Zheng, 2014/06/05
- [Qemu-devel] [PATCH v3 5/9] virtio-blk: Replace VirtIOBlockRequest with VirtIOBlockReq, Fam Zheng, 2014/06/05
- [Qemu-devel] [PATCH v3 6/9] virtio-blk: Use VirtIOBlockReq.in to drop VirtIOBlockReq.inhdr, Fam Zheng, 2014/06/05
- [Qemu-devel] [PATCH v3 7/9] virtio-blk: Convert VirtIOBlockReq.out to structrue, Fam Zheng, 2014/06/05
- [Qemu-devel] [PATCH v3 8/9] virtio-blk: Fill in VirtIOBlockReq.out in dataplane code, Fam Zheng, 2014/06/05
- [Qemu-devel] [PATCH v3 9/9] virtio-blk: Fix and clean up the in_sg and out_sg check, Fam Zheng, 2014/06/05