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-users

[Xen-users] PCI device access and debugging output

To: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] PCI device access and debugging output
From: Lee Azzarello <lee.azzarello@xxxxxxxxxxxxx>
Date: Tue, 12 Jul 2005 15:47:12 -0400
Delivery-date: Tue, 12 Jul 2005 19:45:55 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Progressive Solutions
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello all. I've reached a problem I haven't found in the docs or on the
user's list. I have a Zapata Telephony FXO interface in a PCI card. I
would like an unprivleged domain to have access to it. I hid the device
from Domain 0 like so:
(without the line wrap)
kernel          /boot/xen.gz dom0_mem=128000
physdev_dom0_hide='(00:06.0)'

Domain 0 forgot about it and I told vm 1 about the same device in its
configuration file:
pci = [ '00,06,00' ]

When I boot vm 1, I see this in the xend log:
[2005-07-12 14:44:52 xend] DEBUG (XendDomainInfo:1178) Creating pci
device dom=3 bus=0 dev=6 func=0

I built the device driver in Domain 0 against the kernel source for
xen-U and the driver loads and claims to see the card. But the
application I need to access it claims it can't open the device.

Before I go to the application developer (Asterisk, if you're
interested), I want to confirm that my xen-U domain really does know
about the device and the driver is being properly loaded. How would I do
this beyond the output I pasted above? Is there any way at all?
 
Thanks for any help you can offer.

-- 
Lee Azzarello
Network Engineer
Progressive Solutions
+1 212 937 8939


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

<Prev in Thread] Current Thread [Next in Thread>