blob: 22449eb475e48f9c4f4f35a44e4a28bdba067602 (
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
57
58
59
60
61
62
63
64
65
66
67
68
69
|
x86: 0.726
i386: 0.701
kernel: 0.592
KVM: 0.450
device: 0.406
ppc: 0.380
debug: 0.338
socket: 0.337
semantic: 0.331
boot: 0.317
graphic: 0.311
network: 0.303
mistranslation: 0.266
register: 0.261
VMM: 0.248
architecture: 0.236
risc-v: 0.227
performance: 0.225
files: 0.208
PID: 0.205
assembly: 0.204
virtual: 0.190
vnc: 0.189
user-level: 0.181
arm: 0.173
hypervisor: 0.153
permissions: 0.127
TCG: 0.112
peripherals: 0.096
[Feature request] x86: dump MSR features in human form
QEMU might fail because host/guest cpu features are not properly configured:
qemu-system-x86_64: error: failed to set MSR 0x48f to 0x7fefff00036dfb
qemu-system-x86_64: /root/qemu-master/target/i386/kvm.c:2695:
kvm_buf_set_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
To ease debugging, it the MSR features bit could be dumped.
Example in this thread:
https://lists.gnu.org/archive/html/qemu-devel/2020-05/msg05593.html
The high 32 bits are 0111 1111 1110 1111 1111 1111.
The low 32 bits are 0000 0011 0110 1101 1111 1011.
The features that are set are the xor, so 0111 1100 1000 0010 0000 0100:
- bit 2, vmx-exit-nosave-debugctl
- bit 9, host address space size, is handled automatically by QEMU
- bit 15, vmx-exit-ack-intr
- bit 17, vmx-exit-save-pat
- bit 18, vmx-exit-load-pat
- bit 19, vmx-exit-save-efer
- bit 20, vmx-exit-load-efer
- bit 21, vmx-exit-save-preemption-timer
This output ^^^ is easier to digest.
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'invalid' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/237
|