similar to: Changing EFI boot order via API

On 6/12/23 15:38, Lukas Zapletal wrote: > Hello, > > I would like to be able to change the boot order of an EFI VM via > libvirt API. Specifically, I am looking into configuring a VM to boot > over HTTP UEFI Boot or HTTPS UEFI Boot (also available as HTTP IPv4 in > the firmware). > > Is this possible? I cannot find anything relevant in the documentation. Thanks. > It

Hi, I'm trying to grant dovecot the ability to manage its socket within the postfix spool directory. I have added the below to file_contexts.local : /var/spool/postfix/private/dovecot-auth system_u:system_r:dovecot_t:s0 However, running "restorecon -v /var/spool/postfix/private/dovecot-auth" gives me the following error : restorecon:

Thanks for the pointer, will take a look down that route. Could you confirm the below is expected behaviour on Centos ? # semanage fcontext -a -t my_postfixauth_private_t "/var/spool/postfix/private(/.*)?" ValueError: Type my_postfixauth_private_t is invalid, must be a file or device type On 23 January 2017 at 19:06, Lukas Zapletal <lukas at zapletalovi.com> wrote: > Hello,

Hi! I'm working currently on integration of UEFI/SecureBoot support into oVirt. And I have several questions about UEFI/SecureBoot support in libvirt. Can you please help me with them? For UEFI I add the following to the XML: <loader readonly="yes" secure="no" type="pflash"> /usr/share/OVMF/OVMF_CODE.secboot.fd </loader> <nvram

Hi, currently syslinux fails to build from source in Debian as has been reported in https://bugs.debian.org/906414 . The reported error is: mbr.bin: too big (452 > 440) I've realized that this is because since a recent version, the linker adds a new section (.note.gnu.property). Discarding this section fixes the problem. I've attached a patch, please consider merging it. Thanks

On Fri, Aug 14, 2015 at 11:42 AM, Patrick Masotta via Syslinux <syslinux at zytor.com> wrote: >>>>> > website (meaning, HP could test their firmware to be compatible with > Syslinux and with non-Windows OSes). If the HP firmware could be made > (more) compliant with UEFI specs, or if it could be improved and still > be compliant with UEFI specs, wouldn't

On 2019-12-13 08:36, Gregory Lee Bartholomew via Syslinux wrote: > On Fri, 2019-12-13 at 08:47 +0100, jps--- via Syslinux wrote: >> Hi, >> >> We are currently testing PXE booting with syslinux.efi in UEFI mode. >> This is working fine. >> However the loading of syslinux.efi and the config files is still using >> TFTP protocol, the rest kernel and initrd is

Hi, We are currently testing PXE booting with syslinux.efi in UEFI mode. This is working fine. However the loading of syslinux.efi and the config files is still using TFTP protocol, the rest kernel and initrd is loaded using HTTP protocol. We would like to use only HTTP protocol. In UEFI it is possible to use HTTP boot instead off PXE boot. Questions: 1. If we load syslinux.efi with HTTP will

On Tue, 2018-12-18 at 14:10 -0500, Gene Cumm wrote: > On Wed, Dec 12, 2018 at 6:30 PM Joakim Tjernlund via Syslinux > <syslinux at zytor.com> wrote: > > On Wed, 2018-12-12 at 17:10 -0600, Carl Karsten wrote: > > > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is

Hi everyone, for UEFI bootable media I currently use preloader+gummiboot while on BIOS media I use isolinux/extlinux. Since maintaining two configurations is some kind of extra work, I plan switching to syslinux in the next weeks or months. Creating an UEFI boot partition or El-Torito image seems easy: Use preloader, hashtool and the syslinux efi file, copy them to the FAT image and be

On Tue, Jun 21, 2016 at 5:33 PM, H. Peter Anvin via Syslinux <syslinux at zytor.com> wrote: > On 06/18/16 03:50, Gene Cumm via Syslinux wrote: >> >> UEFI is very different. There's no option ROM nor PXE stack. >> Generally speaking, the underlying UEFI system has to get NIC drivers >> (commonly built-in) and initialize the network through a round of DHCP

Hi! I am currently trying upgrade my bios pxe server with additional uefi support. My current using memtest86+ doesn't seem to support uefi, so I would have to use memtest86, as it supports this. But the memtest86 file itself is an *.efi file. When booting this one directly without syslinux, its working. But I want to launch it later from the syslinux menu. Can I chainload somehow another

Hello, restorecon works only for existing files, for new files you are looking for file transition rule. Google that out, there is plenty of articles on that topic, for example: https://fedoraproject.org/wiki/Features/SELinuxFileNameTransition LZ 2017-01-23 19:57 GMT+01:00 Tim Smith <r.a.n.d.o.m.d.e.v.4+centos at gmail.com>: > Hi, > > I'm trying to grant dovecot the

> > Today there are certain PCs i.e Elitebook 2560p, Elitebook 8460p that with > updated FW ""to the last known version"" cannot PXE boot syslinux for the > above mentioned reasons. > > We have already talked about this with Gene an there's an strategy for making > syslinux able to deal with these "weirdo" FWs. > It's just a matter

On Sat, Jun 18, 2016 at 4:09 AM, Geert Stappers via Syslinux <syslinux at zytor.com> wrote: > On Fri, Jun 17, 2016 at 07:27:17PM -0500, Alexander Perlis via Syslinux wrote: >> Question: >> If syslinux.efi is loaded locally off USB rather than via an EFI >> PXE option ROM boot, but on a client whose EFI firmware has TCP >> support, should that locally-booted

On 11/28/2016 09:33 AM, Ady Ady via Syslinux wrote: > >> Hello, >> >> I am pxebooting a large linux kernel (with embedded initramfs) that is around >> 250 MB in size. >> >> When booting a board in legacy BIOS mode, the pxelinux.0 executable is >> transferred to the board and takes over, from where loading and booting this >> large kernel works as

>>> > It does contain a Net but there are 2 issues with SNP: > 1) The interface is different than UDPv4/TCPv4 protocols; this imply lot of code. Not as much as you may think.? We already have lwIP implemented into lpxelinux.0.? It's more a matter of using more glue. > 2) SNP has its non-blocking transmit issues ; see "Flaws in the design" at >

I'm looking for direction to install and boot CentOS 7 from an iSCSI device. Any experience and advice will be greatly appreciated. Thanks! Michael Duvall

Ady Ady via Syslinux wrote: > >> However, I have just tested the exact same boot procedure using a Dell >> laptop (Latitude 7480) - and it all worked without a problem - that is, >> syslinux.efi and ldlinux.e64 were downloaded without a problem - and >> from a tcpdump, there was *no* DHCP transaction between downloading >> syslinux.efi and ldlinux.e64 >>

I had to boot my HP Envy into Win8 for the first time in ages this morning. When I did that, it installed some updates including a BIOS update. Once this was all done, once again the GRUB boot menu was gone and it booted straight into Win8. Using the advanced boot manager options in Win8 I managed to get the EFI boot menu up and chose Ferdora 21. It was only after Fedora failed to boot that