similar to: Kernel updates do not boot - always boots oldest kernel

OK, found out the problem as to why it doesn't boot any kernel except 36.2 the system reports that it cannot find vmlinuz-3.10.0-1160.88.1.el7.x86_64 or any one of the others, except for vmlinuz-3.10.0-1160.36.2.el7.x86_64 hence a manual selection from the grub menu when in front of the machine will only load the 36.2 kernel I found that under /boot/grub2 there were two .rpmnew files

Change it to GRUB_DEFAULT=0 (I encountered the same issue week ago with a workstation booted for three month with an older kernel because of https://bugzilla.redhat.com/show_bug.cgi?id=2143438 , and solved it this way) Regards, Petko On 3/14/23 10:51, Rob Kampen wrote: > Can I edit /etc/default/grub and change > > GRUB_DEFAULT=saved > > to something else? -- Petko Alov

Am 14.03.23 um 12:30 schrieb Rob Kampen: > OK, > > found out the problem as to why it doesn't boot any kernel except 36.2 > > the system reports that it cannot find > > vmlinuz-3.10.0-1160.88.1.el7.x86_64 > > or any one of the others, except for vmlinuz-3.10.0-1160.36.2.el7.x86_64 > > hence a manual selection from the grub menu when in front of the machine

> > On 2022-11-08 15:49, Orion Poplawski wrote: > > On 11/8/22 13:12, Simon Matter wrote: > > Is anyone else experiencing trouble with > kernel-3.10.0-1160.80.1.el7.x86_64? > > I'm seeing a kernel panics in the kvm module on one of our VM hosts with > > it. > > I did notice a new libvirt

Has this been solved? Is there a bug report I can follow? Thank you for letting me know, Val?re Binet On Wed, Nov 16, 2022 at 2:23 PM Bill Gee <bgee at campercaver.net> wrote: > On the other hand --- I just upgraded one of my CentOS7 systems to > 3.10.0-1160.80.1 today. With that kernel it will not run any KVM guest. > The system hangs - HARD - within one or two seconds of

This grub.cfg from a default fedora 19 Beta install caused pygrub failures.The previous pygrub commit fixed taht. So this example file added for reference. Signed-off-by: Marcel Mol <marcel@mesa.nl> --- tools/pygrub/examples/fedora-19.grub2 | 117 +++++++++++++++++++++++++++++++++ 1 files changed, 117 insertions(+), 0 deletions(-) create mode 100644 tools/pygrub/examples/fedora-19.grub2

> > > > I have only changed GRUB_DEFAULT from "saved" to "0" > > > > I have also run > > > > /usr/sbin/grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg > > I may be wrong here but IIRC, using grub2-mkconfig as described in the > Grub docs didn't work for me when I tried to use it years ago. > > I think you have to find out

I''m trying to run Xen on Arch Linux with UEFI boot. I followed the steps for Xen in the Arch Linux Wiki https://wiki.archlinux.org/index.php/Xen I get the following when attempting to boot: Loading Xen 4.2.2 ... WARNING: no console will be available to the OS Loading Linux linux ... Loading initial ramdisk ... Unfortunately there is no console so I cannot determine what has gone wrong,

You get these if you install Debian Wheezy as HVM and then try to convert to PV. This is Debian bug #603391. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Tested-by: Tril <tril@metapipe.net> --- tools/pygrub/examples/debian-wheezy-hvm.grub2 | 104 +++++++++++++++++++++++++ tools/pygrub/src/GrubConf.py | 6 +- 2 files changed, 109 insertions(+), 1

On 02/01/2018 12:15 PM, wwp wrote: > Hello there, > > > Dell XPS-15-9560 laptop (SSD drive, UEFI, secure boot off).. Windows 10 > pre-installed, CentOS7 installed in a separate partition and running > for months w/o issue. Don't know what happened but at reboot yesterday > (not even booted in Windows, just rebooted), grub has disappeared, > booted in Windows by

Confirmed this issue. To reproduce: Install a fresh Wheezy AMD64 guest under Xen 4.1 (hypervirtualized, boot from the debian-7.1.0-amd64-CD-1.iso). Use "entire disk" automatic layout for partitioning, this creates /dev/xvda1 for / and /dev/xvda5 for swap. It will create /boot/grub/grub.cfg with many references to (/dev/xvda,msdos1) which works fine when the machine is booted

On Sat, 2013-09-28 at 20:59 -0700, Tril wrote: > Backtrace from manual run of the buggy GrubConf.py: > # python /usr/lib/xen-4.1/lib/python/grub/GrubConf.py grub2 grub.cfg > WARNING:root:Unknown directive load_video > WARNING:root:Unknown directive terminal_output > WARNING:root:Unknown image directive load_video > Traceback (most recent call last): > File

Hello there, Dell XPS-15-9560 laptop (SSD drive, UEFI, secure boot off).. Windows 10 pre-installed, CentOS7 installed in a separate partition and running for months w/o issue. Don't know what happened but at reboot yesterday (not even booted in Windows, just rebooted), grub has disappeared, booted in Windows by default, which apparently has taken over the UEFI boot. By booting from a USB

Hello CentOS users, in the recent time I keep getting the logwatch warnings from my 2 dedicated servers running CentOS 7.4.1708. I guess because of the numerous kernel updates (because of Spectre+Meltdown) in the near past? Could someone please suggest me, which files in my /boot partition would be safe to delete? I would like to avoid the situation of having to boot the rescue partiton etc.

On Fri, 2020-07-31 at 22:35 +1200, Alan McRae via CentOS wrote: > I am running an Intel x64 machine using UEFI to boot an SSD. > > Installing the latest yum update which includes grub2 and kernel > 4.18.0-193.14.2.el8_2.x86_64 renders the machine unbootable, blank > screen where grub should be, no error messages, just hangs. > > After some hours I managed to modify another

Once upon a time, isdtor <isdtor at gmail.com> said: > We have a working PXE setup. I've tried to adapt it to UEFI as per > RHEL6 manual, but the client won't boot. I have BIOS+UEFI PXE boot set up, although it took some doing. I still use SYSLINUX for BIOS, but GRUB2 plus Red Hat's secure boot shim for UEFI. I never could get SYSLINUX's UEFI support working very

I have tried 4 time unsuccessfully to install Xen 4 on Ubuntu Lucid (10.4) 64 bit version using the tutorial at http://bderzhavets.wordpress.com/2010/04/24/set-up-ubuntu-10-04-server-pv-domu-at-xen-4-0-dom0-pvops-2-6-32-10-kernel-dom0-on-top-of-ubuntu-10-04-server/ on a Lenovo thinkcentre workstation. When I boot I get a kernel panic. If I boot the Linux kernel that I compiled using the

Booting a fedora 19 domU failed because a it could not properly parse the grub.cfg file. This was cased by set default="${next_entry}" This statement actually is within an ''if'' statement, so maybe it would be better to skip code within if/fi blocks... But this patch seems to work fine. --- tools/pygrub/src/GrubConf.py | 2 ++ 1 files changed, 2 insertions(+), 0

On Tuesday 28 May 2019 19:52:02 Jonathan Billings wrote: > I suggest running 'blkid' and 'efibootmgr -v', and double-check that > the UUID for the CentOS boot entry matches the UUID of the EFI disk. > > You can delete and recreate the boot entry with 'efibootmgr', which > will likely solve the problem. > > It depends on the UEFI implementation, but

Hello, I have installed the Xen 4.1.1 and a working kernel 2.6.32.43 which supports Xen on a Ubuntu Linux 10.04 LTS. However, I have never successfully booted the Hypervisor and Dom0. The screen is always black after some kernel messages rapidly go by. I think that I may pass the wrong parameters to the kernel or Hypervisor with GRUB2. Can any one share his/her working grub.cfg for GRUB2 with