Re: [Xen-users] HVM DomU+Dom0 crash with PCI USB passthrough

[Gordan Bobic <gordan@xxxxxxxxxx>]

On 08/02/2013 08:17 PM, Andrew Bobulsky wrote:
> > Hello everyone,
> >
> > I've removed the PCI USB controller from one PCI slot and inserted it
> > into another. Still, when trying to boot a DomU, DomU and Dom0 hang.
> >
> > I have also tried passing the PCI USB controller with
> > device_model_version = "qemu-xen-traditional"
> > and this is what I get from xl create xenwin.cfg:
> > Parsing config from xenwin.cfg
> > xc: info: VIRTUAL MEMORY ARRANGEMENT:
> >   Loader:        0000000000100000->000000000019eea8
> >   Modules:       0000000000000000->0000000000000000
> >   TOTAL:         0000000000000000->000000007f000000
> >   ENTRY ADDRESS: 0000000000100000
> > xc: info: PHYSICAL MEMORY ALLOCATION:
> >   4KB PAGES: 0x0000000000000200
> >   2MB PAGES: 0x00000000000003f7
> >   1GB PAGES: 0x0000000000000000
> > libxl: error: libxl_exec.c:227:libxl__wait_for_offspring: Device Model not ready
> > libxl: error: libxl_pci.c:835:qemu_pci_add_xenstore: qemu refused to
> > add device: 0000:01:07.0,msitranslate=0,power_mgmt=0
> > libxl: error: libxl_exec.c:227:libxl__wait_for_offspring: Device Model not ready
> > libxl: error: libxl_pci.c:835:qemu_pci_add_xenstore: qemu refused to
> > add device: 0000:01:07.1,msitranslate=0,power_mgmt=0
> > libxl: error: libxl_exec.c:227:libxl__wait_for_offspring: Device Model not ready
> > libxl: error: libxl_pci.c:835:qemu_pci_add_xenstore: qemu refused to
> > add device: 0000:01:07.2,msitranslate=0,power_mgmt=0
> > Daemon running with PID 3627
> >
> >
> > The DomU boots fine, but doesn't detect the USB controller.
> >
> > If I try to pass one of the motherboard's USB controllers, 00:12.0 and
> > 00:12.2, I don't get any such error messages, Windows boots, but in
> > the Device manager complains about a PCI Device being unavailable for
> > use (yellow triangle with Code 28, messages would be something like
> > "Drivers not installed" (translated message, but that's what it
> > means.))
> >
> > This is my current lspci -vvv: http://pastebin.com/MBFPd3Kx
> > And this is lspci -t: http://pastebin.com/0Mk5y5db
> >
> >
> > Again, thanks for helping. :)
> Hello Guatav,
>
> I have a Gigabyte board with a similar PCI layout.  Passing any of those 
> 00:XX.Y devices doesn't play terribly well unless you ensure that as much as 
> possible is assigned to pciback; or that at least all of the USB controllers 
> are ;)
>
> Anyway, what I *know* works for me is to pass the device...
>
> > 03:00.0 USB controller: Etron Technology, Inc. EJ188/EJ198 USB 3.0 Host 
> > Controller (prog-if 30 [XHCI])
> ...through to your Windows DomU.
>
> Windows 7 _does_not_have_ drivers for this device as there is no USB3 stack.  
> The USB3 drivers from your motherboard mfg's website (ASRock?) should work to 
> get it installed after it shows up unknown in device manager.
This is pretty much the same thing I've found - I had a lot of random 
lockups passing through south-bridge USB devices, especially if they 
share interrupts. Switched to passing the discrete USB3 controller, and 
the problem went away.
Gordan

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