On 21/01/2022 13.23, Alex Bennée wrote:
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.
In case it helps: We're already doing that in
tests/avocado/machine_s390_ccw_virtio.py : For the Debian kernel, booting
with BOOT_DEBUG=3 worked out pretty well, and for the Fedora kernel
"rd.rescue" did the job. Also unpacking the Fedora ramdisk on the host
proved to be quite faster than letting the guest unpacking the ramdisk on
its own.
Thomas
