[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] qemu-xen-dir + PCI passthrough = BOOM



> >> (d1) [2014-01-10 03:20:29] Running option rom at ca00:0003
> >> 
> >> (d1) [2014-01-10 03:20:47] Booting from DVD/CD...
> >> (d1) [2014-01-10 03:20:47] Booting from 0000:7c00
> >> ..
> >> and I did see the PXE boot menu in my guest - so even
> >> better!
> 
> > Perfect, look like it is the fix for PCI passthrough.
> 
> Hi Konrad,
> 
> Are you sure it's the rom of the NIC, and not the iPXE rom from the emulated 
> device that
> gets run ?

Yes. I double checked that the MAC address that was given an DHCP
address was indeed for the physical hardware. And it was.

> 
> With this patch and VGA devices it still points to another rom for me.
> (it looks like it is pointing to the rom of the device with a BDF just one 
> lower than the passed through one)

That all sounds to me like a bug in QEMU which constructs
the 'world'. Then 'hvmloader' and the kernel ingest this to
create their view of what the PCI configuration/slots/etc should look like.
They use 'inb' and 'outb' instructions on the 0xcf8/0xcfc port.

Perhaps the 'vga=none' is having an hard time dealing with 
'no-VGA-but-wait-there
is-and-PT-VGA'?

Just to make sure I am not forgetting a crucial fact - if you don't
have vga=none, does the lspci output look sane?

> 
> Do you by any chance know if there is a difference in how lspci and the linux 
> kernel scan / list pci devices ?
> (for example one by reading acpi tables .. the other one by real probing .. ?)

The kernel and hvmloader all use the 'inb' and 'outb' to figure out
what the PCI space looks like.

'lspci' uses /sysfs. Thought if you use '-xxxx' I think it also does
'inb' and 'outb'. 

So it all seems to point to QEMU. 
> 
> --
> Sander
> 
> 
> >> I have not yet done the GPU - this issue was preventing me from using
> >> qemu-xen as it would always blow up before SeaBIOS was in the picture.
> >> 
> >> If you would like to put 'Reported-and-Tested-by: Konrad Rzeszutek Wilk
> >> <konrad.wilk@xxxxxxxxxx>' please do.
> 
> > Will do.
> 
> >> Thank you!
> >> > 
> >> > 
> >> > diff --git a/hw/xen/xen_pt.c b/hw/xen/xen_pt.c
> >> > index 6dd7a68..2bbdb6d 100644
> >> > --- a/hw/xen/xen_pt.c
> >> > +++ b/hw/xen/xen_pt.c
> >> > @@ -440,8 +440,8 @@ static int 
> >> > xen_pt_register_regions(XenPCIPassthroughState *s)
> >> >  
> >> >          s->bases[PCI_ROM_SLOT].access.maddr = d->rom.base_addr;
> >> >  
> >> > -        memory_region_init_rom_device(&s->rom, OBJECT(s), NULL, NULL,
> >> > -                                      "xen-pci-pt-rom", d->rom.size);
> >> > +        memory_region_init_io(&s->rom, OBJECT(s), &ops, &s->dev,
> >> > +                              "xen-pci-pt-rom", d->rom.size);
> >> >          pci_register_bar(&s->dev, PCI_ROM_SLOT, 
> >> > PCI_BASE_ADDRESS_MEM_PREFETCH,
> >> >                           &s->rom);
> >> >  
> >> > 
> >> > -- 
> >> > Anthony PERARD
> 
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.