https://bugzilla.novell.com/show_bug.cgi?id=859361 https://bugzilla.novell.com/show_bug.cgi?id=859361#c4 --- Comment #4 from Michael Chang <mchang@suse.com> 2014-02-07 08:26:26 UTC --- (In reply to comment #2)
And I wonder why /etc/grub.d/20_linux_xen exists at all. All the work must be done in /etc/grub.d/10_linux. If a given vmlinu* is capable of being a dom0 then /boot/xen.gz must be added. If its pvops then perhaps the given file should be offered as native and (if xen.gz exists) also as dom0.
The 20_linux_xen is to group xen dom0 kernels (be it xenlinux kernel or pvops) in a submenu and boot the hypervisor (mainly with the multiboot protocol) with them. The 10_linux is used to group native or domU kernels bookable by linux stanza. The problem could be in 10_linux that trying to boot xenlinux kernel, I remember we had similar bug report in openSUSE and no idea why the regression happens so far. By the way, how to tell native, xenlinux and pvops kernel ? Is there any kernel configs could use ?
Also, /boot/xen.gz is written again as /boot/xen-dbg-4.4.0_03-301.2.gz. which will break once xen.rpm is updated.
This also sounds familiar .. :( -- 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.