Your message dated Tue, 11 Jan 2022 07:44:25 -0700
with message-id <[email protected]>
and subject line Re: Bug#1003480: Using AAVMF32_VARS.fd causes data exception
and failure to boot
has caused the Debian Bug report #1003480,
regarding Using AAVMF32_VARS.fd causes data exception and failure to boot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1003480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003480
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-efi-arm
Version: 2020.11-2
Hello Maintainers,
There seems to be an issue with the 32-bit ARM UEFI firmware VARS file,
at /usr/share/AAVMF/AAVMF32_VARS.fd. When I try to use it, I get a Data
exception and a failure to boot the firmware.
This issue can be reproduced using the following command:
qemu-system-arm -display none -machine virt -drive \
if=pflash,format=raw,unit=1,readonly=on,file=/usr/share/AAVMF/AAVMF32_VARS.fd
\
-drive \
if=pflash,format=raw,unit=0,readonly=on,file=/usr/share/AAVMF/AAVMF32_CODE.fd
\
-monitor file:/dev/null -serial file:/dev/stdout
It can be seen that the VARS file is at issue here because the
following command boots as expected:
qemu-system-arm -display none -machine virt -drive \
if=pflash,format=raw,unit=0,readonly=on,file=/usr/share/AAVMF/AAVMF32_CODE.fd
\
-monitor file:/dev/null -serial file:/dev/stdout
Glenn
--- End Message ---
--- Begin Message ---
On Mon, Jan 10, 2022 at 06:40:52PM -0600, Glenn Washburn wrote:
> On Mon, 10 Jan 2022 14:27:01 -0700
> dann frazier <[email protected]> wrote:
>
> > On Mon, Jan 10, 2022 at 02:50:27PM -0600, Glenn Washburn wrote:
> > > Package: qemu-efi-arm
> > > Version: 2020.11-2
> > >
> > > Hello Maintainers,
> > >
> > > There seems to be an issue with the 32-bit ARM UEFI firmware VARS file,
> > > at /usr/share/AAVMF/AAVMF32_VARS.fd. When I try to use it, I get a Data
> > > exception and a failure to boot the firmware.
> > >
> > > This issue can be reproduced using the following command:
> > >
> > > qemu-system-arm -display none -machine virt -drive \
> > >
> > > if=pflash,format=raw,unit=1,readonly=on,file=/usr/share/AAVMF/AAVMF32_VARS.fd
> > > \
> > > -drive \
> > >
> > > if=pflash,format=raw,unit=0,readonly=on,file=/usr/share/AAVMF/AAVMF32_CODE.fd
> > > \
> > > -monitor file:/dev/null -serial file:/dev/stdout
> > >
> > > It can be seen that the VARS file is at issue here because the
> > > following command boots as expected:
> > >
> > > qemu-system-arm -display none -machine virt -drive \
> > >
> > > if=pflash,format=raw,unit=0,readonly=on,file=/usr/share/AAVMF/AAVMF32_CODE.fd
> > > \
> > > -monitor file:/dev/null -serial file:/dev/stdout
> >
> > Hi Glenn,
> >
> > The VARS file needs to be writeable. You should typically make a
> > copy per-guest and omit the readonly=on bit for that file on the QEMU
> > command line.
>
> Thanks Dann, I can confirm that this does indeed resolve the issue. I
> had previously tried copying the VARS file, but hadn't thought to take
> off the readonly=on.
No problem, glad it's working for you.
--- End Message ---
