Your message dated Tue, 18 Mar 2025 09:24:02 +0000
with message-id <[email protected]>
and subject line Bug#1095073: fixed in ipxe 1.21.1+git20250317.42a29d56+dfsg-1
has caused the Debian Bug report #1095073,
regarding qemu-system: coordination with ROMs provided by ipxe
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.)
--
1095073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095073
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: qemu
Version: 1:9.2.0+ds-5
Severity: normal
X-Debbugs-CC: [email protected]
Control: affects -1 + ipxe-qemu
Dear qemu maintainers,
I will soon maintain ipxe along with Harry Chen, planing importing new
ipxe version snapshots and enabling more architectures. I noticed that
qemu-system-* is depending the ROMs provided by ipxe. So I believe it will
be necessary for coordination between the two packages.
Currently the package ipxe-qemu provides a series of ROM files for the
emulated NICs. Without manually specifying romfile=, qemu-system-* for
whichever architecture will try to load the corresponding ROM file.
Without the ROM file, qemu will refuse to start, unless an empty romfile=
is manually specified. In such condition, of course the PXE functionality
will not work.
Previously, each ROM file provided by ipxe-qemu is combined with two ROMs,
one is for x86 legacy booting and the other is for x86-64 UEFI booting.
The former provides the networking driver for the emulated NIC and full
PXE stack, while the later only provides the driver on the lower layer,
letting the firmware provide the upper PXE stack. When booting a virtual
machine of other architectures, say an arm64 virtual machine, the ROMs
will also be picked up by qemu-system-aarch64 by default, but not
providing any functionalities, since they do not contain code for that
architecture.
The first problem is that currently the package qemu-system-x86 depends
on ipxe-qemu, but other qemu-system-* packages recommend it. According to
the same behavior that qemu for no matter which architecture requires a
ROM file by default, should the relationship between all the qemu-system-*
packages be made the same?
The second problem is that Debian is additionally providing edk2
firmwares for arm64, riscv64 and loong64, enabling UEFI booting for
qemu-system for these architectures. I've tested that if drivers for these
architectures are also compiled in iPXE and combined into the ROM files,
the emulated NIC can be recognized in the UEFI firmware settings interface
(in Device Manager -> Network Device List). We now may have two options
for enabling drivers for these architectures:
Opt1: Combine the drivers for all the architectures into one ROM like
before.
Pros:
- changes are only needed in ipxe and no changes are needed for qemu;
- it is actually tested and indeed works;
Cons:
- the size of the ROM files will grow beyond the current 512k pow2
bucket, affecting live migration. (See #881263)
Opt2: Using separate ROM files for each architecture. The name of the
files remain unchanged but the ROMs for each architecture is put into
separate directories, and maybe into separate packages, and qemu-system-*
is configured to search different directories for different architectures.
Pros:
- it will be unlikely that the size of ROM files grows beyond the current
512k pow2 bucket, even if new architectures are introduced or ipxe is
updated in the future.
Cons:
- changes are needed for qemu, and further coordination is required.
We have uploaded a new version of ipxe into stable (approval from FTP
team is needed), in which drivers for arm64 are enabled and combined into
the ROM files, since none of the ROM files exceeds the current 512k pow2
bucket.
Looking forward to your advice on introducing support for new
architectures to the ROM files.
Cheers,
Miao Wang
--- End Message ---
--- Begin Message ---
Source: ipxe
Source-Version: 1.21.1+git20250317.42a29d56+dfsg-1
Done: Shengqi Chen <[email protected]>
We believe that the bug you reported is fixed in the latest version of
ipxe, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Shengqi Chen <[email protected]> (supplier of updated ipxe package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 18 Mar 2025 17:03:54 +0800
Source: ipxe
Architecture: source
Version: 1.21.1+git20250317.42a29d56+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Miao Wang <[email protected]>
Changed-By: Shengqi Chen <[email protected]>
Closes: 1095073
Changes:
ipxe (1.21.1+git20250317.42a29d56+dfsg-1) unstable; urgency=medium
.
[ Miao Wang ]
* d/control: add <!nocheck> back for qemu-system-misc
* d/p/reduce_efirom_size.patch: remove unnecessary objects
* d/p/fix-lkrn-long-version.patch: use upstream patch
* d/tests: add pxe boot tests
* d/rules: output size information during combining ROMs
* efirom: remove non-x86 roms and remain within 256k (closes: #1095073)
* d/rules: fix build failure on i386
.
[ Shengqi Chen ]
* New upstream version 1.21.1+git20250317.42a29d56+dfsg
* d/control: bump std-ver to 4.7.2 (no changes required)
* d/patches: remove applied patch and refresh
Checksums-Sha1:
22f62254adf4d33a99c8e3aa9edded16f8bde5f8 3316
ipxe_1.21.1+git20250317.42a29d56+dfsg-1.dsc
ec1d7d252438e3f97edf4bc59d17803cad38954a 2871940
ipxe_1.21.1+git20250317.42a29d56+dfsg.orig.tar.xz
6a11ef7411f3b2271db210e2cebe672e2169c01e 24508
ipxe_1.21.1+git20250317.42a29d56+dfsg-1.debian.tar.xz
2c70905d67a658bd1fec33a8bba089e651ecfa9e 11340
ipxe_1.21.1+git20250317.42a29d56+dfsg-1_amd64.buildinfo
Checksums-Sha256:
82c2db9e7e68923ca2f384cf57a085510c57664cc88e8ddd0672fb3091fb8b96 3316
ipxe_1.21.1+git20250317.42a29d56+dfsg-1.dsc
149ea7a227321eea0cb236107a20897c6d637fb9351adfd46c37d09fb980905a 2871940
ipxe_1.21.1+git20250317.42a29d56+dfsg.orig.tar.xz
0ba6af47e5cef41df370d4a2d6b3c92f12a2e944c727ae46f177608c18a8b79f 24508
ipxe_1.21.1+git20250317.42a29d56+dfsg-1.debian.tar.xz
a07f1808b5e5d0dbcd84e28a5327f5605fdb7901dcc97c37ece7a2606b71951f 11340
ipxe_1.21.1+git20250317.42a29d56+dfsg-1_amd64.buildinfo
Files:
7110b9c2b06ad06120ad24df529507bc 3316 admin optional
ipxe_1.21.1+git20250317.42a29d56+dfsg-1.dsc
d876d52bb4f4a277250eeb209888b8ee 2871940 admin optional
ipxe_1.21.1+git20250317.42a29d56+dfsg.orig.tar.xz
0d88b8e9397765d4d395fe02dd2669da 24508 admin optional
ipxe_1.21.1+git20250317.42a29d56+dfsg-1.debian.tar.xz
9c6790644d16e6966db582fd3ff030ac 11340 admin optional
ipxe_1.21.1+git20250317.42a29d56+dfsg-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE+Fg++qmpHzqjSzySzhGnsHs6uUYFAmfZOQsACgkQzhGnsHs6
uUbPRRAApyO4bZUj8m2aRzariX2xnf8PZHXRZowF8pb/MfD9c0ZK6R2zDicmZmk3
8qPl/q57fl/mXG7y6f0YpzCyYxON1zyvU2DoqOJHSILyiP83LSLAGnrGwiOj20FY
46pSx3zehLfiZFt3hRlcTbR8rZdmNEBKGi+wbCHBIxKa+Hy7/B1cK+zJbl6ADyLp
kNNbNkiFobDL3SSmAduLKVbIwO5Y4DNq9cOWdFoHsmTet6Yc9zu/6BkH2Jv+R5th
bSKRT/SRHad+6Zr20Aezsk8PeH2LBY/+DTuMoxLXhKdh8hQAkrCrlESFnM4i7Vkb
PYT+mBafsTO1aAiVOyYgcGg9Q9ccdF10EVkD61jJL6/wp/tO97Q1mE/UN9zH7JDc
NnXwXZ2di323QTsEHYTtFPPP27/LZ6PmAsRdU4Gy8C9c5sH751bC2mVwyT/GiZDx
txtF7vJddwNRj4PffJtkdd5KoFOYQVzmNaKdycQFCjB6yxb7WW6lcc+tiV2qBtZy
XRYZuL9gkFhu2hIfqtI6iYSLwMOGg3RJAd4xJ65hMq7COQ0Rg1lWgApK8wQge7ea
Ki5HHES/7VvHCT6qmIHOfrcLAlJV0d5Glx5J7nJJ95wnZD9AuRwlp6SmfmM5VSRC
ir4tAnqjvceCEjbHgkfNz8YkZQFCSiUiIEEKdaS+SDR32ExyxlU=
=/uoB
-----END PGP SIGNATURE-----
pgpd7LU0YYL7s.pgp
Description: PGP signature
--- End Message ---
