[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] what needs to be config'd to fix "Unknown boot option `pciback.permissive'"?
hi, on opensuse 11beta3plus w/ latest repo-available xen, rpm -qa | grep -i xen xen-doc-pdf-3.2.1_16881_01-11 kernel-xen-2.6.25.4-2 xen-3.2.1_16881_01-11 xen-libs-3.2.1_16881_01-11 xen-tools-3.2.1_16881_01-11 xen-doc-html-3.2.1_16881_01-11 xen-devel-3.2.1_16881_01-11 enabling PCI-passthrough "as usual", @ /boot/grub/menu.lst, ... physdev_dom0_hide=(##:##.#)(##:##.#) \ pciback.permissive \ pciback.hide=(##:##.#)(##:##.#) \ ... dmesg 'complains', Unknown boot option `pciback.permissive': ignoring Unknown boot option `pciback.hide=(00:14.0)(04:06.0)': ignoring reading, "5.3 Driver Domain Configuration" "5.3.1 PCI" "5.3.1.1 Compile-Time Setup" http://www.cl.cam.ac.uk/research/srg/netos/xen/readmes/user/ To use this functionality, ensure that the PCI Backend is compiled in to a privileged domain (e.g. domain 0) and that the domains which will be assigned PCI devices have the PCI Frontend compiled in. In XenLinux, the PCI Backend is available under the Xen configuration section while the PCI Frontend is under the architecture-specific "Bus Options" section. You may compile both the backend and the frontend into the same kernel; they will not affect each other. and checking, grep XEN_PCIDEV /usr/src/linux-2.6.25.3-2-obj/x86_64/xen/.config CONFIG_XEN_PCIDEV_FRONTEND=y # CONFIG_XEN_PCIDEV_FE_DEBUG is not set --> CONFIG_XEN_PCIDEV_BACKEND=m CONFIG_XEN_PCIDEV_BACKEND_VPCI=y # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set # CONFIG_XEN_PCIDEV_BE_DEBUG is not set note, CONFIG_XEN_PCIDEV_BACKEND=m is a module. (fwiw, this has been reported as a bug @opensuse, https://bugzilla.novell.com/show_bug.cgi?id=393379) so, next, i rebuild kernel-xen from src, with "de-modularized" xen, i.e @ 'menuconfig' setting, # SECTION XEN ------------------------------------------ [*] Privileged Guest (domain 0) <*> Backend driver support <*> Block-device backend driver <*> Block-device tap backend driver <*> Network-device backend driver [ ] Pipelined transmitter (DANGEROUS) <*> Network-device loopback driver <*> PCI-device backend driver PCI Backend Mode (Virtual PCI) ---> [*] PCI Backend Debugging <*> TPM-device backend driver <*> Block-device frontend driver <*> Network-device frontend driver <*> Network-device frontend driver acceleration for Solarflare NICs <*> User-space granted page access driver <*> Framebuffer-device frontend driver <*> Keyboard-device frontend driver [*] Xen virtual console [*] Scrub memory before freeing it to Xen [ ] Disable serial port drivers <*> Export Xen attributes in sysfs Xen version compatibility (3.0.4 and later) ---> ------------------------------------------ so as to compile-in xen 'stuff'. build seems OK, ls -alt /boot/*CUSTOM* -rw-r--r-- 1 root root 5254725 2008-05-23 07:51 /boot/initrd-2.6.25.4-2-xenCUSTOM -rw-r--r-- 1 root root 81915 2008-05-23 07:42 /boot/config-2.6.25.4-2-xenCUSTOM -rw-r--r-- 1 root root 1123251 2008-05-23 07:42 /boot/System.map-2.6.25.4-2-xenCUSTOM -rw-r--r-- 1 root root 2012154 2008-05-23 07:42 /boot/vmlinuz-2.6.25.4-2-xenCUSTOM after reboot to "vmlinuz-2.6.25.4-2-xenCUSTOM", Linux server 2.6.25.4-2-xenCUSTOM #1 SMP Wed May 21 16:33:54 PDT 2008 x86_64 x86_64 x86_64 GNU/Linux the "pciback.hide ..." is, apparently now OK, as dmesg now shows only, Unknown boot option `pciback.permissive': ignoring so, what needs to be done to recognize "pciback.permissive"? or, has it gone away when i wan't looking? thanks! _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |