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

Re: [Xen-devel] Vt-d: problem passthrough a PCI ISDN-board in WIndowsXP HVM domU with 3.5-unstable



On Wed, Dec 02, 2009 at 04:35:44PM +0100, Ralf Bonenkamp wrote:
> Hi all,
> 
> yesterday I've build the latest xen-unstable on top of a Ubuntu 9.10 x64 
> server.
> Now I setup a XP domU (same problem occurs also with Windos 7 domU) and 
> passthrough a PCI device (ISDN board) into this domU.
> This is basically working and the device is shown in device manager BUT the 
> device lacks the SUBSYS part of the device Id and therefore the device can't 
> be installed or the driver itself failed to load afterwards.
> 
> Example:
> device Id found on "real" system: PCI\VEN_1397&DEV_08B4&SUBSYS_B5401397
> 
> device Id in HVM domU: PCI\VEN_1397&DEV_08B4&SUBSYS_00000000
> 
> 
> 
> This seems to be some sort of regression, because with 3.4.1 (around two 
> month ago) I was able to install the driver and communicate with the same 
> device in a XP domU but had some stability issues, which I now wanted to sort 
> out...
> 
> 
> 
> Any helpful hints are highly appreciated :-)
> 
> 
> 
> If any additional logs/informations are needed please let me know.

Hi Ralf,

I'm having some trouble reproducing this problem.
Could you be a bit more specific about which versions
of xen-unstable and qemu-xen-unstable (aka tools/ioemu-remote)
you are using:

cd $XEN_SOURCE_DIR
$ hg tip
$ (cd tools/ioemu-remote && git log -1;)

Also, which dom0 kernel are you running?


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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