hey, I'm investigating enabling AArch32/Virt edk2 builds in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857858
I wanted to see if we can reach a consensus on what the pathname for these images should be, as these paths for other architectures have become hardcoded in upstream projects like OpenStack Nova and libvirt.
These project currently expect to find the AArch64 images at: /usr/share/AAVMF/AAVMF_{CODE,VARS}.fd And, similarly, the x86-64 images at: /usr/share/ovmf/OVMF_{CODE,VARS}.fd I'm unaware of anyone shipping 32-bit x86 images.
I propose: /usr/share/AAVMF/AAVMF32_{CODE,VARS}.fd
-dann
On 10 April 2017 at 20:02, dann frazier dannf@dannf.org wrote:
hey, I'm investigating enabling AArch32/Virt edk2 builds in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857858
I wanted to see if we can reach a consensus on what the pathname for these images should be, as these paths for other architectures have become hardcoded in upstream projects like OpenStack Nova and libvirt.
These project currently expect to find the AArch64 images at: /usr/share/AAVMF/AAVMF_{CODE,VARS}.fd And, similarly, the x86-64 images at: /usr/share/ovmf/OVMF_{CODE,VARS}.fd I'm unaware of anyone shipping 32-bit x86 images.
I propose: /usr/share/AAVMF/AAVMF32_{CODE,VARS}.fd
I don't have strong opinion, but once shipping the arm32 EFI in the package, it would be good to submit a patch to libvirt, since it seems the place where all the other projects derive their location for efi firmwares...
Riku
On Tue, Apr 11, 2017 at 1:28 AM, Riku Voipio riku.voipio@linaro.org wrote:
On 10 April 2017 at 20:02, dann frazier dannf@dannf.org wrote:
hey, I'm investigating enabling AArch32/Virt edk2 builds in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857858
I wanted to see if we can reach a consensus on what the pathname for these images should be, as these paths for other architectures have become hardcoded in upstream projects like OpenStack Nova and libvirt.
These project currently expect to find the AArch64 images at: /usr/share/AAVMF/AAVMF_{CODE,VARS}.fd And, similarly, the x86-64 images at: /usr/share/ovmf/OVMF_{CODE,VARS}.fd I'm unaware of anyone shipping 32-bit x86 images.
I propose: /usr/share/AAVMF/AAVMF32_{CODE,VARS}.fd
I don't have strong opinion, but once shipping the arm32 EFI in the package, it would be good to submit a patch to libvirt, since it seems the place where all the other projects derive their location for efi firmwares...
(Belated) thanks Riku. fyi, it's in final-comment phase: https://www.redhat.com/archives/libvir-list/2017-July/msg00846.html
-dann
-
dann frazier -
dann frazier -
Riku Voipio