Hi, > Gerd, can you chime in please? As far as I remember, qemu only picks up > the ".efidrv" output from the iPXE build process, which should only be > the SNP driver.
Yes, we are using .efidrv, with the intention to pick up just the driver and give ovmf network access that way. You can also build ipxe (with all the features it has) as driver-less efi application, so one can simply run that on top of the (ipxe or other) driver when advanced ipxe features such as sanboot are needed. That is at least the intention. But ipxe documentation on the topic is *ahem* sparse, I've figured things by digging in the ipxe Makefiles and some guesswork. Quite possible that things are not built correctly. Check roms/Makefile in the qemu tree to see how the roms are built. Patches are welcome. Asking on the ipxe mailing list might be a good idea. There was another ipxe update in December, after the 2.2 release, so you might want try updating to latest master branch or cherry-pick the commit and see whenever that fixes your problem: =============== cut here =============== commit c246cee4eedb17ae3932d699e009a8b63240235f Author: Gerd Hoffmann <[email protected]> Date: Wed Dec 17 13:56:50 2014 +0100 update ipxe from 69313ed to 35c5379 [ shortlog snipped ] =============== cut here =============== HTH, Gerd ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
