2 files changed, 51 insertions, 0 deletions
diff --git a/results/classifier/108/other/1287 b/results/classifier/108/other/1287
new file mode 100644
index 00000000..da493449
--- /dev/null
+++ b/results/classifier/108/other/1287
@@ -0,0 +1,25 @@
+device: 0.799
+graphic: 0.686
+other: 0.638
+performance: 0.605
+network: 0.457
+permissions: 0.452
+debug: 0.440
+semantic: 0.423
+boot: 0.354
+socket: 0.275
+vnc: 0.219
+PID: 0.212
+files: 0.066
+KVM: 0.044
+
+qemu-img info foo.qcow2 tries to get write lock
+Description of problem:
+When trying to run qemu-img info on an image which is used by QEMU qemu-img tries to acquire a write lock. Ideally this would not attempt to acquire a write lock and let qemu-img info succeed.
+```
+[jelle@t14s][/tmp]%qemu-img info /var/tmp/cockpit-qr_j3e_m.qcow2
+qemu-img: Could not open '/var/tmp/cockpit-qr_j3e_m.qcow2': Failed to get shared "write" lock
+Is another process using the image [/var/tmp/cockpit-qr_j3e_m.qcow2]?
+```
+Steps to reproduce:
+1. Run qemu-img on an image used by a QEMU process.
diff --git a/results/classifier/108/other/1287195 b/results/classifier/108/other/1287195
new file mode 100644
index 00000000..82fd7ab9
--- /dev/null
+++ b/results/classifier/108/other/1287195
@@ -0,0 +1,26 @@
+device: 0.792
+socket: 0.671
+files: 0.660
+vnc: 0.658
+network: 0.632
+permissions: 0.551
+PID: 0.541
+boot: 0.512
+other: 0.489
+graphic: 0.419
+semantic: 0.389
+debug: 0.328
+performance: 0.271
+KVM: 0.176
+
+validate_guest_space incorrectly enabled on AArch64
+
+When running linux-user targetting AArch64, validate_guest_space() in elfload.c reserves space in the guest address space for the ARM commpage. Since there is no commpage on AArch64, this function should be disable on that target.
+
+Thanks for the bug report -- I've just submitted this patch which should fix this:
+  http://patchwork.ozlabs.org/patch/328565/
+
+
+Fix will be in 2.0.
+
+