[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] slow pciback
I'm using Xen 3.0.3 on Slamd64 11.0 and when I pass the PCI-devices bellow to guest domain it's really slow access to the device nut drivers loads properly. Is there a bug that causes this or how can I solve this? My menu.lst for grub looks like this: # Linux bootable partition config begins title Xen-2.6.16.29 (hda1) root (hd0,0) kernel /boot/xen-3.gz dom0_mem=262144module /boot/vmlinuz-2.6.16.29-xen root=/dev/hda1 ro vga=791 max_loop=64 pciback.hide=(00:10.0)(00:10.1)(00:10.2)(00:10.3)(00:10.4) # Linux bootable partition config ends The config file for xen guest domain looks like: pci = [ '00:10.0', '00:10.1', '00:10.2', '00:10.3', '00:10.4' ]00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 90) 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 90) 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 90) 00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 90) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 90) When I do a dmesg I get this messages about my devices:pciback 0000:00:10.4: Driver tried to write to a read-only configuration space field at offset 0x84, size 2. This may be harmless, but if you have problems with your device: 1) see permissive attribute in sysfs2) report problems to the xen-devel mailing list along with details of your device obtained from lspci. PCI: Enabling device 0000:00:10.4 (0000 -> 0002) ACPI: PCI Interrupt 0000:00:10.4[C] -> GSI 22 (level, low) -> IRQ 18pciback 0000:00:10.0: Driver tried to write to a read-only configuration space field at offset 0x84, size 2. This may be harmless, but if you have problems with your device: 1) see permissive attribute in sysfs2) report problems to the xen-devel mailing list along with details of your device obtained from lspci. PCI: Enabling device 0000:00:10.0 (0000 -> 0001) ACPI: PCI Interrupt 0000:00:10.0[A] -> GSI 20 (level, low) -> IRQ 21pciback 0000:00:10.1: Driver tried to write to a read-only configuration space field at offset 0x84, size 2. This may be harmless, but if you have problems with your device: 1) see permissive attribute in sysfs2) report problems to the xen-devel mailing list along with details of your device obtained from lspci. PCI: Enabling device 0000:00:10.1 (0000 -> 0001) ACPI: PCI Interrupt 0000:00:10.1[C] -> GSI 22 (level, low) -> IRQ 18pciback 0000:00:10.2: Driver tried to write to a read-only configuration space field at offset 0x84, size 2. This may be harmless, but if you have problems with your device: 1) see permissive attribute in sysfs2) report problems to the xen-devel mailing list along with details of your device obtained from lspci. PCI: Enabling device 0000:00:10.2 (0000 -> 0001) ACPI: PCI Interrupt 0000:00:10.2[B] -> GSI 21 (level, low) -> IRQ 20pciback 0000:00:10.3: Driver tried to write to a read-only configuration space field at offset 0x84, size 2. This may be harmless, but if you have problems with your device: 1) see permissive attribute in sysfs2) report problems to the xen-devel mailing list along with details of your device obtained from lspci. PCI: Enabling device 0000:00:10.3 (0000 -> 0001)My device on the guest domain is a usb serial port and I get the following from dmesg: ftdi_sio 3-1:1.0: FTDI USB Serial Device converter detected drivers/usb/serial/ftdi_sio.c: Detected FT232BM usb 3-1: FTDI USB Serial Device converter now attached to ttyUSB0 ftdi_sio 3-2:1.0: FTDI USB Serial Device converter detected drivers/usb/serial/ftdi_sio.c: Detected FT232BM usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB1 usbcore: registered new driver ftdi_sio drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver I really need help with this... Regards Claes Lindblom _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |