23.11.2015 20:17, Michal Marek пишет:
On 2015-11-23 17:55, Andrei Borzenkov wrote:
23.11.2015 16:59, Michal Marek пишет:
(opensuse-kernel added)
On 2015-11-22 15:09, Frank Krüger wrote:
Hi there
FYI: After today's update to kernel 4.3.0-17.g6a48ac7-default x86_64, using the repo
http://download.opensuse.org/repositories/Kernel:/stable/standard/
I have an additional grub entry entitled "openSUSE GNU/Linux, mit Xen-Hypervisor", although there are no xen-packages installed at all.
So I guess the entry does not boot? We enabled CONFIG_XEN in the default so it is now used for both bare metal and Xen. But grub2 should be smart enough to create a Xen entry iff Xen is available.
Hmm ... our 20_linux_xen always adds "dummy" /boot/xen.gz if it finds Xen-dom0 enabled kernels (as workaround kernel being install before Xen itself). Xen enabled kernels are checked by one of CONFIG_XEN_DOM0=y or CONFIG_XEN_PRIVILEGED_GUEST=y. Does new kernel qualify?
Ah, there it comes from. Yes, we have CONFIG_XEN_DOM0=y in kernel-default now.
In this case I guess fix is to remove this hack and instead run bootloader update from Xen in addition to kernel. it should be performed just once as posttrans if I understand it correctly.
Yes please.
Actually Xen already runs update-bootloader in post. OK, it is not once per transaction but it is different topic. @Michael, is there any reason to keep this hack in grub2 now? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org