blob: c4a9d31ac509791281f4a3e9ae49eb9d90fc8e6d (
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
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
|
KVM: 0.818
mistranslation: 0.788
virtual: 0.774
graphic: 0.763
hypervisor: 0.744
debug: 0.738
semantic: 0.695
i386: 0.610
device: 0.570
ppc: 0.550
kernel: 0.516
performance: 0.488
x86: 0.460
peripherals: 0.437
architecture: 0.433
vnc: 0.431
socket: 0.424
network: 0.421
PID: 0.404
boot: 0.374
permissions: 0.365
risc-v: 0.348
register: 0.340
files: 0.340
VMM: 0.327
arm: 0.281
TCG: 0.234
user-level: 0.233
assembly: 0.122
When a break point is set, nested virtualization sees "kvm_queue_exception: Assertion `!env->exception_has_payload' failed."
Description of problem:
I am debugging XMHF and LHV using QEMU + KVM. I found that if I set a break point using GDB, QEMU will crash when LHV is booting. The message is
```
qemu-system-i386: ../../../target/i386/kvm/kvm.c:678: kvm_queue_exception: Assertion `!env->exception_has_payload' failed.
```
The address of the break point is arbitrary. The break point does not need to hit. So I chose 0 as the address in this bug report.
Steps to reproduce:
1. Start QEMU using `qemu-system-i386 -m 512M -gdb tcp::1234 -smp 2 -cpu Haswell,vmx=yes -enable-kvm -serial stdio -drive media=disk,file=1.img,index=1 -drive media=disk,file=2.img,index=2 -S`
2. In another shell, start GDB using `gdb --ex 'target remote :::1234' --ex 'hb *0' --ex c`
3. See many serial output lines. The tail of the output is
```
CPU #0: vcpu_vaddr_ptr=0x01e06080, esp=0x01e11000
CPU #1: vcpu_vaddr_ptr=0x01e06540, esp=0x01e15000
BSP(0x00): Rallying APs...
BSP(0x00): APs ready, doing DRTM...
LAPIC base and status=0xfee00900
Sending INIT IPI to all APs...
```
4. See assertion error in QEMU
```
qemu-system-i386: ../target/i386/kvm/kvm.c:645: kvm_queue_exception: Assertion `!env->exception_has_payload' failed.
```
Additional information:
This bug was first incorrectly filed in KVM's bug tracker at <https://bugzilla.kernel.org/show_bug.cgi?id=216002>.
|