summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/105/graphic/2897
blob: ebb22e489d85a193243a1c48b7d0d11fc873d11a (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
graphic: 0.966
boot: 0.904
device: 0.847
instruction: 0.808
vnc: 0.667
semantic: 0.640
network: 0.497
mistranslation: 0.319
other: 0.314
socket: 0.232
KVM: 0.171
assembly: 0.118

Can't boot SeaBIOS based VM when using -display gtk, works fine with vnc or sdl
Description of problem:
When using -display gtk, SeaBIOS hangs nondeterministicly. Changing to -display sdl or -display vnc lets it boot.
Steps to reproduce:
1. Run `qemu-system-x86_64 -display gtk` and the VM will not complete BIOS POST.
2. Run `qemu-system-x86_64 -display sdl` and the VM will complete BIOS POST.
Additional information:
This ONLY happens with SeaBIOS. Using a UEFI BIOS to boot the VM does not cause this issue. 

I realise this is a crazy bug. I suspect that the only way it could have slipped through testing is because it *requires* human interaction.

There is no difference with using --accel kvm or not, but I have provided the smallest possible command line to duplicate the issue, which is literally just `qemu-system-x86_64 -display gtk`

#