[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] xen/next & pvm pci passthrough?


Does anyone know if pvm pci passthrough is supposed to work on xen/next 
branch? I'm trying to get a device passed to the pvm, but things don't work 
the same as on xen/master (where i used pciback).

Here's what i do on xen/master dom0:
echo -n "0000:05:00.0" > /sys/bus/pci/drivers/cx23885/unbind
echo -n "0000:05:00.0" > /sys/bus/pci/drivers/pciback/new_slot
echo -n "0000:05:00.0" > /sys/bus/pci/drivers/pciback/bind

Then when i boot the pvm using also xen/master kernel, it shows up on lspci, 
and i can load the driver.

But when i run xen/next dom0, pciback doesn't seem to exist, so i use pci-stub 
to grab the device:

lspci -n
05:00.0 0400: 14f1:8852 (rev 02)

echo -n "14f1 8852" > /sys/bus/pci/drivers/pci-stub/new_id
echo -n "0000:05:00.0" > /sys/bus/pci/drivers/cx23885/unbind
echo -n "0000:05:00.0" > /sys/bus/pci/drivers/pci-stub/bind

Now i boot the same pvm using xen/next kernel, however nothing shows up on 
lspci after the pvm is up.

Is this not working yet? Or am i just doing something wrong?

My config file is the same for both, and contains the following:

bootloader = "/usr/bin/pygrub"
maxmem = 1024
memory = 1024
name = "pvm"
vif = [ 'mac=aa:20:00:00:02:17, bridge=br0' ]
disk = [
pci = [


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.