I know, I could distribute some DHCP options for the VM to boot via HTTP. Now, If I switch from OVMF to BIOS, the same procedure works just fine. How ever, what ever I try to boot now, my Windows 10 Setup or SystemrescueCD, launching wimboot or the SysrescueCD-Kernel, after the download I am back on the OVMF shell. That works, my ipxe boot menue is downloaded via http and I get my boot options. My next step was to replace the original vmxnet3.rom with my own one, that has the nasboot script embeded, so that the boot process would continue via http. If I examine the pxe/efi roms from /usr/share/kvm, I realize, that those look more like plain 32bit roms rather then 32/64bit as the one, I create using the. Make bin-x86_64-efi/vmxnet3.efirom EMBED=nasboot.ipxe Make bin-x86_64-efi/vmxnet3.efi EMBED=nasboot.ipxe MS-DOS executable PE32+ executable (DLL) (EFI application) x86-64, for MS Windows Make bin-x86_64-efi/ipxe.efi EMBED=nasboot.ipxe In short: If I boot a VM in OVMF using vmxnet3 (I also tried e1000) aiming to boot via pxe to my tftp server, where it is served ipxe.efi (a build working fine on dozens of bare-metal computers of different brands (HP, Lenovo)), OVMF ignores the received ipxe.efi (tftp log shows "client does not accept options", and continues on trying any other boot-device.Īs I build my own ipxe.efi images with embeded scripts to chainload from http server, so that the setup will work from any computer, what ever the native pxe-build might be, I know, that there are 32 and 64bit efi builds, as well as 32-bit bios-pxe builds. Unfortunately I did not find any satisfying answers to this topics in any other post, so I'm starting a new one:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |