blob: 5930a10f888ddbddbe03e4d32383cb5cc7a5b35a (
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
28
29
|
graphic: 0.966
boot: 0.904
device: 0.847
performance: 0.677
vnc: 0.667
semantic: 0.640
debug: 0.543
network: 0.497
PID: 0.430
other: 0.314
permissions: 0.261
socket: 0.232
files: 0.216
KVM: 0.171
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`
#
|