On 18/10/2007, Pierre Bernhardt <pierre@xxxxxxxxxxxxxxxxxx> 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
