similar to: UEFI boot - no console will be available to OS

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

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

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

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 Tue, 9 Oct 2018 at 21:47, Yves Bellefeuille <yan at storm.ca> wrote: > > I had CentOS 6 installed on an MBR hard disk. I converted the disk to > GPT (with UEFI) and installed CentOS 7 on a new partition. > Was CentOS6 bootable after you converted the disk to GPT? My luck with getting it to work has not been good as the conversion usually changes something very important to

I had CentOS 6 installed on an MBR hard disk. I converted the disk to GPT (with UEFI) and installed CentOS 7 on a new partition. CentOS 7 itself seems to work properly. Grub from CentOS 7 automatically created an entry for CentOS 6, but I get an error if I try to boot CentOS 6. The menu entry is: menuentry 'CentOS release 6.10 (Final) (on /dev/sda7)' --class gnu-linux --class gnu

I''m running Xen 4.1 (4.1.3-3ubuntu1.3) on an Ubuntu 12.10 server with an AMD FX-8150 processor (8 cores) and 16 GB of RAM. When I boot the server, Xen sees only 3 GB of RAM (instead of 16 GB). If I try to create a domU with more than about 1.5 GB of RAM, the create fails with messages saying it "could not allocate memory for HVM guest". Here''s the output when I do

Hi all. I''ve got a situation with Fedora 18 on a dual Xeon E5506 box, 16GB RAM, Tyan S7002 motherboard with the latest BIOS. Because of all the issues, I''m starting to think maybe there''s something wrong with the box itself, maybe something strange going on with the BIOS or mobo resources. Although this box was in service without incident for about 2 years prior. I

The error occurred while evaluating nil.prefetch_primary_key? Hi, I have a problem with a model when I have 3 belongs_to relations in one the middle. This example is a subset of a grid-routing project: n 1 1 n +------------ Project Connection ------- ConnectionCost +------------ WaySearchRun

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

On 10/12/14 18:13, Jeff Boyce wrote: > Greetings - > > The short story is that got my new install completed with the > partitioning I wanted and using software raid, but after a reboot I > ended up with a grub prompt, and do not appear to have a grub.cfg file. > So here is a little history of how I got here, because I know in order > for anyone to help me they would

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

Greetings - The short story is that got my new install completed with the partitioning I wanted and using software raid, but after a reboot I ended up with a grub prompt, and do not appear to have a grub.cfg file. So here is a little history of how I got here, because I know in order for anyone to help me they would subsequently ask for this information. So this post is a little long, but

This is my /proc/cmdline BOOT_IMAGE=(hd0,gpt2)/boot/vmlinuz-4.18.0-147.5.1.el8_1.x86_64 root=UUID=c1bef884-0180-4955-a669-c99a8c64f75a ro crashkernel=auto resume=UUID=0fe1a972-9912-4803-b5ec-265a13a888c1 biosdevname=0 net.ifnames=0 rhgb quiet rd.driver. blacklist=nouveau nomodeset nouveau.modeset=0 acpi_backlight=vendor "acpi_osi=!Windows 2013" "acpi_osi=!Windows 2012" Jerry

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

Hi All, I have a Dell R710 that has 6x1TB in a RAID-5 configuration. When installing CentOS 7 using the full disk capacity and booting in UEFI mode the machine dumps me into a GRUB rescue mode prompt. error: disk `,gpt2' not found Entering rescue mode... grub rescue> If I use the PERC RAID controller to make the disk smaller ROOTDISK volume of 100GB in size and then a DATA volume

There is some interest lately in making a self-contained grub2 boot image - call it pvgrub2, used for booting paravirtual domU in xen where a grub2 config is installed. First attempt------------------ I first tried using the grub2*.src.rpm from the C7 vault. I configured as shown belowhttps://blog.xenproject.org/2015/01/07/using-grub-2-as-a-bootloader-for-xen-pv-guests/ for headers, I used

Hi folks, I have an existing CentOS 7.2 system, that I want to re-install. I copied /vmlinuz and /initrd.img into /boot, place my kickstart file into /boot, and created a grub2 menu entry for this, as follows: menuentry "Install CentOS 7" { insmod gzio insmod part_gpt insmod xfs set root=(hd0,2) linux /vmlinuz console=tty0 console=ttyS1,115200

On Thu, Aug 18, 2016 at 11:57 AM, James A. Peltier <jpeltier at sfu.ca> wrote: > Hi All, > > I have a Dell R710 that has 6x1TB in a RAID-5 configuration. This is hardware RAID 5? Because it's pretty screwy how this ends up working when using software RAID and might take additional troubleshooting. > When installing CentOS 7 using the full disk capacity and booting in