https://bugzilla.novell.com/show_bug.cgi?id=393379 Summary: kernel-xen .config requires CONFIG_XEN_PCIDEV_BACKEND compiled-in, *not* as module Product: openSUSE 11.0 Version: Beta 3plus Platform: All OS/Version: All Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: schneecrash+opensuse@gmail.com QAContact: qa@suse.de Found By: --- installed opensuse-11/factory's kernel-xen, rpm -qa kernel-xen kernel-xen-2.6.25.4-2 @boot, grub-defined kernel-xen options for pci-passthrough fail. checking, dmesg reports, ... Kernel command line: root=/dev/v_0/l_root resume=/dev/v_0/l_swap showopts max_loop=64 physdev_dom0_hide=(##:##.#)(##:##.#) pciback.permissive pciback.hide=(##:##.#)(##:##.#) Unknown boot option `pciback.permissive': ignoring Unknown boot option `pciback.hide=(##:##.#)(##:##.#)': ignoring .... as per, "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. the pciback (CONFIG_XEN_PCIDEV_BACKEND) module must be compiled into the dom0 kernel, & the pcifront (CONFIG_XEN_PCIDEV_FRONTEND) module must be compiled into the domU kernel. or, if using a single/unified kernel-xen, then both must be compiled in. and, as you can see, in factory's kernel-xen .config, grep PCIDEV /boot/config-2.6.25.4-2-xen 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 that's not the case. to avoid that problem above, and any add'l module-vs-compile "surprises" i'm trying to "completely de-modularize" 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) ---> ------------------------------------------ also (haven't gotten there yet ...), build a dual-use kernel (Dom0 & DomU), which I think requires also, CONFIG_XEN_PRIVILEGED_GUEST=y --- # CONFIG_XEN_UNPRIVILEGED_GUEST is not set +++ CONFIG_XEN_UNPRIVILEGED_GUEST=y but 'make menuconfig' seems to not allow both, allowing one or the other ... investigating further. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.