thanks for the quick reply.
On Mon, 2015-01-05 at 14:37 +0100, mikkel@xxxxxxxxxxwrote:
Hi all, I have been running xen 3.4.1
You don't really mean 3.4.1 (released in 2009, 6 years ago) do you?
Given your use of xl I suspect you probably meant 4.3.1.
Sorry, you are of course right 4.3.1
on debian 7.3 for some time and it is stable and working for my purpose. Every now and then I have to shut the system down, and bring it up again. The latter is my pain, because I have to remember to add my pcie devices manually in regards to passing them through. The way I hide the devices is via: /etc/initramfs-tools/modules xen-pciback passthrough=1 hide=(00:1d.0)(00:1c.4)(02:00.0)(03:00.0)(03:01.0) perviously I also entered xen-pciback hide in GRUB, but that made no difference so I stuck to only editing modules GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT="xen-pciback.hide=(00:1d.0)(00:1c.4)(02:00.0)(03:00.0)(03:01.0)"
Is the module loaded and does /sys/modules/xen-pciback exist? Does the
parameters directory under there contain a hide file with the expected
contents?
Yes, both exist.
Never knew to look there. The file does contain devices, but not the sub devices.
I have also black-listed relevant kernel modules which could try to connect but only using xl will make the devices available for the DomU $ xl pci-assignable-add (00:1d.0) I cannot figure out why it does not work for all devices. I am thinking about scripting my way out of the, but maybe I am missing something?
xl -vvv pci-assignable-add might print what the old driver was, or you
can look for the driver symlink in the device's sysfs directory.
Ian.
$ xl -vvv pci-assignable-add 06:00.2
libxl: debug: libxl_pci.c:434:sysfs_dev_unbind: Driver re-plug path: /sys/bus/pci/drivers/ohci_hcd
xc: debug: hypercall buffer: total allocations:6 total releases:6
xc: debug: hypercall buffer: current allocations:0 maximum allocations:1
xc: debug: hypercall buffer: cache current size:1
xc: debug: hypercall buffer: cache hits:5 misses:1 toobig:0
I don't know if this gives me anything new, but then again black-listing ohci_hcd does not work. Maybe this is the reason?
Googling has unfortunately now given me any new insight. cheers for any input Mik _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
