search for: uefi

I installed my first UEFI disk yesterday. Seemed to go fine. CentOS 7.6 x86_64 I then took that disk "out" of that machine and put it another machine - it seems to not even boot. I put the original disk back in that machine and it boots fine. I put the UEFI disk back in the machine I built it on and it works fine...

Commit 889386f8c6088e57fd68f2bb6bf85f69ecfc6f6c removed most of them already, so remove the last ones, and the supporting code. --- generator/UEFI.ml | 6 ------ v2v/utils.ml | 1 - 2 files changed, 7 deletions(-) diff --git a/generator/UEFI.ml b/generator/UEFI.ml index 5161e28ee..1ff3f84d2 100644 --- a/generator/UEFI.ml +++ b/generator/UEFI.ml @@ -30,12 +30,6 @@ open Docstrings (* Order is significant *within architectures only*. *)...

Are UEFI clients still not possible on 8.1 ? I was looking for a setup in the GUI and dont see it. Searching "suggests" that --boot-uefi may be a command line option - but again I see nothing on the GUI. Thanks Jerry

This was only used inside the library, so move it there. --- .gitignore | 2 +- common/utils/Makefile.am | 4 +--- common/utils/guestfs-internal-frontend.h | 12 ------------ docs/C_SOURCE_FILES | 2 +- generator/UEFI.ml | 3 ++- generator/main.ml | 2 +- lib/Makefile.am | 3 ++- lib/appliance-uefi.c | 2 +- lib/guestfs-internal.h | 12 ++++++++++++ 9 files changed, 21 insertions(+), 21 deletions(-)...

...roving the isohybrid wiki > and will watch for pointers to descriptions of the FAT > production process (with GRUB/GRUB2 if not with SYSLINUX). > > If no such descriptions appear within the next weeks, > then i plan to state in > http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI > > "The SYSLINUX project cannot yet provide a FAT filesystem > image which would work with the isohybrid feature. > Known isohybrid ISOs for UEFI employ FAT images which > contain software from bootloader projects GRUB or GRUB2. > This software boots by own non-SYSLINUX...

...e: > > This could be misinterpreted by some users as: "if > > you want to build an isohybrid image, then you cannot use > > 'syslinux.efi'". This would be incorrect. > > I don't know whether syslinux.efi can be used for booting > from ISO 9660 via UEFI. Currently there is no example > around which would succeed without GRUB or GRUB2. I don't know how many times I have to express this and in how many different ways: 'syslinux.efi v.6.03 cannot be used for booting from ISO9660 via UEFI. Can 'syslinux.efi' be included in an i...

hello every body, I'm trying to build an isohybrid image based on syslinux able to boot on bios and uefi with optical disk or usb key. I've build a 16Mb hard disk image (core.img) with necessary parts for bios (legacy bootable partition, protective mbr, gptmbr.bin & syslinux installation) and for uefi (gpt, esp, /efi/boot/bootx64.efi & syslinux files). my hard disk image is ok - eg. boot...

Not all UEFI guests can survive conversion, because of lost bootloader information in UEFI NVRAM. But some guest can cope with this because they have a fallback bootloader and use UEFI Removable Media Boot Behavior. (see https://uefi.org/sites/default/files/resources/UEFI_Spec_2_8_A_Feb14.pdf 3.5.1.1 Removable...

Hi, Ok, when can we then anticipate pxe-chaining to be possible with syslinux under the UEFI architecture? Are there any plans to implement both correct interfacing to UEFI as well as the issue of arbitrary UEFI images? Haven't tried to read the UEFI-specification as it is sub 3000-pages long, so I am a bit in the dark as to the changes in architecture from BIOS to UEFI. It has been &q...

https://bugzilla.redhat.com/show_bug.cgi?id=1338083 Now that UEFI is fully open source the UEFI firmware can be included in Fedora. The location will be slightly different. These patches do a bit of code rearrangement and add the new paths. Rich.

v2: Rich, I hope I've done all modifications according to your comments, namely: * moved the code from linux_bootloaders to convert_linux * made minor code modifications --- Not all UEFI guests can survive conversion, because of lost bootloader information in UEFI NVRAM. But some guest can cope with this because they have a fallback bootloader and use UEFI Removable Media Boot Behavior to load (see https://uefi.org/sites/default/files/resources/UEFI_Spec_2_8_A_Feb14.pdf 3.5.1.1 Rem...

...suggestion is usually ignored by almost everyone, > >but if we are troubleshooting... > > Tried with more and less than 30 MB without impatc. > Aligned: could you give me an example of how you would create it with dd > ? Not exactly, but see below. > > >_ Creating a UEFI-boot-only image... > > I can try that indeed. Don't think it's creating an impact as I do see > the bootable VFAT32 part of my media and can navigate to it. I'm not sure what exactly you mean by "can navigate to it". Do you mean that from the EFI shell you can r...

Hi, Ady wrote: > the UEFI specs do state that the ESP is supposed > to be set/used as no-emulation mode > ... > the UEFI specs should tolerate / accept this situation, rather than < restricting the ESP to no-emulation mode. My criticism towards this UEFI implementation is that it probably cannot serve as real...

...3 at 08:43 -0500, Gene Cumm via Syslinux wrote: > On Thu, Dec 15, 2016 at 2:59 PM, Robin Mathews (robimath) via > Syslinux > <syslinux at zytor.com> wrote: > > > > Hi Folks , > > > > Can you please let me know if there is any fix for chain > > loading??UEFI boot loader using chain.c32??in 6.04 release ? > > I am booting my system with syslinux.efi and want to chain load to > > windows or sex specific boot loader in the second stage??. > chain.c32 has a lot of BIOS-isms and probably isn't worth modifying. > I believe none of the c...

I checked and secure boot is turned off. Jonathan brings it exactly to the point: we have to face UEFI because legacy mode is fading out, if I enable legacy mode I can't even boot anymore through the network (PXE) as these newer network cards can only boot PXE with UEFI. In the mean time I have installed Ubuntu 17.10 with Xen and I was lucky to see that this combination works with UEFI even Xen...

Hi, ________________________________________ From: Gene Cumm <gene.cumm at gmail.com> Sent: Wednesday, March 16, 2016 00:56 To: Jan Frode J?ger Cc: syslinux at zytor.com Subject: Re: [syslinux] Updated status on UEFI compliant version of the pxechn-module On Tue, Mar 15, 2016 at 9:32 AM, Jan Frode J?ger <jan.frode.jaeger at ntnu.no> wrote: Without trying to figure out where data is stored or the possibility of calls to manipulate the data, I can't speak for the possibility of implementing anything t...

Hi Ady, Ady Ady via Syslinux wrote: > > To me, it is not so clear what exactly is your goal. sorry for not being detailed enough. > Do you want to build an image for an internal HDD that could be capable > of booting in both, BIOS mode and UEFI mode? Yes. This would make us independent from the BIOS boot mode. > Or, is this for a portable (USB) device? Maybe - would be nice if this would work, but not required. > Or, is this for some kind of ISO image? No. > Or, is this for some kind of network-booting, in order to install O...

Hi, I have browsed through your syslinux archives and see that the issue of an UEFI compliant version of the pxechn-module has come up several times: http://www.syslinux.org/archives/2014-August/022611.html http://www.syslinux.org/archives/2015-March/023320.html http://www.syslinux.org/archives/2015-September/024231.html Now the issue as I understand it is that the original...

...me; hopefully some of these PXELINUX experts have seen this before. And can tell me what I'm doing wrong. Or confirm my suspicions. I have a test lab server at work. Split config. The network team manages the DHCP servers, points to our TFTP server. Test subnet has 3 DHCP pools. BIOS PXE, UEFI PXE and catch-all (straight DHCP). DHCP server is filtering on client's initial VCI (option 60). PXEClient:Arch:00000* => BIOS PXE boot client PXEClient:Arch:00007* => UEFI PXE boot client empty => std DHCP request This is all working correctly. Based on the OFFERed DHCP ad...

First version was posted here: https://www.redhat.com/archives/libguestfs/2016-August/thread.html#00100 This is semantically the same as the first version. However I've split the patch up into two parts. In the first part, I factor out the UEFI paths so now they are created by the generator and written in the library and v2v/ directory directly, instead of the complex business of having a C database which is read in virt-v2v using C bindings. The second part is the same as before (but simplified because it now needs fewer changes). Rich...