Your message dated Wed, 3 Jan 2024 18:55:48 +0300
with message-id <[email protected]>
and subject line Re: Bug#973790: qemu-system-arm: qemu-system-aarch64 does not
support secure boot
has caused the Debian Bug report #973790,
regarding qemu-system-arm: qemu-system-aarch64 does not support secure 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.)
--
973790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973790
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-system-arm
Version: 1:5.1+dfsg-4+b1
Severity: wishlist
Control: block 973780 by -1
Dear Maintainer,
apt-cache show qemu-efi-aarch64 says
Description-en: UEFI firmware for 64-bit ARM virtual machines
qemu-efi-aarch64 is a build of EDK II for 64-bit ARM virtual machines. It
includes full support for UEFI, including Secure Boot.
But qemu-system-aarch64 does not seem to provide a way to enable
secure boot. Specifically, -machine virt,secure=on gives
Unexpected error in object_property_find() at
/build/qemu-sqqV4a/qemu-5.1+dfsg/qom/object.c:1254:
qemu-system-aarch64: Property '.secure-memory' not found
Aborted
Best regards, Ryutaroh Matsumoto
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)
Kernel: Linux 5.9.0-1-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages qemu-system-arm depends on:
ii libaio1 0.3.112-8
ii libc6 2.31-4
ii libcapstone3 4.0.1+really+3.0.5-2+b1
ii libepoxy0 1.5.4-1
ii libfdt1 1.6.0-1
ii libgbm1 20.1.9-1
ii libgcc-s1 10.2.0-15
ii libglib2.0-0 2.66.1-2
ii libgnutls30 3.6.15-4
ii libibverbs1 31.0-1
ii libjpeg62-turbo 1:2.0.5-1.1
ii libnettle8 3.6-2
ii libnuma1 2.0.12-1+b1
ii libpixman-1-0 0.36.0-1
ii libpmem1 1.9.2-1
ii libpng16-16 1.6.37-3
ii librdmacm1 31.0-1
ii libsasl2-2 2.1.27+dfsg-2
ii libseccomp2 2.4.4-1+b1
ii libslirp0 4.3.1-1
ii libspice-server1 0.14.3-2
ii libstdc++6 10.2.0-15
ii liburing1 0.7-2
ii libusb-1.0-0 2:1.0.23-2
ii libvdeplug2 4.0.1-2
ii libvirglrenderer1 0.8.2-4
ii qemu-system-common 1:5.1+dfsg-4+b1
ii qemu-system-data 1:5.1+dfsg-4
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages qemu-system-arm recommends:
ii ipxe-qemu 1.0.0+git-20190125.36a4c85-5
ii qemu-efi-aarch64 2020.08-1
ii qemu-efi-arm 2020.08-1
pn qemu-system-gui <none>
ii qemu-utils 1:5.1+dfsg-4+b1
Versions of packages qemu-system-arm suggests:
pn qemu-block-extra <none>
pn samba <none>
pn vde2 <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:7.2+dfsg-1
On Thu, 05 Nov 2020 17:32:26 +0900 Ryutaroh Matsumoto
<[email protected]> wrote:
Package: qemu-system-arm
Version: 1:5.1+dfsg-4+b1
Severity: wishlist
Control: block 973780 by -1
Dear Maintainer,
apt-cache show qemu-efi-aarch64 says
Description-en: UEFI firmware for 64-bit ARM virtual machines
qemu-efi-aarch64 is a build of EDK II for 64-bit ARM virtual machines. It
includes full support for UEFI, including Secure Boot.
But qemu-system-aarch64 does not seem to provide a way to enable
secure boot. Specifically, -machine virt,secure=on gives
Unexpected error in object_property_find() at
/build/qemu-sqqV4a/qemu-5.1+dfsg/qom/object.c:1254:
qemu-system-aarch64: Property '.secure-memory' not found
Aborted
This has been implemented quite some time ago. For one, bookworm
version supports secure-boot on aarch64, it seems. Closing this
bug report now.
Overall, it's kind of pointless to file feature request bugs against
debian bug tracker, such features should be implemented in upstream
qemu, not in debian.
/mjt
--- End Message ---
