hvf accelerator crashes on quest boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QEMU |
Expired
|
Undecided
|
Unassigned |
Bug Description
Host OS: macOS High Sierra (10.13.6)
MacBook Pro (Retina, Mid 2015)
Processor: 2.8GHz Intel Core i7
Guest OS: OpenBSD 6.4 install media (install64.iso)
Qemu 3.1.0 release, built with:
./configure --prefix=
-
-
-
-
-
--enable-vde
-
-
--disable-sdl
--disable-gtk
--enable-hvf
-
-
I invoke qemu like this:
Last command had exit code: 0 at 22:58
nwallace@
$ sudo qemu-system-x86_64 -M accel=hvf -boot d -cdrom ~/Downloads/
Password:
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H
bad size
Abort trap: 6
Last command had exit code: 134 at 22:58
nwallace@
$
I ran qemu in lldb to get a stack trace and I get:
Last command had exit code: 0 at 22:54
nwallace@
$ sudo lldb -- qemu-system-x86_64 -M accel=hvf -boot d -cdrom /Users/
Password:
(lldb) target create "qemu-system-
Current executable set to 'qemu-system-
(lldb) settings set -- target.run-args "-M" "accel=hvf" "-boot" "d" "-cdrom" "/Users/
so"
(lldb) run
Process 96474 launched: '/usr/local/
Process 96474 stopped
* thread #1, queue = 'com.apple.
frame #0: 0x00007fff5ef0c00a libsystem_
libsystem_
-> 0x7fff5ef0c00a <+10>: jae 0x7fff5ef0c014 ; <+20>
0x7fff5ef0c00c <+12>: movq %rax, %rdi
0x7fff5ef0c00f <+15>: jmp 0x7fff5ef02b0e ; cerror
0x7fff5ef0c014 <+20>: retq
Target 0: (qemu-system-
(lldb) process handle SIGUSR1 -n true -p true -s false
NAME PASS STOP NOTIFY
=========== ===== ===== ======
SIGUSR1 true false true
(lldb) process handle SIGUSR2 -n true -p true -s false
NAME PASS STOP NOTIFY
=========== ===== ===== ======
SIGUSR2 true false true
(lldb) c
Process 96474 resuming
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H
Process 96474 stopped and restarted: thread 9 received signal: SIGUSR2
<line above repeats about 64 times or so>
Process 96474 stopped and restarted: thread 9 received signal: SIGUSR2
bad size
Process 96474 stopped
* thread #9, stop reason = signal SIGABRT
frame #0: 0x00007fff5ef0bb66 libsystem_
libsystem_
-> 0x7fff5ef0bb66 <+10>: jae 0x7fff5ef0bb70 ; <+20>
0x7fff5ef0bb68 <+12>: movq %rax, %rdi
0x7fff5ef0bb6b <+15>: jmp 0x7fff5ef02ae9 ; cerror_nocancel
0x7fff5ef0bb70 <+20>: retq
Target 0: (qemu-system-
(lldb) bt
* thread #9, stop reason = signal SIGABRT
* frame #0: 0x00007fff5ef0bb66 libsystem_
frame #1: 0x00007fff5f0d6080 libsystem_
frame #2: 0x00007fff5ee671ae libsystem_
frame #3: 0x000000010016b6ec qemu-system-
frame #4: 0x000000010016ada4 qemu-system-
frame #5: 0x0000000100169aaa qemu-system-
frame #6: 0x0000000100164eb2 qemu-system-
frame #7: 0x000000010005bed6 qemu-system-
frame #8: 0x00000001003ee531 qemu-system-
frame #9: 0x00007fff5f0d3661 libsystem_
frame #10: 0x00007fff5f0d350d libsystem_
frame #11: 0x00007fff5f0d2bf9 libsystem_
(lldb) quit
Quitting LLDB will kill one or more processes. Do you really want to proceed: [Y/n] Y
Last command had exit code: 0 at 23:01
nwallace@
$
I'm happy to work with someone more knowledgeable to reproduce this issue and provide debugging assistance as I'm able.
Looking through old bug tickets... is this still an issue with the latest version of QEMU? Or could we close this ticket nowadays?