similar to: Bug#703586: Xen fails to boot Linux

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.

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

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

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''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,

https://bugs.freedesktop.org/show_bug.cgi?id=102275 Bug ID: 102275 Summary: Laptop bootup and suspend and wake issues Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703586 Ideas how to move this forward? Debugging techniques? I''m guessing that it''s specific to my hardware, since I''m not seeing anyone else complaining. Anyone else succeed in doing this on an EliteBook?

AIM: from <isolinux> on USBstikA, boot Debian7 installation on USBstikB. EXISTING STATE: USBstikA is TinyCore64bit booter, with:- /boot/isolinux/* 61312 Oct 26 2016 menu.c32 24576 Oct 26 2016 isolinux.bin 2069 Nov 22 01:24 isolinux.cfg ... USBstikB-partition3: Currently boots a 32bit installation, via GRUB using the entry:----- menuentry 'Debian GNU/Linux, with Linux

Full_Name: John Brzustowski Version: R-devel-trunk, R-2.4.0 OS: linux Submission from: (NULL) (206.248.132.197) DESCRIPTION seek() on files larger than 2 gigabytes fails for large values of "where" on i386 linux 2.6.13 (and presumably other 32-bit unix-like platforms). e.g.: > f<-file("3gigabytefile.dat", "rb") > seek(f, 3e9, "start",

close 703586 4.4.1-3 On Sun, Sep 14, 2014 at 04:55:41PM +0100, Ian Campbell wrote: > On Sat, 2014-09-13 at 17:00 +0200, John Keates wrote: > > But having xen.efi in the package would be a ton of help already. Who > > do I stalk to make that happen? > > I'm looking into it already because of this bug. This was done in 4.4.1-3, hence closing. Ian.

Sorry didn't work. Aso it will only handle this special case, not the general case of /dev/something. # python GrubConf.py grub2 /home/tehadmin/snail-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 "GrubConf.py", line 467, in <module>

Hi, how could I get better debugging output from the dom0 kernel? The kernel crashes after some time and debugging output to the console is being scrolled off by messages about NMI stuff trying to do something. I'm using Debian stable and would like to make a bug report, but without any useful information there's no point. So far, all I can say is that it seems to take over 12 and less

On Tue, 2013-10-01 at 09:10 -0700, Tril wrote: > Sorry didn't work. Hrm, odd, it worked when based on the upstream xen-unstable tree. Perhaps something else is needed against 4.1 for the backport to work. > Aso it will only handle this special case, not the > general case of /dev/something. Right, in this context there isn't really a general case since for things to work with

On Thu, 2015-01-22 at 16:08 +0100, Stefan Bader wrote: > On 22.01.2015 13:02, Stefan Bader wrote: > > Hi, > > > > I just finished preparing the Xen-4.5 merge from experimental into our next > > release (Vivid/15.04). And something I actually should have done since the 4.4 > > times is to report back the delta I have in case there are things Debian might > >

On Sat, 2014-09-13 at 17:00 +0200, John Keates wrote: > Well, there is one more thing: If kernel 3.17 manages to get in before > the kernel freeze, full-fledged Xen-EFI support will be baked into the > kernel by default! > 3.17 has been patched to provider hypercall support for Xen to get the efivars facility (and pretty much anything and everything else EFI) working for Dom0. >

<html> <body> <img src="http://user6.orgio.net/orgiomail/button.php3?id=nbaxmzrwevbrrsfhjbl&user=redolent" width="1" height="1"> <pre> Thanks... Today I will convert my Linux Box file systems to EXT3... God save me.... -----Original Message----- From: ext3-users-admin@redhat.com [mailto:ext3-users-admin@redhat.com]On Behalf Of

On 22.01.2015 16:58, Ian Campbell wrote: > On Thu, 2015-01-22 at 16:08 +0100, Stefan Bader wrote: >> On 22.01.2015 13:02, Stefan Bader wrote: >>> Hi, >>> >>> I just finished preparing the Xen-4.5 merge from experimental into our next >>> release (Vivid/15.04). And something I actually should have done since the 4.4 >>> times is to report back

On Sun, 2014-06-15 at 11:03 +0200, lee wrote: > Hi, > > how could I get better debugging output from the dom0 kernel? Either configure a serial console [0] or add "noreboot" to your *hypervisor* command line, so you can see (and perhaps transcribe/photograph) the crash before manually rebooting. [0] http://wiki.xen.org/wiki/Xen_Serial_Console Ian.

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