https://bugzilla.novell.com/show_bug.cgi?id=450267 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450267#c25 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Xen |Basesystem AssignedTo|jbeulich@novell.com |hare@novell.com QAContact|jdouglas@novell.com |qa@suse.de --- Comment #25 from Jan Beulich <jbeulich@novell.com> 2009-02-04 02:49:46 MST --- DOMU_INITRD_MODULES is definitely not intended to be used standalone, but indeed the way /lib/mkinitrd/scripts/setup-start.sh sets RESOLVED_INITRD_MODULES seems wrong. I wonder how nobody else ran into that issue so far. It seems to be done better (but still not optimal) in SLE11 - there the construct says if is_xen_kernel $kernel_version; then RESOLVED_INITRD_MODULES="$modules $domu_modules" else RESOLVED_INITRD_MODULES="$modules" fi But in a DomU it could really just use $domu_modules, it's just that that case isn't being considered (perhaps because it depends on running mkinitrd inside the VM, whereas the current approach does not use this run-time characteristic - otoh, other run-time characteristics are being considered when constructing the module list, so that apparently is not the issue). -- 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.