similar to: EFI guest firmware for xen-ia64: where to put the sources ?

Hello, is there a way to start a efi-application (bios update tool) from syslinux ? best regards Johann

I have been using syslinux-6.x along with isohybrid --mac and --efi option to create a usb hybrid iso with EFI support. The thing with EFI is that you'll need to use grub as your bootloader for EFI but isohybrid does setup the proper partition schema for EFI. You'll need to use the following to generate an iso that works. xorriso -as mkisofs -J -R -l -V some-vol-label \ -o ../image.iso

>> Doesn't work. Apparently the Dell UEFI PXE firmware doesn't know HTTP. > > There's a lot of variation. Do you have a shell option > in your boot selections? None of Dell OptiPlex 990 (firmware A19), 9010 (firmware A22), nor 9020 (firmware A16) seem have a built-in EFI shell option, but in all three cases I had success running the external EFI shell from

The UEFI PXE boot DHCP/proxyDHCP issue is very timely. I am working on that very topic now. Our scenario is a manufacturing environment set up to format and load/install custom hard drive images in our systems. Our environment: This is a manufacturing floor setup where we build computers for our customers. We have two servers and a client in the mix, all connected via Ethernet (IPv4 only).

Hello all, hope all is well Was wondering if I'm doing something wrong/missing something. I have pxe+tftp+uefi working between 2 vms. However after the build is done and I reboot, I still come up to pxe b/c tianocore always starts, from what I've seen, with trying PXE first. Great for initial builds :) but I would like to it stop after. In the xml I am pointing to the disk to boot first.

Hello dear list, Using VMware I built a test setup of a server with dhcp, tftp and a http-server and several pxe-clients with EFI mode turned on. This setup worked, albeit with the exponential-like decay of IO rate I described earlier. The work-around of using HTTP works beautifully though. So it was time for the next step. Migrate this setup to our automated testing environment that runs

>>> The real DHCP server supplies client ip address only. Everything else comes from proxyDHCP. The proxyDHCP server supplies boot file name, boot file (syslinux.efi), boot loader (ldlinux.e64), config file, tinycore and OS image files. <<< This is not completely correct: your DHCP server provides an IP and your proxyDHCP server only processes a complementary DHCP

Hi, "Appendix X: virtio-mmio" in the virtio spec says ? 0x040 | RW | QueuePFN [...] When the Guest stops using the queue it must write zero (0x0) to this register. [...] and Virtqueue Configuration [...] 2. Check if the queue is not already in use: read QueuePFN register, returned value should be zero (0x0). [...] I think this in itself is

Hi, "Appendix X: virtio-mmio" in the virtio spec says ? 0x040 | RW | QueuePFN [...] When the Guest stops using the queue it must write zero (0x0) to this register. [...] and Virtqueue Configuration [...] 2. Check if the queue is not already in use: read QueuePFN register, returned value should be zero (0x0). [...] I think this in itself is

Hi, for ia64, I''d like to add xc_domain_setdebugging() in the xenctrl API. This patch implements it and modifies xc_ptrace.c to use it. The rationnal is enabling debugging tool not based on the ptrace API. The ptrace API is based on Linux ptrace which (at least on ia64) doesn''t have many privilegied registers. I''d prefer this patch being integrated on

I've been using various versions of syslinux as the boot loader for the g4l project that I have been the maintainer of since 2004. It was already using syslinux, so I've just updated it over the years, and currently have it use 5.10 version, but have done test builds with the 6.x versions. Recently had request from to users about EFI support, and one suggested that virtualbox has

Patches before the last are small cleanups. In the last patch I'm trying to extract / generalize an idea from Stefan Hajnoczi's review of my virtio-net driver for OVMF. Unfortunately I can't find Stefan's email on any mailing list archive (sourceforge, gmane, mail-archive etc. all have only my response), so I'll quote it here. The patch Stefan was reviewing is

Patches before the last are small cleanups. In the last patch I'm trying to extract / generalize an idea from Stefan Hajnoczi's review of my virtio-net driver for OVMF. Unfortunately I can't find Stefan's email on any mailing list archive (sourceforge, gmane, mail-archive etc. all have only my response), so I'll quote it here. The patch Stefan was reviewing is

Hello. I played with UEFI PXE booting the other day, and as usual, used qemu/kvm virtual machine for initial testing/debugging, because it is way easier and faster for this task than using a real hardware. However, it looks like either qemu or {pxe,sys}linux 6.03 is buggy, -- the two does not play well together. When booting, the system successfully loads syslinux.efi, at least the tftp server

Hi Rui, > but why don't you use lld-link (lld for Windows target) instead of ld.lld (lld for Unix target) to create UEFI applications? I need support both PE/COFF and ELF format tools. I’m also working on the lld-link enabling (clang-cl + lld-link) in both Linux and windows. The ld.lld enabling (clang + ld.lld) is for ELF format native users. E.g.

>>> Using VMware I built a test setup of a server with dhcp, tftp and a http-server and several pxe-clients with EFI mode turned on. This setup worked, albeit with the exponential-like decay of IO rate I described earlier. The work-around of using HTTP works beautifully though. <<< ""exponential-like decay of IO rate"" could you please post a link on

On Mon, Nov 27, 2017 at 12:07 PM, Joakim Tjernlund <Joakim.Tjernlund at infinera.com> wrote: > On Mon, 2017-11-27 at 08:42 -0500, Gene Cumm wrote: >> Bringing the discussion to the list. >> >> You stated you see the following on your Lenovo ThinkPad T470s with >> UEFI firmware N1WET41W (1.20 date: 10/17/2017): >> >> >> core_udp_sendto: stalling

EFI_XEN_OVMF_INFO is defined to accept configurations from hvmloader. It must match the definition on Xen side. XenInfo is extended to include necessary bits as well. Currently only E820 map is in use. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Wei Liu <wei.liu2@citrix.com> --- OvmfPkg/Include/Guid/XenInfo.h | 7 +++++++ OvmfPkg/PlatformPei/Xen.h | 44

Hi Rui, A quick question: Does lld-link only work with clang-cl with windows-msvc option? Can lld-link work with clang with linux-gnu option? Thanks Steven Shi Intel\SSG\FID\Firmware Infrastructure From: Shi, Steven Sent: Tuesday, January 29, 2019 1:32 PM To: 'Rui Ueyama' <ruiu at google.com> Cc: llvm-dev at lists.llvm.org Subject: RE: lld write wrong symbol value in .data

E820 definitions copied from IntelFrameworkModulePkg/Csm/ LegacyBiosDxe/LegacyBiosInterface.h. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Wei Liu <wei.liu2@citrix.com> Reviewed-by: Jordan Justen <jordan.l.justen@intel.com> --- OvmfPkg/Include/IndustryStandard/E820.h | 46 +++++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) create mode