[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [ipxe-devel] [PATCH ipxe] build: Enable IPv6 for qemu
From: |
Laszlo Ersek |
Subject: |
Re: [Qemu-devel] [ipxe-devel] [PATCH ipxe] build: Enable IPv6 for qemu |
Date: |
Thu, 28 Jan 2016 18:50:14 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 |
Sorry, Cole disappeared from the address list, and I forgot to re-add
him. Resending.
On 01/28/16 11:19, Gerd Hoffmann wrote:
> Hi,
>
>> How common is it to build EFI roms, compared to building ipxe.efi or
>> snponly.efi?
>
> No idea. qemu is a very specific case, ipxe has drivers for the qemu
> nics (both virtual such as virtio-net and emulated such as rtl8139), and
> right now we actually build ipxe tree times (bios, efi-ia32,
> efi-x86_64), then combine them into a single image, using EfiRom
> (shipped with edk2). That image is populated to the guest via pci rom
> bar. That way both seabios and ovmf (edk2 firmware for qemu) have
> drivers available.
>
> How much bios vs. efi is used -- I don't know. seabios is the default
> and has been for years, so it is pretty clear that seabios takes the
> lead. But whenever uefi share is at 1% or 10% -- no idea.
>
> Probably we'll go add efi-aarch64 roms to the mix once ipxe support is
> there, or maybe drop efi-ia32 in favor of efi-aarch64.
>
>> On IRC, roms is quite rare topic compared to non rom builds, but maybe
>> that's because those that build roms don't have that many questions.
>
> I suspect it is because it rarely happens. For onboard nics there
> simply is no rom you can easily populate. Instead the nic rom is stored
> in the firmware flash, together with bios/uefi. Chainloading ipxe.efi
> is *alot* simpler than hacking your firmware flash.
>
> Add-on cards are a different story of course, but I suspect >90% of the
> use cases are with onboard nics.
>
> The only case where I personally had a ipxe rom running on physical
> hardware was when I flashed a T60 Thinkpad (hardware broke meanwhile)
> with coreboot.
>
> qemu has a defined set of hardware and prebuilt roms are shipped with
> both qemu and distros. So people rarely have to build qemu roms
> themself -> no irc questions either ;)
I think that enabling IPv6 for the CONFIG=qemu build of iPXE will have
no effect for OVMF guests.
With CONFIG=qemu we only request SNP interfaces (low level NIC drivers)
from iPXE. Internet protocols are at a higher level, and with
CONFIG=qemu, the edk2 network stack is used on top of iPXE's SNP
interface. The iPXE feature test macro NET_PROTO_IPV6 will have no effect.
OVMF can pull in the IPv6 parts of edk2, but it needs
-D NETWORK_IP6_ENABLE
for that (<https://github.com/tianocore/edk2/commit/36c6413f76e5>).
Thanks
Laszlo
- Re: [Qemu-devel] [PATCH ipxe] build: Enable IPv6 for qemu, Cole Robinson, 2016/01/12
- Re: [Qemu-devel] [PATCH ipxe] build: Enable IPv6 for qemu, Gerd Hoffmann, 2016/01/26
- Re: [Qemu-devel] [ipxe-devel] [PATCH ipxe] build: Enable IPv6 for qemu, Michael Brown, 2016/01/27
- Re: [Qemu-devel] [ipxe-devel] [PATCH ipxe] build: Enable IPv6 for qemu, Gerd Hoffmann, 2016/01/27
- Re: [Qemu-devel] [ipxe-devel] [PATCH ipxe] build: Enable IPv6 for qemu, Christian Nilsson, 2016/01/27
- Re: [Qemu-devel] [ipxe-devel] [PATCH ipxe] build: Enable IPv6 for qemu, Gerd Hoffmann, 2016/01/28
- Re: [Qemu-devel] [ipxe-devel] [PATCH ipxe] build: Enable IPv6 for qemu, Michael Brown, 2016/01/28
- Re: [Qemu-devel] [ipxe-devel] [PATCH ipxe] build: Enable IPv6 for qemu, Laszlo Ersek, 2016/01/28
- Re: [Qemu-devel] [ipxe-devel] [PATCH ipxe] build: Enable IPv6 for qemu,
Laszlo Ersek <=
- Re: [Qemu-devel] [ipxe-devel] [PATCH ipxe] build: Enable IPv6 for qemu, Tore Anderson, 2016/01/28