WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Problem passing a HP-DAT (USB) device to domU (fwd) (this ti

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Problem passing a HP-DAT (USB) device to domU (fwd) (this time with outputs!)
From: Matthias Wolf <matthias.wolf@xxxxxx>
Date: Wed, 08 Aug 2007 00:47:00 +0200
Delivery-date: Fri, 17 Aug 2007 09:53:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
(lspci-output added at the end of this mail!) Hi specialists,
I'm trying to pass an HP Surestore USB-drive to a domU. I'm hiding the
pci-device in the dom0, and capturing it in the domU. Although this works fine I receive the following lines in /var/log/syslog of the dom0 after a reboot
=======================================================================
Aug  8 00:04:49 localhost kernel: pciback 0000:00:1d.7: Driver tried to
write to a read-only configuration space field at offset 0x54,
size 2. This may be harmless, but if you have problems with your device:
Aug  8 00:04:49 localhost kernel: 1) see permissive attribute in sysfs
Aug  8 00:04:49 localhost kernel: 2) report problems to the xen-devel
mailing list along with details of your device obtained from lspci.
======================================================================= and the tapedrive wouldn't work: udev fails to create devicefiles in the domU.
I'm not quite sure what I'm expected to check in the /sys-tree: root has
write-permissions all the way down the branches. I'm using the stable version of the xen-hypervisor 3.0.3-0-2 (debian).
As I kind of *need* this functionality I'd be very grateful for any
kind of help or hint. Thanx in advance,
Bests from Vienna/Austria
Matthew A. Wolf pS.: THANKS a whole lot for such a fine piece of software! ppS.: SORRY! Forgot the output of lspci in the last mail - here is the output from lspci in the dom0:
===================================================================
00:00.0 Host bridge: Intel Corporation 5000V Chipset Memory Controller Hub (rev b1) 00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 2-3 (rev b1) 00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev b1) 00:08.0 System peripheral: Intel Corporation 5000 Series Chipset DMA Engine (rev b1) 00:10.0 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev b1) 00:10.1 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev b1) 00:10.2 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev b1) 00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev b1) 00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev b1) 00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev b1) 00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev b1) 00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09) 00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09) 00:1d.1 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09) 00:1d.2 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09) 00:1d.3 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 (rev 09) 00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)
00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09) 00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09) 00:1f.2 IDE interface: Intel Corporation 631xESB/632xESB/3100 Chipset SATA Storage Controller IDE (rev 09) 00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 09) 01:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01) 01:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01) 02:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01) 02:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 (rev 01) 02:02.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3 (rev 01) 05:00.0 Ethernet controller: Intel Corporation 631xESB/632xESB DPT LAN Controller Copper (rev 01) 05:00.1 Ethernet controller: Intel Corporation 631xESB/632xESB DPT LAN Controller Copper (rev 01)
09:0c.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02)
09:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
======================================================================
The device in question is 00:1d.7. The output of lspci in the domU is:
======================================================================
00:00.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09) ======================================================================
and the output of lsusb in the domU:
======================================================================
Bus 001 Device 002: ID 03f0:0125 Hewlett-Packard
Bus 001 Device 001: ID 0000:0000
======================================================================
What other information can I provide?

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Problem passing a HP-DAT (USB) device to domU (fwd) (this time with outputs!), Matthias Wolf <=