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

[Xen-users] pci uhci delegation not working (OR: can we please just get usb support back?)


  • To: "Xen Users" <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Florian Heigl" <florian.heigl@xxxxxxxxx>
  • Date: Sat, 29 Mar 2008 05:29:32 +0100
  • Delivery-date: Fri, 28 Mar 2008 21:30:01 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=DqDsbuSa0X3C6XYiKJ+9Eo9klVgwSnIRV9DfMnhCc12y6ni9DdTtAJxjC6RoMfLENfcrcwVfxZ2o4ND5WDVGyNr6vHEbPw9a6mo5VRZlAb2EOtAebJp43dhtWVMFJ9GOsnSgfWe1ZPvYOFcM3jfMadqZrdS+0kfIF/8pDE1E/sg=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,

I'm trying to "push" my usb controllers and grahpics into a pvm linux
domU, the graphics bit appears to work just fine :/

I have gone through some of the steps that led some posters here to
success, unfortunately no luck for me.

This is the error I'm getting:

Started domain cent-desk01
rtc: IRQ 8 is not free.
rtc: IRQ 8 is not free.
i8042.c: No controller found.
Red Hat nash version 5.1.19.6 starting
uhci_hcd 0000:00:01.0: unable to allocate consistent memory for frame list
uhci_hcd 0000:00:01.0: startup error -16
uhci_hcd 0000:00:01.0: init 0000:00:01.0 fail, -16
uhci_hcd 0000:00:01.1: unable to allocate consistent memory for frame list
uhci_hcd 0000:00:01.1: startup error -16
uhci_hcd 0000:00:01.1: init 0000:00:01.1 fail, -16
uhci_hcd 0000:00:02.0: unable to allocate consistent memory for frame list
uhci_hcd 0000:00:02.0: startup error -16
uhci_hcd 0000:00:02.0: init 0000:00:02.0 fail, -16
uhci_hcd 0000:00:02.1: unable to allocate consistent memory for frame list
uhci_hcd 0000:00:02.1: startup error -16
uhci_hcd 0000:00:02.1: init 0000:00:02.1 fail, -16
uhci_hcd 0000:00:02.2: unable to allocate consistent memory for frame list
uhci_hcd 0000:00:02.2: startup error -16
uhci_hcd 0000:00:02.2: init 0000:00:02.2 fail, -16

[ domU just hangs after that ]
but i think the usb controllers start to get reinitialized as the
mouse / keyboard lose power at that point.


I echo'ed each pci id to pciback/new_slot, pciback/bind,
pciback/permissive in that order, using cat shows permissive is set
just fine

dom0 debian etch 2.6.18-5-xen-amd64
domU centos 5.1
xen 3.0.3-1 (holy shit is that old!)

bios iommu enabled (does it matter for pvm?)


(debian etch doesn't recognize the ICH9 components at all, but i don't
care as they'll be mapped to the domU which happens to have the
fitting drivers)

00:1a.0 USB Controller: Intel Corporation Unknown device 2937 (rev 02)
00:1a.1 USB Controller: Intel Corporation Unknown device 2938 (rev 02)
00:1a.2 USB Controller: Intel Corporation Unknown device 2939 (rev 02)
00:1a.7 USB Controller: Intel Corporation Unknown device 293c (rev 02)
00:1d.0 USB Controller: Intel Corporation Unknown device 2934 (rev 02)
00:1d.1 USB Controller: Intel Corporation Unknown device 2935 (rev 02)
00:1d.2 USB Controller: Intel Corporation Unknown device 2936 (rev 02)
00:1d.7 USB Controller: Intel Corporation Unknown device 293a (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc R580 [Radeon
X1900 XT] Primary
01:00.1 Display controller: ATI Technologies Inc R580 [Radeon X1900
XT] Secondary

domU conf
extra = 'ro root=LABEL=/ console=xvc0 rhgb quiet'
pci = [ 
'0000:01:00.0','0000:01:00.1','0000:00:1a.0','0000:00:1a.1','0000:00:1a.7','0000:00:1d.0','0000:00:1d.1','0000:00:1d.2','0000:00:1d.7'
]

menu.lst
module          /vmlinuz-2.6.18-5-xen-amd64 root=/dev/sda2 ro
console=tty0 pciback.permissive
pciback.hide=(01:00.0)(01:00.1)(00:1a.0)(00:1a.1)(00:1a.2)(00:1a.7)(00:1d.0)(00:1d.1)(00:1d.2)(00:1d.7)

i also tried swiotlb=force (domU crash) iommu=force (same result as
w/o), but i dont exactly know what these do anyway, i tried to stir up
some documentation on those, but turned up quite blank so far.

To me this somewhat feels like not a xen issue dom0 but one in the
domU, still I'd be glad about any input, or hints as to maybe working
around the problem.
Summed what I'm trying to do is to build a loadbalaced (enomalism)
shared root cluster (opensharedroot) of dom0s, where some domUs stay
local to a specific domU, one is the firewall for the non-vlan
external interfaces, and one is my desktop pc for the graphics card.
after successful dom0 boot it's supposed to simply launch a xen
enabled kernel instead of the standard one and otherwise look just the
same, keeping it bootable outside of xen.

So far, it seems possible within a few more rainy weekends, supposing
i somehow get my keyboard activated in the domU :))))

Any hints?
Florian





-- 
'Sie brauchen sich um Ihre Zukunft keine Gedanken zu machen'

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


 


Rackspace

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