Re: [Qemu-devel] Q35 FreeBSD install status

[Bret Ketchum]

     Qemu says the IRQ is 11:

  Bus  0, device   3, function 0:
    Ethernet controller: PCI device 8086:100e
      IRQ 11.
      BAR0: 32 bit memory at 0xfebc0000 [0xfebdffff].
      BAR1: I/O at 0xc040 [0xc07f].
      BAR6: 32 bit memory at 0xffffffffffffffff [0x0003fffe].
      id ""

    FreeBSD thinks the IRQ is 23:
address@hidden:0:3:0: class=0x020000 card=0x11001af4 chip=0x100e8086 rev=0x03 
hdr=0x00
pciconf -r -b pci0:0:4:0 0x3c:0x3d
17 01


-----Original Message-----
From: Bret Ketchum 
Sent: Monday, September 16, 2013 8:03 AM
To: 'Michael S. Tsirkin'
Cc: address@hidden; address@hidden
Subject: RE: Q35 FreeBSD install status


    Syslog suggests the interface is brought down then up but no interrupt at 
the irq assigned. Need to enable more debug and make sure the interrupt is 
wired properly.

-----Original Message-----
From: Michael S. Tsirkin [mailto:address@hidden 
Sent: Monday, September 16, 2013 7:36 AM
To: Bret Ketchum
Cc: address@hidden; address@hidden
Subject: Re: Q35 FreeBSD install status

On Mon, Sep 16, 2013 at 12:28:41PM +0000, Bret Ketchum wrote:
> 
>      As a workaround until I can uncover the qemu/FreeBSD AHCI/SATA issue, I 
> simply create a legacy IDE to hang the CD and HD from:
> 
>     -device piix4-ide \
>     -drive 
> if=none,file=/home/ehv/images/FreeBSD-9.1-RELEASE-amd64-dvd1.iso,id=drive-ide0-0-0
>  \
>     -device ide-cd,bus=ide.0,drive=drive-ide0-0-0,id=ide0-0-0 \
>     -drive 
> if=none,file=/home/ehv/images/r060501.img,format=raw,id=drive-ide0-0-1 \
>     -device ide-hd,bus=ide.0,drive=drive-ide0-0-1,id=ide0-0-1 \
> 
>     But now the e1000 emulated network device under q35 does not seem to pass 
> interrupts. Using:
> 
>     -netdev 
> tap,id=hostnet0,script=/home/ehv/images/qemu-ifup,downscript=/home/ehv/images/qemu-ifdown
>  \
>     -device e1000,netdev=hostnet0 \
> 
>     Or a user network:
> 
>     -netdev user,id=hostnet0,net=192.168.76.0/24,dhcpstart=192.168.76.9 \
> 
>     But machine pc-i440fx-1.6 works just fine. Anyone have any
>     thoughts on where to start looking or a possible workaround?

Maybe irq gets asserted, but guest does not have a handler?
Take a look at system log, that might give some hints.


-- 
MST