Peter Maydell <peter.mayd...@linaro.org> writes:
> On Fri, 21 Jan 2022 at 10:50, Markus Armbruster <arm...@redhat.com> wrote: >> No objection, but it's no replacement for looking into why these tests >> are so slow. >> >> The #1 reason for things being slow is not giving a damn :) > > See previous messages in the thread -- the test starts a > full-fat guest OS including UEFI boot, and it takes forever to > get to the login prompt because systemd is starting everything > including the kitchen sink. There has to be a half-way house between booting a kernel until it fails to find a rootfs and running a full Ubuntu distro. Maybe just asking systemd to reach "rescue.target" would be enough to show the disks are up and userspace works. Running the EFI firmware is probably useful coverage but I'm not sure how one passes command line args to the guest in that approach? Do we need to set a magic EFI variable? > > -- PMM -- Alex Bennée
