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

Re: [Xen-users] Uninitialized hardware under Xen Client?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Uninitialized hardware under Xen Client?
From: Andy Burns <lists.xensource.com@xxxxxxxxxxxxxx>
Date: Sat, 05 Jul 2008 09:15:34 +0100
Delivery-date: Sat, 05 Jul 2008 01:16:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <486F28BE.1000504@xxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <486F28BE.1000504@xxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.14) Gecko/20080421 Lightning/0.8 Thunderbird/2.0.0.14 Mnenhy/0.7.5.0
On 05/07/2008 08:54, Kenneth Andresen wrote:

I would like to know if a
Xen client can use Firewire without it being supported by the host system?

lspci is listing the firewire as:
07:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
Controller (rev c0)

Yes, you can use pciback and pcifront to pass the device from dom0 into a domU, where you can install a different kernel that does support the device.

the centos 5.2 xen kernels are built with pciback/pcifront, other distro xen kernels may vary.

On the dom0, in /etc/modprobe.conf add this (beware of line-wrapping on the install line)

options pciback hide=(0000:07:03.0)
install XXXXXX /sbin/modprobe pciback ; /sbin/modprobe --first-time --ignore-install XXXXXX

where XXXXXX is the driver which would normally load the device, essentially what it does is say where you'd normally load the driver for XXX, load pciback instead.

If the dom0 kernel doesn't have a driver for XXXXXX, then you can do it this way instead, but it will be required each boot so put it in /etc/rc.local or similar.

modprobe pciback
echo -n 0000:07:03.0 > /sys/bus/pci/drivers/pciback/new_slot
echo -n 0000:07:03.0 > /sys/bus/pci/drivers/pciback/bind


You will need to use the xmdomain.cfg style config file for your domU not a libvirt xml stykle config, you can then add the pci device

with a line e.g

pci = ['07:03.0']

When you boot the domU, it should the show the passthrough device with an lspci, and you can modprobe drivers for it if they aren't done automatically

You may need to use pollirq kernel parameter on dom0 if the device shares interrupts with other devices.

You may need swoitlb parameters to xen itself, or domU kernel if it does DMA transfers.



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

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