[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] pci device not owned by pciback.
Hi James, What Xen version are you using? Are you using a pvops based kernel? Or a'classic' xen kernel based on 2.6.18+patches? Could you please answer this? It would help to know what your Xen andkernel are based on. Do you build your own Xen & kernel? Or are you using a Xen and kernel version provided by your distro? Yeah, it is not sufficient to unload only. You still have to assign the devices to pciback:I tried unloading mptspi and it unloads, but I still can't start the virtual machine assigned those cards. Same error as before:Error: pci: improper device assignment specified: pci: 0000:0e:04.0 must be co-assigned to the same guest with 0000:0e:04.0, but it is not owned by pciback. echo -n "0000:0e:04.0" > /sys/bus/pci/drivers/pciback/new_slot echo -n "0000:0e:04.1" > /sys/bus/pci/drivers/pciback/new_slot echo -n "0000:0e:04.0" > /sys/bus/pci/drivers/pciback/bind echo -n "0000:0e:04.1" > /sys/bus/pci/drivers/pciback/bind It does seem that way... or worse, perhaps your kernel doesn't have pciback at all... You can try to load it manually and then run the echo commands listed above.Unknown boot option `pciback.hide=(0e:04.0)(0e:04.1)': ignoring Unknown boot option `xen-pciback.hide=(0e:04.0)(0e:04.1)': ignoringDoes this mean it is not compiled in the kernel? That would really suck. What would my next step be? If you can't manually load pciback, and the echo commands above fail, then all i can think of is to try a different kernel... Regards, Mark. _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |