Alexandros Manakos
2007-Oct-14 15:11 UTC
[Xen-users] USB Support for DomU - pciback.hide Problem
Hey everybody, i have a problem getting the usb interface running in my domU. I successfully booted my dom0 and the log says "/pciback 0000:00:1d.7: seizing device" (so did the parameters in grub.conf etc.) / I also successfully started the virtual machine (domU) with "xm create xmDebian pci=0000:00:1d.7" with no errors. BUT when i connect to the domU machine and make a "lspci" it shows nothing...no devices... The Log of the VM (domU) says: Oct 14 17:53:38 kernel: Allocating PCI resources starting at 10000000 (gap: 04800000:fb800000) Oct 14 17:53:39 kernel: PCI: setting up Xen PCI frontend stub Oct 14 17:53:39 kernel: pcifront pci-0: Installing PCI frontend Oct 14 17:53:39 kernel: pcifront pci-0: Creating PCI Frontend Bus 0000:00 Oct 14 17:53:39 kernel: PCI: System does not support PCI Oct 14 17:53:39 kernel: PCI: System does not support PCI Can anybody help me getting the usb-interface running in my domU? Iam Using eisxen as dom0 but it doesnt make any difference to any other xen-system as i think. As DomU i tried debian and eisfair. in domU: If i do a "cat /proc/bus/pci/devices" it also shows nothing...(there is no /proc/bus/usb/devices) I might forgot to mention that when i run lspci in Dom0 it shows me the "hided" usb device. Isnt it supposed to be hidden? Greetings Alexandros _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Janusz Ulanowski
2007-Oct-17 12:37 UTC
Re: [Xen-users] USB Support for DomU - pciback.hide Problem
On 14/10/2007, Alexandros Manakos <alexandros@manakos.de> wrote:> > Hey everybody, > > i have a problem getting the usb interface running in my domU. I > successfully booted my dom0 and the log says "/pciback 0000:00:1d.7: > seizing device" (so did the parameters in grub.conf etc.) > / I also successfully started the virtual machine (domU) with "xm create > xmDebian pci=0000:00:1d.7" with no errors. > BUT when i connect to the domU machine and make a "lspci" it shows > nothing...no devices... > > The Log of the VM (domU) says: > Oct 14 17:53:38 kernel: Allocating PCI resources starting at 10000000 > (gap: 04800000:fb800000) > Oct 14 17:53:39 kernel: PCI: setting up Xen PCI frontend stub > Oct 14 17:53:39 kernel: pcifront pci-0: Installing PCI frontend > Oct 14 17:53:39 kernel: pcifront pci-0: Creating PCI Frontend Bus 0000:00 > Oct 14 17:53:39 kernel: PCI: System does not support PCI > Oct 14 17:53:39 kernel: PCI: System does not support PCI > > Can anybody help me getting the usb-interface running in my domU? > Iam Using eisxen as dom0 but it doesnt make any difference to any other > xen-system as i think. As DomU i tried debian and eisfair. > > in domU: If i do a "cat /proc/bus/pci/devices" it also shows > nothing...(there is no /proc/bus/usb/devices) > > I might forgot to mention that when i run lspci in Dom0 it shows me the > "hided" usb device. Isnt it supposed to be hidden? > > Greetings > AlexandrosI have exactly the same problem. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pierre Bernhardt
2007-Oct-17 13:24 UTC
Re: [Xen-users] USB Support for DomU - pciback.hide Problem
Janusz Ulanowski schrieb:> On 14/10/2007, Alexandros Manakos <alexandros@manakos.de> wrote: >> Hey everybody, >> >> i have a problem getting the usb interface running in my domU. I >> successfully booted my dom0 and the log says "/pciback 0000:00:1d.7: >> seizing device" (so did the parameters in grub.conf etc.) >> / I also successfully started the virtual machine (domU) with "xm create >> xmDebian pci=0000:00:1d.7" with no errors. >> BUT when i connect to the domU machine and make a "lspci" it shows >> nothing...no devices...Janusz Ulanowski schrieb:> On 14/10/2007, Alexandros Manakos <alexandros@manakos.de> wrote: >> Hey everybody, >> >> i have a problem getting the usb interface running in my domU. I >> successfully booted my dom0 and the log says "/pciback 0000:00:1d.7: >> seizing device" (so did the parameters in grub.conf etc.) >> / I also successfully started the virtual machine (domU) with "xm create >> xmDebian pci=0000:00:1d.7" with no errors.Hi, I''d run a config which use my whole usb card in domu on debian xen on etch (3.0.3). My NEC Usb and my ALi USB has claimed more than one pci devices. Here a tree of mypcidevices with ali: xen:/etc/xen# lspci -vt -[0000:00]-+-00.0 Advanced Micro Devices [AMD] AMD-760 MP [IGD4-2P] System Conr +-01.0-[0000:01]----05.0 nVidia Corporation NV43 [GeForce 6200] +-07.0 Advanced Micro Devices [AMD] AMD-768 [Opus] ISA +-07.1 Advanced Micro Devices [AMD] AMD-768 [Opus] IDE +-07.3 Advanced Micro Devices [AMD] AMD-768 [Opus] ACPI +-08.0-[0000:02]--+-00.0 Sun Microsystems Computer Corp. EBUS | +-00.1 Sun Microsystems Computer Corp. Happy Meal | +-01.0 Sun Microsystems Computer Corp. EBUS | +-01.1 Sun Microsystems Computer Corp. Happy Meal | +-02.0 Sun Microsystems Computer Corp. EBUS | +-02.1 Sun Microsystems Computer Corp. Happy Meal | +-03.0 Sun Microsystems Computer Corp. EBUS | \-03.1 Sun Microsystems Computer Corp. Happy Meal +-09.0 Adaptec AHA-3960D / AIC-7899A U160/m +-09.1 Adaptec AHA-3960D / AIC-7899A U160/m \-10.0-[0000:03]--+-00.0 Advanced Micro Devices [AMD] AMD-768 [OpusB +-04.0 Adaptec AHA-2940U/UW/D / AIC-7881U +-05.0 Silicon Image, Inc. SiI 3114 [SATALink/SATr +-07.0 ALi Corporation USB 1.1 Controller +-07.1 ALi Corporation USB 1.1 Controller +-07.2 ALi Corporation USB 1.1 Controller +-07.3 ALi Corporation USB 2.0 Controller \-08.0 3Com Corporation 3c905C-TX/TX-M [Tornado] I''d trouble by pass only one of them to the domu so could you check first, that you will export all your pci-devices of the usb-card? Which xen-version is used in domu please? Is it an hvm domu? Im not shure but I mean exporting pci-devices to an hvm dom is not working, yet. Could you give me a pcilist -tv to see your device tree, please? Do you have checked, that the device is really claimed by the pciback? Check with ls -l /sys/bus/pci/devices/0000\:00\:1d.7. Here is an example: xen:/etc/xen# ls -l /sys/bus/pci/devices/0000\:02\:00.1/driver|less lrwxrwxrwx 1 root root 0 2007-10-17 13:17 /sys/bus/pci/devices/0000:02:00.1/\ driver -> ../../../../bus/pci/drivers/pciback And last question: Which guest kernel you are using? MfG... Pierre Bernhardt _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Janusz Ulanowski
2007-Oct-18 09:20 UTC
Re: [Xen-users] USB Support for DomU - pciback.hide Problem
On 17/10/2007, Pierre Bernhardt <pierre@starcumulus.owl.de> wrote:> > Janusz Ulanowski schrieb: > > On 14/10/2007, Alexandros Manakos <alexandros@manakos.de> wrote: > >> Hey everybody, > >> > >> i have a problem getting the usb interface running in my domU. I > >> successfully booted my dom0 and the log says "/pciback 0000:00:1d.7: > >> seizing device" (so did the parameters in grub.conf etc.) > >> / I also successfully started the virtual machine (domU) with "xm > create > >> xmDebian pci=0000:00:1d.7" with no errors. > >> BUT when i connect to the domU machine and make a "lspci" it shows > >> nothing...no devices... > Janusz Ulanowski schrieb: > > On 14/10/2007, Alexandros Manakos <alexandros@manakos.de> wrote: > >> Hey everybody, > >> > >> i have a problem getting the usb interface running in my domU. I > >> successfully booted my dom0 and the log says "/pciback 0000:00:1d.7: > >> seizing device" (so did the parameters in grub.conf etc.) > >> / I also successfully started the virtual machine (domU) with "xm > create > >> xmDebian pci=0000:00:1d.7" with no errors. > Hi, > > I''d run a config which use my whole usb card in domu on debian xen on etch > (3.0.3). > > My NEC Usb and my ALi USB has claimed more than one pci devices. Here a > tree of mypcidevices with ali: > > xen:/etc/xen# lspci -vt > -[0000:00]-+-00.0 Advanced Micro Devices [AMD] AMD-760 MP [IGD4-2P] > System Conr > +-01.0-[0000:01]----05.0 nVidia Corporation NV43 [GeForce > 6200] > +-07.0 Advanced Micro Devices [AMD] AMD-768 [Opus] ISA > +-07.1 Advanced Micro Devices [AMD] AMD-768 [Opus] IDE > +-07.3 Advanced Micro Devices [AMD] AMD-768 [Opus] ACPI > +-08.0-[0000:02]--+-00.0 Sun Microsystems Computer Corp. EBUS > | +-00.1 Sun Microsystems Computer Corp. Happy > Meal > | +-01.0 Sun Microsystems Computer Corp. EBUS > | +-01.1 Sun Microsystems Computer Corp. Happy > Meal > | +-02.0 Sun Microsystems Computer Corp. EBUS > | +-02.1 Sun Microsystems Computer Corp. Happy > Meal > | +-03.0 Sun Microsystems Computer Corp. EBUS > | \-03.1 Sun Microsystems Computer Corp. Happy > Meal > +-09.0 Adaptec AHA-3960D / AIC-7899A U160/m > +-09.1 Adaptec AHA-3960D / AIC-7899A U160/m > \-10.0-[0000:03]--+-00.0 Advanced Micro Devices [AMD] AMD-768 > [OpusB > +-04.0 Adaptec AHA-2940U/UW/D / AIC-7881U > +-05.0 Silicon Image, Inc. SiI 3114 > [SATALink/SATr > +-07.0 ALi Corporation USB 1.1 Controller > +-07.1 ALi Corporation USB 1.1 Controller > +-07.2 ALi Corporation USB 1.1 Controller > +-07.3 ALi Corporation USB 2.0 Controller > \-08.0 3Com Corporation 3c905C-TX/TX-M > [Tornado] > > > I''d trouble by pass only one of them to the domu so could you check > first, that you will export all your pci-devices of the usb-card? > > Which xen-version is used in domu please? > > Is it an hvm domu? Im not shure but I mean exporting pci-devices to an > hvm dom is not working, yet. > > Could you give me a pcilist -tv to see your device tree, please? > > Do you have checked, that the device is really claimed by the pciback? > Check with ls -l /sys/bus/pci/devices/0000\:00\:1d.7. Here is an example: > xen:/etc/xen# ls -l /sys/bus/pci/devices/0000\:02\:00.1/driver|less > lrwxrwxrwx 1 root root 0 2007-10-17 13:17 /sys/bus/pci/devices/0000:02: > 00.1/\ > driver -> ../../../../bus/pci/drivers/pciback > > And last question: Which guest kernel you are using? > > MfG... > Pierre Bernhardt >Hi there, I use xen 3.1 installed from source. 1. before hide pci # lspci -vt -+-[0000:05]---02.0 Compaq Computer Corporation Smart Array 64xx +-[0000:02]-+-01.0 Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) | \-01.1 Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) \-[0000:00]-+-00.0 Broadcom CMIC-WS Host Bridge (GC-LE chipset) +-00.1 Broadcom CMIC-WS Host Bridge (GC-LE chipset) +-00.2 Broadcom CMIC-LE +-02.0 Adaptec AHA-3960D / AIC-7899A U160/m +-02.1 Adaptec AHA-3960D / AIC-7899A U160/m +-03.0 ATI Technologies Inc Rage XL +-04.0 Broadcom Corporation NetXtreme BCM5702X Gigabit Ethernet +-05.0 Compaq Computer Corporation Advanced System Management Controller +-0f.0 Broadcom CSB5 South Bridge +-0f.1 Broadcom CSB5 IDE Controller +-0f.2 Broadcom OSB4/CSB5 OHCI USB Controller +-0f.3 Broadcom CSB5 LPC bridge +-11.0 Broadcom CIOB-X2 PCI-X I/O Bridge \-11.2 Broadcom CIOB-X2 PCI-X I/O Bridge # lspci -v ... 00:0f.2 USB Controller: Broadcom OSB4/CSB5 OHCI USB Controller (rev 05) (prog-if 10 [OHCI]) Subsystem: Broadcom OSB4/CSB5 OHCI USB Controller Flags: bus master, medium devsel, latency 64, IRQ 11 Memory at f5fc0000 (32-bit, non-prefetchable) [size=4K] ... # lsusb Bus 001 Device 002: ID 04e8:3242 Samsung Electronics Co., Ltd Bus 001 Device 001: ID 0000:0000 --------------------------- 2. hiding pci from Dom0 # echo -n ''0000:00:0f.2'' > /sys/bus/pci/drivers/ohci_hcd/unbind # echo -n ''0000:00:0f.2'' > /sys/bus/pci/drivers/pciback/new_slot # echo -n ''0000:00:0f.2'' > /sys/bus/pci/drivers/pciback/bind ----------------- 3. after hiding # lspci -v ... 00:0f.2 USB Controller: Broadcom OSB4/CSB5 OHCI USB Controller (rev 05) (prog-if 10 [OHCI]) Subsystem: Broadcom OSB4/CSB5 OHCI USB Controller Flags: medium devsel, IRQ 11 Memory at f5fc0000 (32-bit, non-prefetchable) [disabled] [size=4K] ... # lsusb [empty] ---------------------------- 4. starting domU with option in config pci = [ ''00:0f.2'' ] xm log in attachement ---------------------- 5. lspci -v in DomU [empty] ------------ Thanks for you help _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pierre Bernhardt
2007-Oct-18 17:31 UTC
[Xen-users] Re: USB Support for DomU - pciback.hide Problem
Janusz Ulanowski schrieb:> Hi there, >Hi, I removed old lines from message... I will only comment the relevant lines.> I use xen 3.1 installed from source.Ok, it''s newer the one I use :-) I think it should work "better" than on my server.> 1. before hide pci > > # lspci -vt...> +-0f.2 Broadcom OSB4/CSB5 OHCI USB Controller... Looks like it''s only an USB 1.1 Controller. That''s ok. I can see you have two pci domains on board.> > # lspci -v > ... > 00:0f.2 USB Controller: Broadcom OSB4/CSB5 OHCI USB Controller (rev 05) > (prog-if 10 [OHCI]) > Subsystem: Broadcom OSB4/CSB5 OHCI USB Controller > Flags: bus master, medium devsel, latency 64, IRQ 11 > Memory at f5fc0000 (32-bit, non-prefetchable) [size=4K] > ... > > # lsusb > Bus 001 Device 002: ID 04e8:3242 Samsung Electronics Co., Ltd > Bus 001 Device 001: ID 0000:0000 > > --------------------------- > 2. hiding pci from Dom0 > > > # echo -n ''0000:00:0f.2'' > /sys/bus/pci/drivers/ohci_hcd/unbind > # echo -n ''0000:00:0f.2'' > /sys/bus/pci/drivers/pciback/new_slot > # echo -n ''0000:00:0f.2'' > /sys/bus/pci/drivers/pciback/bindOk.> ----------------- > 3. after hiding > > > # lspci -v > ... > 00:0f.2 USB Controller: Broadcom OSB4/CSB5 OHCI USB Controller (rev 05) > (prog-if 10 [OHCI]) > Subsystem: Broadcom OSB4/CSB5 OHCI USB Controller > Flags: medium devsel, IRQ 11 > Memory at f5fc0000 (32-bit, non-prefetchable) [disabled] [size=4K] > ...Thats normal because pci is still there, only other module has hands on the device.> # lsusb > [empty]True because pciback is no usb-driver ;-)> ---------------------------- > 4. starting domU with option in config > pci = [ ''00:0f.2'' ]Normally ok. As you have to pcidomains it is possible you need to preadd to 0000:00:0f.2 instead of the short 00:0f.2.> xm log in attachementI cannot see a problem here, but I have not enough experience to understand the log fully. In log they say that it is waiting for usb. What say''s lsusb in domu?> ---------------------- > > 5. lspci -v in DomU > [empty]Is there any lines in dmesg on domu which shows problems with the pci device? I think dmesg output and ls -R (or filetree command) of sysfs is helpfull. MfG... Pierre Bernhardt> Thanks for you helpYou''re welcome, hopefully we find the problem. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Janusz Ulanowski
2007-Oct-19 13:25 UTC
Re: [Xen-users] Re: USB Support for DomU - pciback.hide Problem
On 18/10/2007, Pierre Bernhardt <pierre@starcumulus.owl.de> wrote:> > Janusz Ulanowski schrieb: > > Hi there, > > > Hi, > > I removed old lines from message... I will only comment the relevant > lines. > > > I use xen 3.1 installed from source. > Ok, it''s newer the one I use :-) I think it should work "better" than on > my server. > > > 1. before hide pci > > > > # lspci -vt > ... > > +-0f.2 Broadcom OSB4/CSB5 OHCI USB Controller > ... > > Looks like it''s only an USB 1.1 Controller. That''s ok. > I can see you have two pci domains on board. > > > > > # lspci -v > > ... > > 00:0f.2 USB Controller: Broadcom OSB4/CSB5 OHCI USB Controller (rev 05) > > (prog-if 10 [OHCI]) > > Subsystem: Broadcom OSB4/CSB5 OHCI USB Controller > > Flags: bus master, medium devsel, latency 64, IRQ 11 > > Memory at f5fc0000 (32-bit, non-prefetchable) [size=4K] > > ... > > > > # lsusb > > Bus 001 Device 002: ID 04e8:3242 Samsung Electronics Co., Ltd > > Bus 001 Device 001: ID 0000:0000 > > > > --------------------------- > > 2. hiding pci from Dom0 > > > > > > # echo -n ''0000:00:0f.2'' > /sys/bus/pci/drivers/ohci_hcd/unbind > > # echo -n ''0000:00:0f.2'' > /sys/bus/pci/drivers/pciback/new_slot > > # echo -n ''0000:00:0f.2'' > /sys/bus/pci/drivers/pciback/bind > Ok. > > > > ----------------- > > 3. after hiding > > > > > > # lspci -v > > ... > > 00:0f.2 USB Controller: Broadcom OSB4/CSB5 OHCI USB Controller (rev 05) > > (prog-if 10 [OHCI]) > > Subsystem: Broadcom OSB4/CSB5 OHCI USB Controller > > Flags: medium devsel, IRQ 11 > > Memory at f5fc0000 (32-bit, non-prefetchable) [disabled] > [size=4K] > > ... > Thats normal because pci is still there, only other module has hands on > the device. > > > # lsusb > > [empty] > True because pciback is no usb-driver ;-) > > > ---------------------------- > > 4. starting domU with option in config > > pci = [ ''00:0f.2'' ] > Normally ok. As you have to pcidomains it is possible you need to > preadd to 0000:00:0f.2 instead of the short 00:0f.2. > > > > xm log in attachement > I cannot see a problem here, but I have not enough experience to > understand > the log fully. > > In log they say that it is waiting for usb. What say''s lsusb in domu? > > > ---------------------- > > > > 5. lspci -v in DomU > > [empty] > Is there any lines in dmesg on domu which shows problems with the > pci device? > > I think dmesg output and ls -R (or filetree command) of sysfs is helpfull. > > > MfG... > Pierre Bernhardt > > > Thanks for you help > You''re welcome, hopefully we find the problem.Hi, lsub on DomU shows nothing kernel config in config-2.6.18-xenhigh03 dmesg DomU in dmesg.log list of /sys in list-sys.txt I tried to do it with second ethernet device and it''s is the same problem. I had no problem with xen 3.0.4 Maybe some issue with kernel configuration but i have no idea what it is. Kernel was compiled with (gcc version 4.1.3 20070831 (prerelease) (Debian 4.1.2-16) thanks very much. -- Janusz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pierre Bernhardt
2007-Oct-20 12:53 UTC
[Xen-users] Re: USB Support for DomU - pciback.hide Problem
Janusz Ulanowski schrieb:> On 18/10/2007, Pierre Bernhardt <pierre@starcumulus.owl.de> wrote: >> Janusz Ulanowski schrieb: >>> I use xen 3.1 installed from source. >> Ok, it''s newer the one I use :-) I think it should work "better" than on >> my server. >> I think dmesg output and ls -R (or filetree command) of sysfs is helpfull. > lsub on DomU shows nothing > kernel config in config-2.6.18-xenhigh03 > dmesg DomU in dmesg.log > list of /sys in list-sys.txtI''m sorry. list-sys looks like come from dom0. I mean sysfs from domu instead ;-)> I tried to do it with second ethernet device and it''s is the same problem.> I had no problem with xen 3.0.4Oh, thats new information for me :-/ I think I have not enough experience to help on newer release. If it is on 3.0.4 working but not on 3.1 so I think I could not further help.> Maybe some issue with kernel configuration but i have no idea what it is. > Kernel was compiled with > (gcc version 4.1.3 20070831 (prerelease) (Debian 4.1.2-16)If you have a not-hvm domain running, so you can try to use the same kernel in dom0. I do this by me so if card is running in dom0 it should work in domu, mostly too. If this will not work I think its more relatet to the new xen release. If this will work it could be more on domu kernel. I mean that 3.1 could usbdevices map to domu directly. I''s possible that here is a cross over problem with pci-hiding? I have no idea. Cheers.... Pierre Bernhardt _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Janusz Ulanowski
2007-Oct-23 09:50 UTC
Re: [Xen-users] Re: USB Support for DomU - pciback.hide Problem
On 20/10/2007, Pierre Bernhardt <pierre@starcumulus.owl.de> wrote:> > Janusz Ulanowski schrieb: > > On 18/10/2007, Pierre Bernhardt <pierre@starcumulus.owl.de> wrote: > >> Janusz Ulanowski schrieb: > >>> I use xen 3.1 installed from source. > >> Ok, it''s newer the one I use :-) I think it should work "better" than > on > >> my server. > >> I think dmesg output and ls -R (or filetree command) of sysfs is > helpfull. > > lsub on DomU shows nothing > > kernel config in config-2.6.18-xenhigh03 > > dmesg DomU in dmesg.log > > list of /sys in list-sys.txt > I''m sorry. list-sys looks like come from dom0. I mean sysfs from domu > instead > ;-)No, it''s from DomU> I tried to do it with second ethernet device and it''s is the same problem. > > > I had no problem with xen 3.0.4 > Oh, thats new information for me :-/ I think I have not enough experience > to help on newer release. If it is on 3.0.4 working but not on 3.1 so I > think I could not further help. > > > Maybe some issue with kernel configuration but i have no idea what it > is. > > Kernel was compiled with > > (gcc version 4.1.3 20070831 (prerelease) (Debian 4.1.2-16) > If you have a not-hvm domain running, so you can try to use the same > kernel > in dom0. I do this by me so if card is running in dom0 it should work in > domu, mostly too. If this will not work I think its more relatet to the > new xen release. If this will work it could be more on domu kernel. > > I mean that 3.1 could usbdevices map to domu directly. I''s possible that > here > is a cross over problem with pci-hiding? I have no idea. > > Cheers.... > Pierre BernhardtThanks Pierre anyway. Maybe it''s some bug. -- Janusz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users