Comment 1 for bug 2056065

Hi Ross,
thanks for the report, and that is odd indeed.
It sounds like the initialization needing a fallback of some sort to then go to the next step and get to the bootloader.

I was quickly retrying and did not see/reproduce that slowdown in the bootloader.
It passes that stage rather quick, let us say ~1 second.

I didn't care about the later system to work (no PW setting or such), just a cmdline to see how fast it would boot (initialize, boot-load, kernel, complete system boot), the command I ran was:

$ sudo qemu-system-x86_64 -m 1G -cpu host -smp 2 -machine accel=kvm,type=q35 -drive file=/tmp/ubuntu-22.04-server-cloudimg-amd64.img,if=virtio,format=qcow2 -nographic

I tried the above 1:6.2+dfsg-2ubuntu6.17 in Ubuntu Jammy, as well 1:8.2.2+ds-1 in Debian sid and 1:7.2+dfsg-7+deb12u5 in Debian bookworm. They are all fast with the 22.04 image you referred to.

I used that commandline to - for now - to avoid having to look for well meant distracting magic of libvirt or other higher level things. I see nothing super special in my commandline nor can I see the issue.
Hence I need to ask you which command or tooling config did you use to start the guest when you see the difference in boot speed?