All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Wolf <matthias.wolf@wot.at>
To: xen-devel@lists.xensource.com
Subject: Problem passing a HP-DAT (USB) device to domU
Date: Wed, 08 Aug 2007 00:31:36 +0200	[thread overview]
Message-ID: <46B8F2C8.3080804@wot.at> (raw)

Hi specialists,

I'm trying to pass a HP Surestore USB-drive to a domU. I'm hiding the 
pci-device in the dom0, capturing it in the domU, and rceive 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.
=======================================================================

I'm not quite sure what I'm expected to do 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).

I kind of *need* this functionality and would 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!

             reply	other threads:[~2007-08-07 22:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07 22:31 Matthias Wolf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-08-07 22:35 Problem passing a HP-DAT (USB) device to domU Matthias Wolf
2007-08-07 22:28 Matthias Wolf
2007-08-18  9:59 ` Keir Fraser
2007-08-23 17:07   ` Matthias Wolf
2007-08-24 14:38     ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46B8F2C8.3080804@wot.at \
    --to=matthias.wolf@wot.at \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.