Re: Why doesn't Intel e1000 NIC work correctly in Windows XP?

[Jan Kiszka <jan.kiszka@siemens.com>]

On 2011-06-20 16:32, Alex Williamson wrote:
> On Sun, 2011-06-19 at 20:29 +0800, Flypen CloudMe wrote:
>> Hi,
>>
>> Here are the command line:
>>
>> /usr/bin/qemu-kvm -S -M rhel6.0.0 -enable-kvm -m 2048 -smp
>> 2,sockets=1,cores=2,threads=1 \
>> -name winxp -uuid 23cd2751-8a30-dd34-db47-bfc8c76ccadb -nodefconfig
>> -nodefaults \
>> -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/winxp.monitor,server,nowait
>> -mon chardev=monitor,mode=readline \
>> -rtc base=localtime -boot c -device lsi,id=scsi0,bus=pci.0,addr=0x5
>> -device lsi,id=scsi1,bus=pci.0,addr=0x6 \
>> -device lsi,id=scsi2,bus=pci.0,addr=0x7 -device
>> lsi,id=scsi3,bus=pci.0,addr=0x8 \
>> -drive file=/mnt/vmdisk/winxp.disk,if=none,id=drive-ide0-0-0,boot=on,format=raw,cache=none
>> \
>> -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 \
>> -drive file=/mnt/vmdisk/virtio-win-1.1.16.vfd,if=none,id=drive-fdc0-0-0,format=raw,cache=none\
>> -global isa-fdc.driveA=drive-fdc0-0-0 -drive
>> file=/dev/sd1,if=none,id=drive-scsi0-0-0,format=raw,cache=none \
>> -device scsi-disk,bus=scsi0.0,scsi-id=0,drive=drive-scsi0-0-0,id=scsi0-0-0 \
>> -drive file=/dev/sdb,if=none,id=drive-scsi0-0-1,format=raw,cache=none \
>> -device scsi-disk,bus=scsi0.0,scsi-id=1,drive=drive-scsi0-0-1,id=scsi0-0-1 \
>> -drive file=/dev/sdc,if=none,id=drive-scsi0-0-2,format=raw,cache=none \
>> -device scsi-disk,bus=scsi0.0,scsi-id=2,drive=drive-scsi0-0-2,id=scsi0-0-2 \
>> -drive file=/dev/sdd,if=none,id=drive-scsi0-0-3,format=raw,cache=none \
>> -device scsi-disk,bus=scsi0.0,scsi-id=3,drive=drive-scsi0-0-3,id=scsi0-0-3 \
>> -drive file=/dev/sde,if=none,id=drive-scsi0-0-4,format=raw,cache=none \
>> -device scsi-disk,bus=scsi0.0,scsi-id=4,drive=drive-scsi0-0-4,id=scsi0-0-4 \
>> -drive file=/dev/sdf,if=none,id=drive-scsi3-0-0,format=raw,cache=none \
>> -device scsi-disk,bus=scsi3.0,scsi-id=0,drive=drive-scsi3-0-0,id=scsi3-0-0 \
>> -drive file=/mnt/vmdisk/D/1,if=none,id=drive-scsi0-0-6,format=raw,cache=none \
>> -device scsi-disk,bus=scsi0.0,scsi-id=6,drive=drive-scsi0-0-6,id=scsi0-0-6 \
>> -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb \
>> -vnc 0.0.0.0:0 -k en-us -vga vmware -device
>> pci-assign,host=02:00.0,id=hostdev0,configfd=18,bus=pci.0,addr=0x3 \
>> -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4
> 
> That's a lot of SCSI controllers.  Why are you creating 4 separate lsi
> SCSI controller devices, but only using 2 of them?  Can you reduce the
> problem by just using 1?  If so, then you might be able to move the
> assigned device and lsi device addr around so the guest will use
> different INTx interrupts for these (or at least move them until the
> assigned device gets an interrupt in the guest exclusively).  Is the
> guest Windows XP 32bit or 64bit?  A 64bit Windows is probably more
> likely to enable MSI interrupts (which hopefully your assigned device
> supports), which would also eliminate INTx sharing problems.
> 

I tend to believe there is some problem with the IRQ routing information
provided to the BIOS or what the BIOS makes out of it. See how "info
pci" looks like on a "qemu-syste-x86_64 -device e1000 -device e1000" VM
after the BIOS is done:

[...]
  Bus  0, device   3, function 0:
    Ethernet controller: PCI device 8086:100e
      IRQ 11.
      BAR0: 32 bit memory at 0xf2020000 [0xf203ffff].
      BAR1: I/O at 0xc040 [0xc07f].
      BAR6: 32 bit memory at 0xffffffffffffffff [0x0001fffe].
      id ""
  Bus  0, device   4, function 0:
    Ethernet controller: PCI device 8086:100e
      IRQ 11.
      BAR0: 32 bit memory at 0xf2060000 [0xf207ffff].
      BAR1: I/O at 0xc080 [0xc0bf].
      BAR6: 32 bit memory at 0xffffffffffffffff [0x0001fffe].
      id ""
  Bus  0, device   5, function 0:
    Ethernet controller: PCI device 8086:100e
      IRQ 10.
      BAR0: 32 bit memory at 0xf20a0000 [0xf20bffff].
      BAR1: I/O at 0xc0c0 [0xc0ff].
      BAR6: 32 bit memory at 0xffffffffffffffff [0x0001fffe].
      id ""

Slot 3 & 4 on IRQ 11, but slot 5 on 10? That confuses Windows XP here -
at least until you reboot it after the device installation.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux