Re: [Xen-devel] domU guest for xcp 0.1.1

[Ritu kaur <ritu.kaur.us@xxxxxxxxx>]

The NIC will remain bound to the pciback driver until you explicitly
unbind it and rebind to another driver in domain 0 and won't be
available until you do this. You can rebind the driver echo'ing the PCI
BDF of the device into the "unbind" and "bind" nodes under the
appropriate drivers in sysfs. e.g. for pcidev=0000:00:08.0:

echo -n "$pcidev" > /sys/bus/pci/devices/"$pcidev"/driver/unbind
echo -n "$pcidev" > /sys/bus/pci/drivers/$mydriver/bind

Hi Ian,

Currently, I have to reboot dom0 when I use

xe vm-param-set uuid=<vm-uuid> other-config:pci=<pci-bfd>  for pci passthrough. 

I looked at above bind/unbind files and they are present in /sys/bus/pci/drivers/<driver_name>/. Currently my driver is not loaded in dom0(not intended to load in dom0 due to passthrough) so I don't think I need to unbind. I did echo -n $pcidev > /sys/bus/pci/drivers/pciback/bind and I get

-bash: echo: write error: No such device

Currently, only way passthrough is enabled in domU is reboot of dom0 and domU after xe vm-param-set...

Kindly let me know if there is a way to avoid reboot.

Thanks


 

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