[opensuse-kernel] Re: openSUSE Kernel Stable Repo
(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. Michal
Any idea? I am using openSUSE 13.2 (x86_64) with the above-mentioned repo enabled.
Thank you.
Best regards
Frank
-- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 11/23/2015 05:59 AM, Michal Marek wrote:
But grub2 should be smart enough to create a Xen entry iff Xen is available.
Fyi, I've an Opensuse instance on a hosted VM. The host's been recently migrated from Xen to KVM. The instance's kernel was upgraded prior to the migration to pv-ops kernel-default & grub2. Prior to the migration, Grub2 created a Xen entry, and the instance booted fine. Once migrated from Xen -> KVM, Xen's been removed from the instance completely grub2 still creates a Xen entry. A second, separate issue is that the generated grub NON-xen entry no longer boots without some workarounds; again, a separate issue. But grub2 still needs attention. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
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? 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. Cc Michael as author of grub2 patches. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
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. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
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
On Mon, Nov 23, 2015 at 09:38:46PM +0300, Andrei Borzenkov wrote:
23.11.2015 20:17, Michal Marek пишет:
On 2015-11-23 17:55, Andrei Borzenkov wrote:
23.11.2015 16:59, Michal Marek пишет:
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?
No, We can drop the hack completely. Let me do it. Thanks, Michael -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
participants (4)
-
Andrei Borzenkov -
Michael Chang -
Michal Marek -
PGNet Dev