similar to: Xen EFI boot how to?

We found machines with >32 E820 memory map entries, where Xen fails to boot (but Linux does boot fine). The native Linux (both x86 and x86_86) already has: #define E820MAX 128 /* number of entries in E820MAP */ Signed-off-by: Jun Nakajima <jun.nakajima@intel.com> Jun --- Intel Open Source Technology Center -- diff -r 3bb1857981e6 -r 51e9c0c806b2 xen/include/asm-x86/e820.h ---

Hey, There has been some discussion about EFI and SecureBoot and such. Most of the time I get questions in the form of "How do I get Fedora 17 with Xen to do EFI", I am going to concentrate on Fedora, but I think this applies to other distros too. From my reading (I hadn't actually tried EFI yet), there are two ways to bootup a system: - Using grub2.efi. Grub2 does the EFI API

u.inuse.type_info is at the end of the pfn_info structure, and is u32 for both x86_32 and x86_64--in this location it can also be the last 32 bits of a page. several functions use bitopts.h functions to manipulate this member, and on x86_64 these functions use u64 instructions, which will overflow the page boundary, and possibly the end of memory as we see here: (XEN)

Hello All, updating from Centos7.3 to Centos7.4 rendered one of our laptops unbootable. EM: Failed to open \EFI\BOOT\grubx64.efi - Not Found Failed to load image \EFI\BOOT\grubx64.efi: Not Found start_image() returned Not Found How could this occur because of an update and how to fix this? What I tried is booting from centos usb, chroot to /mnt/sysimage and gave command: efibootmgr

----- Original Message ----- | On Fri, Aug 19, 2016 at 4:59 PM, James A. Peltier <jpeltier at sfu.ca> wrote: | > | > | > ----- Original Message ----- | > | 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. | > | | > | |

----- Oorspronkelijk bericht ----- Van: "Adrian Jenzer" <a.jenzer at herzogdemeuron.com> Aan: "CentOS mailing list" <centos at centos.org> Verzonden: Dinsdag 9 januari 2018 16:56:57 Onderwerp: Re: [CentOS] update to Centos7.4: Failed to open \EFI\BOOT\grubx64.efi - Not Found -----Original Message----- From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of

----- Original Message ----- | 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. Yes, it's a Dell R710XD |

Hi all - I'm not sure if it's appropriate to ask this here, but I don't see this question explicitly answered anywhere. Is there an EFI version of "pxelinux.0" that will function basically the same way and read the same pxelinux.cfg/default menu files? I've got a really dodgy grubx64.efi EFI PXE menu up at work, but it can't load the 1.2 gigabyte LiveCD that we use

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

On Mon, Feb 5, 2018 at 8:27 AM, Kay Diederichs <kay.diederichs at uni-konstanz.de> wrote: > grub-install /dev/nvme0n1 Running this on computers with UEFI firmware is not good advice, it's an obsolete command. People should use the prebaked grubx64.efi binary that comes in the grub2-efi package, and is a signed binary so it can support UEFI Secure Boot. If you run grub2-install, a

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 bootable partition (containing older software) and boot it from there. After that, I? found out

Hi, I am trying to get a UEFI bootable USB. And I am unable to make it working. I have two x86_64 systems and both of them 'hangs' when I choose to boot UEFI from USB. I've created fat32 formated partition with ef00 type. I placed EFI/BOOT there with content of efi64/ distribution, I've created syslinux.cfg and renamed syslinux.efi to BOOTX64.EFI. However, it does just

hi guys I've one box where I just yesterday upgraded Centos. I wonder if that kernel upgrade process might somewhat troublesome. After that upgrade UEFI boot fails with: Failed to set MokListRT: Invalid Parameter Something has gone seriously wrong: import_mok_state() failed : Invalid Parameter Has anybody seen that? And maybe know to fix it? many thanks, L.

Jan suggested a couple of cleanups based upon my "xen: allow architecture to choose whether to compress installed xen binary" patch. So this series now consists of: xen: allow architecture to choose how/whether to compress installed xen binary xen: x86: drop the ".gz" suffix when installing xen: Use $(T) and $(D) aliases in install target This is based

After updates to grub2 and kernel in CentOS 7, today, systems will no longer boot in Secure Boot mode. I'm not positive, but I think grub2 is the culprit. Is anyone else seeing the same problem?

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

This is a quick recovery and fix for the machines rendered unbootable after the grub2/shim yum update. It is written for CentOS 8.2.2004 but similar should work for any CentOS 8 or 7 as long as you get the correct shim file, that is, the one from the latest installation media. I am running on an x86_64 architecture (see uname -i). Please use the correct shim file for your architecture

On Sun, 2014-09-07 at 00:02 +0200, John Keates wrote: > How do I assist with getting this in for Jessie? > > I have this working in a fairly easy setup, it basically only requires > the pep target to be on for debian?s Xen package, What is "pep"? > and a tiny bit of infrastructure to get xen.efi, vmlinuz, an initrd > and a xen.cfg on to the ESP partition and letting

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

# HG changeset patch # User Matt Wilson <msw@amazon.com> # Date 1342481836 0 # Branch efi # Node ID dd1ab0cae2c870942c2e1b6bc3a507b1a40dae16 # Parent 9950f2dc2ee6dfd172258a5a4ee29809b0ff8263 x86/EFI: define and use EFI_DIR make variable, defaulting to /usr/lib64/efi After commit 25594:ad08cd8e7097, EFI Xen binaries were installed to /efi instead of /usr/lib64/efi. This patch restores the