On Sun, 21 Dec 2025 at 22:07:40 +0100, Paul Gevers wrote: >> Given autopkgtest-virt-qemu works, could you please provide its >> qemu-system command line for comparison? > > The autopkgtest logs always have the command line, you can find it on line 3.
AFAICT that's the autopkgtest-virt-qemu command line; I was wondering about the qemu-system arguments instead to compare with what we manually spawn in our autopkgtests. (Not sure if autopkgtest-virt-qemu produces different arguments depending on the platform it runs on; if not I can also run it locally.) >> There might be something to >> tweak in our tests there. Having the boot messages (`--show-boot` flag) >> for comparison could be helpful too. > > On IRC, bluca is also trying to help figuring out what's different. If it > would help you, we can give you access to a testbed to debug there if that > would help. (We need to be on-line, so we'd need to coordinate a timeslot). Sounds good! Comparing the `--show-boot` messages, it looks like both systemd and cryptsetup use `machine=q35` while autopkgtest-virt-qemu use `machine=pc`. AFAIK q35 uses I/O APIC mode which is one of the reported errors, and there might be something preventing the host from exposing I/O APIC to the guests. For cryptsetup at least there is no real reason to use q35 here, so it might be worth trying with `machine=pc` to see if that makes any difference. -- Guilhem.
signature.asc
Description: PGP signature
