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

Re: [Xen-devel] [Qemu-devel] [PATCH v3] libxl: usb2 and usb3 controller support for upstream qemu

Il 14/08/2013 12:30, Fabio Fantoni ha scritto:
Il 18/07/2013 14:35, Paolo Bonzini ha scritto:
Il 18/07/2013 14:31, Andreas Färber ha scritto:
I'm just curious, why is this so complicated?  Is this likely to be
fragile and break in the future?
As pointed out previously, the bus=pci.0 bit will break with different
PCI host bridges, such as the q35 machine existing today (-M q35 uses
pcie.0 instead and it has been discussed to make q35 the default at some
point). I had thus suggested to use a variable for the bus name to
abstract it. For -M pc-i440fx-1.5 etc. pci.0 should continue to work.
I think if we ever made a PCIe machine the default, it would be
different from what today's q35.  In particular it probably should
include a default DMI-to-PCI bridge, so as to make the command line
compatible with i440FX-based machines.


FWIK q35 is not supported now on xen.
Anyone on this?

Based on Anthony Liguori reply the usb2 hardcoded parameter should be stable and will be supported in future:

There is also reply of Ian Jackson:

I had also posted v4 of patch:

Reposted the tests results:

Tested on linux domU (ubuntu 12.04 64 bit) with usb redirection:
- with usb1 and usb2 working and no problem found.

- with usb3 linux sees the usb3 controller but usbredirection not working (tested with qemu 1.3 of xen-unstable)

Tested on windows 7 pro 64 bit domU with usb redirection:

- with usb1 not working, windows sees the usb devices (flash mass storage) with error (unable to start device, code 10); seems
windows bugs.

- with usb2 working and no problem found.

- with usb3 not working, windows sees the usb controller but usbredirection is not working (tested with qemu 1.3 of xen-unstable)

About usb3 seems that qemu does not support some functionalities for now.

Qemu log on usb3 test:
xhci_cap_read: reg 2 unimplemented
xhci: unimplemented command 52
xhci: ERDP out of bounds: 7e7d5000
xhci: ER[7] at 0 len 0
xhci: asserted controller error
xhci: ERDP out of bounds: 7eace000
xhci: ER[6] at 0 len 0
xhci: asserted controller error
xhci: slot 1 has no device
xhci: error firing data transfer

There wasn't any reply about this for one month. usb1 controller is already supported by xen but it has some problems with latest windows. usb2 works with both linux and windows but it needs this patch or a similar one to add support on xen. usb3 can be removed for now if someone think unimplemented functions are a problem.
Thanks for any reply.


Xen-devel mailing list



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