On Sun, Nov 17, 2013 at 7:50 PM, Celelibi <celel...@gmail.com> wrote: > Hello, > > I compiled OVMF from the lastest revision available on git sourceforge. > > I run it with the command: > qemu-system-x86_64 -device rtl8139,netdev=tap0 -netdev > tap,id=tap0,ifname=tap0,script=no -bios > Build/OvmfX64/DEBUG_GCC47/QEMU/bios.bin -boot order=n > > This combination of -device and -netdev works fine with the default > BIOS (seaBIOS if I'm not wrong). > > And not only it doesn't even seem to try to boot on the network, when > I type ifconfig -l in the EFI shell I get the error: > "Error. The protocol 'gEfiIp4ConfigProtocolGuid' was required and not > found (...)" > > While, if I understood correctly OvmfPkg/README, everything should > work all by itself. > It says "OVMF provides a UEFI network stack by default.". > > Did I miss something? > > For what it's worth, qemu version is 1.6.1.
We don't have a EDK II driver for that network device. Thanks to Laszlo, we have a virtio network driver. Hmm, it seems Gerd may have indicated that the ipxe roms were UEFI compatible. I'm not sure if that meant, can boot from the network, or if it meant can work with the rest of the EDK II network stack. -Jordan ------------------------------------------------------------------------------ Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
