Your message dated Mon, 04 Oct 2021 20:34:04 +0000
with message-id <[email protected]>
and subject line Bug#973522: fixed in autopkgtest 5.17
has caused the Debian Bug report #973522,
regarding autopkgtest-virt-qemu does not support i386 uefi 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.)


-- 
973522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973522
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: autopkgtest
Version: 5.15
Severity: minor
X-Debbugs-Cc: [email protected]

Dear Maintainer,

The following part of autopkgtest-virt-qemu gives impression that
autopkgtest ... -- qemu --efi supports QEMU testbed with UEFI.
Indeed, QEMU with UEFI testbed works fine for amd64, as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973038#30

    if args.efi:
        code = None
        data = None

        if 'qemu-system-x86_64' in args.qemu_command or \
                'qemu-system-i386' in args.qemu_command:
            code = '/usr/share/OVMF/OVMF_CODE.fd'
            data = '/usr/share/OVMF/OVMF_VARS.fd'
        elif 'qemu-system-aarch64' in args.qemu_command:
            code = '/usr/share/AAVMF/AAVMF_CODE.fd'
            data = '/usr/share/AAVMF/AAVMF_VARS.fd'
        elif 'qemu-system-arm' in args.qemu_command:
            code = '/usr/share/AAVMF/AAVMF32_CODE.fd'
            data = '/usr/share/AAVMF/AAVMF32_VARS.fd'
        else:
            VirtSubproc.bomb('Unknown architecture for EFI boot')

With the attached patch to vmdb2 and autopkgtest-build-qemu,
QEMU i386 UEFI testbed can be built without error.
But autopkgtest ... -- qemu --efi -q qemu-system-i386 does
not work, as the Linux in VM does not boot, at least on
my amd64 laptop.

This means that complete switching of autopkgtest-virt-qemu to
UEFI is impossible as of now, while arm64 QEMU autopkgtestbed
seems to require UEFI booting...

Best regards, Ryutaroh Matsumoto

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.8.0-1-amd64 (SMP w/12 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages autopkgtest depends on:
ii  apt-utils       2.1.11
ii  libdpkg-perl    1.20.5
ii  procps          2:3.3.16-5
ii  python3         3.8.2-3
ii  python3-debian  0.1.38

Versions of packages autopkgtest recommends:
ii  autodep8  0.24

Versions of packages autopkgtest suggests:
pn  lxc               <none>
pn  lxd               <none>
ii  ovmf              2020.08-1
ii  qemu-efi-aarch64  2020.08-1
ii  qemu-efi-arm      2020.08-1
ii  qemu-system       1:5.1+dfsg-4+b1
ii  qemu-utils        1:5.1+dfsg-4+b1
pn  schroot           <none>
ii  vmdb2             0.19-1

-- no debconf information
--- usr/lib/python3/dist-packages/vmdb/plugins/grub_plugin.py-orig      
2020-11-01 17:24:02.365918675 +0900
+++ usr/lib/python3/dist-packages/vmdb/plugins/grub_plugin.py   2020-11-01 
17:44:44.244822315 +0900
@@ -112,8 +112,8 @@
             raise Exception('"efi" or "efi-part" required in UEFI GRUB 
installation')
 
         vmdb.progress("Installing GRUB for UEFI")
-        grub_package = "grub-efi-amd64"
-        grub_target = "x86_64-efi"
+        grub_package = "grub-efi-ia32"
+        grub_target = "i386-efi"
         self.install_grub(values, settings, state, grub_package, grub_target)
 
     def install_bios(self, values, settings, state):
--- usr/bin/autopkgtest-build-qemu-orig 2020-10-31 10:05:36.350588392 +0900
+++ usr/bin/autopkgtest-build-qemu      2020-10-31 14:38:34.403340017 +0900
@@ -252,12 +252,20 @@
   - mkimg: "{{ image }}"
     size: $size
 
-  - mklabel: msdos
+  - mklabel: gpt
     device: "{{ image }}"
 
   - mkpart: primary
+    fs-type: fat32
     device: "{{ image }}"
     start: 0%
+    end: 200MiB
+    tag: efipart
+
+  - mkpart: primary
+    fs-type: ext4
+    device: "{{ image }}"
+    start: 200MiB
     end: 100%
     tag: root
 
@@ -266,6 +274,9 @@
   - mkfs: ext4
     partition: root
 
+  - mkfs: vfat
+    partition: efipart
+
   - mount: root
 
   - $debootstrap_cmd: $release
@@ -279,8 +290,9 @@
       - ifupdown
     tag: root
 
-  - grub: bios
+  - grub: uefi
     tag: root
+    efi: efipart
     console: serial
 
   - chroot: root
@@ -295,6 +307,9 @@
       rootdev=\$(ls -1 /dev/mapper/loop* | sort | tail -1)
       uuid=\$(blkid -c /dev/null -o value -s UUID \$rootdev)
       echo "UUID=\$uuid / ext4 errors=remount-ro 0 1" > \$ROOT/etc/fstab
+      efidev=\$(ls -1 /dev/mapper/loop* | sort | head -1)
+      uuid=\$(blkid -c /dev/null -o value -s UUID \$efidev)
+      echo "UUID=\$uuid /boot/efi vfat rw 0 2" >> \$ROOT/etc/fstab
     root-fs: root
 
   - shell: '$script \$ROOT'

--- End Message ---
--- Begin Message ---
Source: autopkgtest
Source-Version: 5.17
Done: Paul Gevers <[email protected]>

We believe that the bug you reported is fixed in the latest version of
autopkgtest, 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.
Paul Gevers <[email protected]> (supplier of updated autopkgtest 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: SHA256

Format: 1.8
Date: Mon, 04 Oct 2021 21:04:48 +0200
Source: autopkgtest
Architecture: source
Version: 5.17
Distribution: unstable
Urgency: medium
Maintainer: Debian CI team <[email protected]>
Changed-By: Paul Gevers <[email protected]>
Closes: 926945 973038 973522 973663 982296 990415
Changes:
 autopkgtest (5.17) unstable; urgency=medium
 .
   [ Ryutaroh Matsumoto ]
   * Use 32-bit OVMF EFI firmware for qemu-system-i386 (Closes: #973522)
   * qemu: Explicitly assign unit numbers for pflash devices
 .
   [ Iain Lane ]
   * lxd: Fix a race condition while rebooting
   * buildvm-ubuntu-cloud: Update for compatibility with other changes
     mentioned below
   * ssh-setup/nova: Quote arguments to `tr`
 .
   [ Simon McVittie ]
   * VirtSubproc: Allow expecting multiple options
   * virt-qemu: Cope with passwordless shell (blank password)
   * virt-qemu: Don't rely on exiting from a shell printing "logout"
   * virt-qemu: Preseed debconf questions so we can upgrade grub-pc, if
     installed (Closes: #982296)
   * virt-qemu: Add --qemu-architecture, --dpkg-architecture options
   * virt-qemu: Load virtio_console in initramfs to make sure it's ready
     when systemd-getty-generator(8) looks for it (workaround for #689962)
   * virt-qemu: Improve reliability of interactions with serial console shell
   * build-qemu: Automatically run under fakemachine if not uid 0
   * build-qemu: Convert image into an absolute path.
     This helps when we're sharing directories as "volumes" with fakemachine.
     The working directory inside fakemachine isn't necessarily the same as
     the working directory outside, leading to the output image being
     written somewhere unintended.
   * build-qemu: Show the log from vmdb2 if it fails
   * build-qemu: Placate pycodestyle
   * build-qemu: Never set http_proxy to DIRECT.
     The special keyword DIRECT is understood by apt, but not by generic
     http clients, and in particular not understood by wget (used by
     debootstrap).
   * Use `command -v` in preference to `which`.
     In Debian, which(1) is provided by the Essential debianutils package,
     which recently deprecated it. Silence the resulting warnings by doing
     this in a slightly less obvious way.
 .
   [ Simon McVittie, Ryutaroh Matsumoto ]
   * setup-testbed: Try to put Linux console on both ttyS0 and hvc0.
     ttyS0 is PC-specific, hvc0 is a generic hypervisor console available
     on multiple hypervisors.
   * setup-testbed: Put root shells on both ttyS1 and hvc1 if they exist.
     ttyS1 is PC-specific, hvc1 is a generic hypervisor console available
     on multiple hypervisors.
   * virt-qemu: Only -enable-kvm if VM is compatible with host architecture
   * virt-qemu: Add --boot=efi (formerly --efi)
   * build-qemu: Add --boot=efi to build images bootable with EFI.
     This requires vmdb2 0.22-1~ or newer.
   * qemu: armhf and aarch64 support (Closes: #973038, #973663)
     - Boot with EFI by default
     - Build images with EFI by default (Closes: #990415)
     - Use ttyAMA0 as the ARM equivalent of ttyS0
     - Default to -machine virt, since there is no default in qemu
     - Default to qemu-system-aarch64 -cpu host,aarch64=off -enable-kvm
       for armhf on aarch64 host, because qemu-system-arm -enable-kvm is
       not available on aarch64 hosts
     - Default to -cpu host -enable-kvm for aarch64 on aarch64 host
     - Default to -cpu cortex-a53 for aarch64 on non-aarch64 host
       since that CPU seems to work well
     Thanks to Christian Kastner, Peter Maydell and Steve McIntyre.
 .
   [ Simon McVittie, Thierry Fauck, Ryutaroh Matsumoto ]
   * qemu: ppc64el support (Closes: #926945)
     - Install grub-ieee1275 by default
     - Avoid trying to allocate hvc0 as a virtio console.
       The default serial port of a pSeries machine appears as /dev/hvc0,
       and the virtio consoles start from hvc1.
     Thanks to Christian Kastner
 .
   [ Christian Kastner ]
   * qemu: Use -machine q35 on i386 or amd64 when booting with EFI.
     Empirically, it seems to be the minimum required for EFI-booting on
     i386; bump the machine on amd64 too, for consistency.
 .
   [ Julian Andres Klode ]
   * setup-testbed: Remove needrestart so its dpkg hook does not interfere
     with the apt test suite
   * setup-testbed: Set Acquire::Retries 10, like debci does
   * setup-testbed: Always include phased updates
Checksums-Sha1:
 18afdd8652f643ff0a719d8bae8f5e550c5d4cfd 1695 autopkgtest_5.17.dsc
 2846ddb25b122d3e91298f4ee82b9a8345006534 196296 autopkgtest_5.17.tar.xz
Checksums-Sha256:
 06bff19d2d5a6d034995bc205645d6376d686f7c7d897d473b1732f4a21d24d2 1695 
autopkgtest_5.17.dsc
 9ec3ab530d445b1d9a3aa92ae73850c7f65ba330381da30da1d2e2e4f36af9cb 196296 
autopkgtest_5.17.tar.xz
Files:
 35fe7b1dfdcc1f303b1bcf4df502d0b5 1695 devel optional autopkgtest_5.17.dsc
 cefb14ba1e18276a9ee48fcc3b1083c5 196296 devel optional autopkgtest_5.17.tar.xz

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmFbW/MACgkQnFyZ6wW9
dQqP/Af/f4r8XHKhwy9NWxo5ROPLteyCWLTYn+CQrHbuuVBQRRuDHvA4gv9J7h04
3rJKHXMm3WIoyMeHcEegUp3ooGZ0uABab/Wgw1lnrBrtbtuEY/6Al+md+vZbMl+x
11lA8FecQDAqMt8Qs0he3c4bKnnV6naCk5Vs8jRW/hw/bDft9tPJF9Pte9hg5QlQ
4Ya2VlvcYgH4/EKUgevuDnNxbPzOy/zXV7q9WcBVqz2prrCdW2bLfBtz8LKnVPF8
5vuB4mm78zszCZeZuCk+68BQD0yPtBuES5t/L0fcPYQRczHtdYY1JMkgpIM7WwP6
mxAcHmiZFxGcQIBEm1DRCeImEWFSuQ==
=Cqmf
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to