1 files changed, 50 insertions, 0 deletions
diff --git a/results/classifier/118/virtual/2393 b/results/classifier/118/virtual/2393
new file mode 100644
index 000000000..a1d2bfa7c
--- /dev/null
+++ b/results/classifier/118/virtual/2393
@@ -0,0 +1,50 @@
+virtual: 0.991
+performance: 0.932
+semantic: 0.874
+boot: 0.872
+x86: 0.855
+graphic: 0.849
+architecture: 0.849
+kernel: 0.829
+device: 0.771
+ppc: 0.730
+hypervisor: 0.729
+vnc: 0.700
+user-level: 0.699
+PID: 0.654
+VMM: 0.568
+socket: 0.543
+KVM: 0.535
+register: 0.532
+network: 0.512
+permissions: 0.500
+peripherals: 0.479
+mistranslation: 0.461
+assembly: 0.460
+files: 0.442
+risc-v: 0.433
+arm: 0.412
+TCG: 0.407
+i386: 0.382
+debug: 0.320
+
+qemu: seabios hangs for 10~15 sec at boot with `-machine q35`
+Description of problem:
+Whenever i'm starting a virtual machine i'm having the issue that seabios (or at least that's what i see) hangs for about 10~15 seconds. In that time on of the cpu cores runs at 100%.
+This issue isn't new actually. I'm having this already for quite some time and a i think for at least the last 2 major versions. I haven't looked into it since it isn't a big issue, just annoying.
+Today i've looked into it and as far as i can see, this issue is always present with the flag `-machine q35`, which is the default for my vm's. If i set it to `-machine pc`, booting works as expected. However i also found a "workaround" where the vm's starting immediately (with `-machine q35` enabled), which is by simply adding a iso image to the command line (via -cdrom) - even though it's not used.
+
+This means:
+- 15 sec delay: qemu-system-x86_64 -machine q35
+- works immediately: qemu-system-x86_64 -machine q35 -cdrom /mnt/data/vm/isos/openSUSE-Tumbleweed-DVD-x86_64-Snapshot20230303-Media.iso
+
+Please note that most of my vm's usually start booting from a kernel image directly (-kernel /mnt/data/vm/kernel/gentoo-latest -initrd /mnt/data/vm/kernel/initrd-v5.cpio.gz) - but even in that case settings a cdrom (image) would fix the issue.
+Also, the image needs to be a valid one, if i set an empty file or /dev/null the issue would remain.
+Further more, i have the same issue on a second computer. This also runs on Gentoo Linux and is also a AMD Ryzen. (in case this is relevant)
+Steps to reproduce:
+1. qemu-system-x86_64 -machine q35
+2. wait about 10-15sec before boot continues
+Additional information:
+I was thinking to add an Screenshot of the hanging boot process, but the only text written there is:
+SeaBIOS (version 1.16.0-20220807_005459-localhost)
+with a blinking cursor below