13 files changed, 330 insertions, 0 deletions
diff --git a/results/classifier/108/other/53 b/results/classifier/108/other/53
new file mode 100644
index 000000000..90f3ad771
--- /dev/null
+++ b/results/classifier/108/other/53
@@ -0,0 +1,16 @@
+device: 0.879
+other: 0.692
+vnc: 0.410
+boot: 0.394
+performance: 0.316
+debug: 0.297
+graphic: 0.275
+semantic: 0.271
+permissions: 0.268
+PID: 0.267
+socket: 0.146
+KVM: 0.096
+network: 0.082
+files: 0.034
+
+RISC-V Disassembler/translator instruction decoding disagreement
diff --git a/results/classifier/108/other/530 b/results/classifier/108/other/530
new file mode 100644
index 000000000..9fff74a3d
--- /dev/null
+++ b/results/classifier/108/other/530
@@ -0,0 +1,58 @@
+graphic: 0.905
+boot: 0.889
+debug: 0.847
+semantic: 0.836
+socket: 0.807
+device: 0.790
+KVM: 0.773
+files: 0.743
+permissions: 0.736
+PID: 0.730
+performance: 0.727
+other: 0.713
+vnc: 0.699
+network: 0.467
+
+Invalid guest state when rebooting a nesting hypervisor
+Description of problem:
+On a standard Linux machine, I run a custom hypervisor stack based on [Hedron](https://github.com/cyberus-technology/hedron) in a qemu VM with nesting capabilities. The Hedron stack starts a nested Linux guest with complete pass-through of all resources not required for virtualizing the nested guest. In particular, ACPI and PCI including the reset functionality are directly accessible to the nested guest. As soon as the nested guest issues a machine reset, I get a hardware error with the following error message:
+
+<details><summary>KVM: entry failed, hardware error 0x80000021</summary>
+<pre>
+If you're running a guest on an Intel machine without unrestricted mode
+support, the failure can be most likely due to the guest entering an invalid
+state for Intel VT. For example, the guest maybe running in big real mode
+which is not supported on less recent Intel processors.
+
+EAX=00000000 EBX=00000000 ECX=00000000 EDX=00050657
+ESI=00000000 EDI=00000000 EBP=00000000 ESP=00000000
+EIP=0000fff0 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0
+ES =0000 00000000 0000ffff 00009300
+CS =f000 ffff0000 0000ffff 00009b00
+SS =0000 00000000 0000ffff 00009300
+DS =0000 00000000 0000ffff 00009300
+FS =0000 00000000 0000ffff 00009300
+GS =0000 00000000 0000ffff 00009300
+LDT=0000 00000000 0000ffff 00008200
+TR =0000 00000000 0000ffff 00008b00
+GDT=     00000000 0000ffff
+IDT=     00000000 0000ffff
+CR0=60000010 CR2=00000000 CR3=00000000 CR4=003726f8
+DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
+DR6=00000000ffff0ff0 DR7=0000000000000400
+EFER=0000000000000000
+</pre>
+</details>
+
+If I'm not mistaken, the CR4 value of `0x003726f8` is the offending state here, because PCIDE (bit 17) is set, even though the arch state indicates real-mode and the Intel SDM states:
+
+> If the “IA-32e mode guest” VM-entry control is 0, bit 17 in the CR4 field (corresponding to CR4.PCIDE) must be 0.
+
+Furthermore, the issue is not present when not using PCID in the L1 hypervisor or when PCID/VPID are fused out using `qemu-kvm -cpu host,-pcid,-vmx-vpid,-vmx-invpcid-exit`.
+Steps to reproduce:
+1. Boot custom hypervisor stack (unfortunately not yet publicly available, I'm working on that)
+2. In nested Linux guest, type `reboot`, which eventually directly reboots the main VM (all main VM hardware is passed through to the single nested guest)
+Additional information:
+I have tracked down the [change](https://gitlab.com/qemu/qemu/-/commit/b16c0e20c74218f2d69710cedad11da7dd4d2190#063d8f78716c7a658841a1d51cc66bf30f697082_3920_3944) that likely introduced this issue. Moving the call to `kvm_put_sregs` back down (I suspect after `kvm_put_nested_state`, but I did not verify that yet) solves the reboot issue for me. The comment makes it clear that it is important to keep a certain order here, so I'm aware just reversing it is not an option.
+
+Maybe this already helps enough to figure out what exactly the issue and correct fix is, and I am happy to try any suggestions as long as I cannot provide a proper reproducer.
diff --git a/results/classifier/108/other/530077 b/results/classifier/108/other/530077
new file mode 100644
index 000000000..20035c657
--- /dev/null
+++ b/results/classifier/108/other/530077
@@ -0,0 +1,31 @@
+KVM: 0.898
+graphic: 0.810
+device: 0.589
+semantic: 0.536
+boot: 0.533
+performance: 0.484
+other: 0.415
+socket: 0.359
+network: 0.350
+permissions: 0.296
+vnc: 0.281
+debug: 0.250
+PID: 0.230
+files: 0.202
+
+kvm: 16-bit code execution failure should be more friendly
+
+Today, when kvm fails at 16-bit code execution, we report:
+
+     spirit:~/qemu> qemu-kvm ./hda-fedora.img 
+     kvm: unhandled exit 80000021
+     kvm_run returned -22
+
+There are three reasons exit reason 21 happens.  The first is that a user is executing an image containing a workload that uses GFXBOOT or some other bootloader that exercises big real mode.  On pre-Westmere Intel processors, VT could not handle big real mode.  The second reason is that the guest's image is corrupted and we're executing random code.  We accidentally fall into one of the unsupported modes for VT.  Again, this is addressed on WSM.  The third case is where there's an actual bug in KVM.  This should be exceedingly rare at this stage.
+
+We should present a friendly error message explaining the possible causes and recommending corrective action.
+
+Triaging old bug tickets... has this ever been fixed, thus could we close this ticket nowadays? Or is there something left to do here?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/108/other/531 b/results/classifier/108/other/531
new file mode 100644
index 000000000..45a61eb76
--- /dev/null
+++ b/results/classifier/108/other/531
@@ -0,0 +1,16 @@
+performance: 0.848
+device: 0.827
+network: 0.755
+socket: 0.626
+vnc: 0.551
+graphic: 0.496
+boot: 0.493
+semantic: 0.369
+other: 0.352
+debug: 0.329
+KVM: 0.320
+permissions: 0.293
+PID: 0.227
+files: 0.212
+
+Replace DMA processing in I/O handlers by asynchronous BH
diff --git a/results/classifier/108/other/532 b/results/classifier/108/other/532
new file mode 100644
index 000000000..fd5c69f02
--- /dev/null
+++ b/results/classifier/108/other/532
@@ -0,0 +1,16 @@
+device: 0.886
+network: 0.830
+socket: 0.654
+performance: 0.617
+graphic: 0.510
+boot: 0.446
+semantic: 0.314
+debug: 0.222
+files: 0.174
+vnc: 0.162
+permissions: 0.140
+PID: 0.104
+KVM: 0.098
+other: 0.071
+
+USB-EHCI: Replace DMA processing in I/O handlers by asynchronous BH
diff --git a/results/classifier/108/other/533 b/results/classifier/108/other/533
new file mode 100644
index 000000000..da783d6ba
--- /dev/null
+++ b/results/classifier/108/other/533
@@ -0,0 +1,16 @@
+network: 0.830
+debug: 0.792
+performance: 0.661
+device: 0.604
+graphic: 0.384
+semantic: 0.283
+boot: 0.215
+vnc: 0.157
+PID: 0.044
+socket: 0.037
+permissions: 0.024
+other: 0.024
+files: 0.022
+KVM: 0.016
+
+Assertion failure in vmxnet3_get_next_body_rx_descr: d->btype == VMXNET3_RXD_BTYPE_BODY
diff --git a/results/classifier/108/other/533613 b/results/classifier/108/other/533613
new file mode 100644
index 000000000..77173277e
--- /dev/null
+++ b/results/classifier/108/other/533613
@@ -0,0 +1,81 @@
+device: 0.770
+network: 0.717
+socket: 0.705
+performance: 0.702
+permissions: 0.683
+graphic: 0.679
+vnc: 0.676
+PID: 0.647
+KVM: 0.638
+files: 0.632
+boot: 0.607
+debug: 0.551
+other: 0.450
+semantic: 0.430
+
+fr-ca keymap is wrong
+
+The fr-ca keymap has tons of wrong keys in it, it affects other projects using Qemu/KVM like Xen.
+Documentation about how to make a keymap is too vague to allow me to make something useful to send a patch, I was however able to make something which at least allows me to use important keys like dot and slash, I will attach it for reference.
+
+
+
+Cc: <email address hidden>
+Cc: Thomas Huth <email address hidden>
+Suggested-by: Jérôme Poulin
+Signed-off-by: Gerd Hoffmann <email address hidden>
+---
+ pc-bios/keymaps/fr-ca | 14 +++++++++++---
+ 1 file changed, 11 insertions(+), 3 deletions(-)
+
+diff --git a/pc-bios/keymaps/fr-ca b/pc-bios/keymaps/fr-ca
+index 030f56a78e..2e540d596c 100644
+--- a/pc-bios/keymaps/fr-ca
++++ b/pc-bios/keymaps/fr-ca
+@@ -3,6 +3,8 @@
+ include common
+ map 0xc0c
+ 
++numbersign 0x29
++bar 0x29
+ backslash 0x29 altgr
+ plusminus 0x2 altgr
+ at 0x3 altgr
+@@ -10,7 +12,6 @@ sterling 0x4 altgr
+ cent 0x5 altgr
+ currency 0x6 altgr
+ notsign 0x7 altgr
+-bar 0x29 shift
+ twosuperior 0x9 altgr
+ threesuperior 0xa altgr
+ onequarter 0xb altgr
+@@ -38,6 +39,10 @@ dead_cedilla 0x1b
+ dead_diaeresis 0x1b shift
+ exclam 0x2 shift
+ quotedbl 0x3 shift
++comma 0x33
++apostrophe 0x33 shift
++period 0x34
++period 0x34 shift
+ slash 0x4 shift
+ dollar 0x5 shift
+ percent 0x6 shift
+@@ -48,5 +53,8 @@ parenleft 0xa shift
+ parenright 0xb shift
+ underscore 0xc shift
+ plus 0xd shift
+-minus 0xc
+-equal 0xd
++minus 0x0c
++underscore 0x0c shift
++equal 0x0d
++semicolon 0x27
++colon 0x27 shift
+-- 
+2.9.3
+
+
+
+Patch has finally been included here:
+http://git.qemu.org/?p=qemu.git;a=commitdiff;h=b02cf99b9d998b3ec23dae8
+
diff --git a/results/classifier/108/other/534 b/results/classifier/108/other/534
new file mode 100644
index 000000000..3c2f97398
--- /dev/null
+++ b/results/classifier/108/other/534
@@ -0,0 +1,16 @@
+performance: 0.822
+device: 0.804
+graphic: 0.396
+network: 0.378
+boot: 0.214
+debug: 0.158
+vnc: 0.151
+KVM: 0.094
+semantic: 0.092
+other: 0.070
+socket: 0.043
+files: 0.036
+PID: 0.032
+permissions: 0.029
+
+Memcpy param-overlap through e1000e_write_to_rx_buffers
diff --git a/results/classifier/108/other/535 b/results/classifier/108/other/535
new file mode 100644
index 000000000..b00350ebf
--- /dev/null
+++ b/results/classifier/108/other/535
@@ -0,0 +1,16 @@
+device: 0.877
+performance: 0.779
+graphic: 0.648
+debug: 0.619
+network: 0.442
+boot: 0.208
+semantic: 0.208
+KVM: 0.136
+vnc: 0.084
+PID: 0.052
+files: 0.031
+socket: 0.030
+permissions: 0.021
+other: 0.015
+
+Assertion failure in iov_from_buf_full through the e1000e
diff --git a/results/classifier/108/other/536 b/results/classifier/108/other/536
new file mode 100644
index 000000000..0bf282b5e
--- /dev/null
+++ b/results/classifier/108/other/536
@@ -0,0 +1,16 @@
+performance: 0.719
+device: 0.689
+debug: 0.610
+graphic: 0.532
+network: 0.240
+semantic: 0.135
+boot: 0.120
+other: 0.076
+vnc: 0.046
+permissions: 0.022
+socket: 0.018
+PID: 0.012
+KVM: 0.009
+files: 0.006
+
+Null-ptr dereference in ich9_apm_ctrl_changed
diff --git a/results/classifier/108/other/537 b/results/classifier/108/other/537
new file mode 100644
index 000000000..f61dfdbea
--- /dev/null
+++ b/results/classifier/108/other/537
@@ -0,0 +1,16 @@
+device: 0.821
+performance: 0.764
+debug: 0.632
+graphic: 0.542
+network: 0.324
+boot: 0.222
+semantic: 0.203
+vnc: 0.132
+KVM: 0.090
+other: 0.050
+socket: 0.049
+PID: 0.049
+files: 0.020
+permissions: 0.011
+
+Assertion failure in e1000e_write_to_rx_buffers
diff --git a/results/classifier/108/other/538 b/results/classifier/108/other/538
new file mode 100644
index 000000000..c7e433894
--- /dev/null
+++ b/results/classifier/108/other/538
@@ -0,0 +1,16 @@
+device: 0.857
+performance: 0.624
+graphic: 0.336
+debug: 0.152
+semantic: 0.138
+boot: 0.076
+other: 0.054
+KVM: 0.031
+PID: 0.020
+permissions: 0.015
+network: 0.012
+vnc: 0.008
+socket: 0.003
+files: 0.001
+
+Memory Leak in hpet_timer results in unusable machine
diff --git a/results/classifier/108/other/539 b/results/classifier/108/other/539
new file mode 100644
index 000000000..8cc3447e3
--- /dev/null
+++ b/results/classifier/108/other/539
@@ -0,0 +1,16 @@
+network: 0.872
+device: 0.836
+performance: 0.703
+graphic: 0.317
+semantic: 0.293
+socket: 0.105
+debug: 0.062
+boot: 0.052
+PID: 0.049
+other: 0.046
+vnc: 0.035
+permissions: 0.016
+files: 0.012
+KVM: 0.006
+
+Abort in vmxnet3_validate_interrupt_idx