2 files changed, 62 insertions, 0 deletions
diff --git a/results/classifier/108/other/690 b/results/classifier/108/other/690
new file mode 100644
index 00000000..3e9afe0b
--- /dev/null
+++ b/results/classifier/108/other/690
@@ -0,0 +1,34 @@
+other: 0.861
+device: 0.851
+graphic: 0.838
+performance: 0.774
+files: 0.767
+semantic: 0.720
+debug: 0.704
+permissions: 0.646
+PID: 0.632
+vnc: 0.621
+network: 0.605
+socket: 0.603
+boot: 0.521
+KVM: 0.086
+
+32bit qemu-arm can't run GCC due to failure to allocate memory range for guest (Allocating guest commpage error)
+Description of problem:
+I'm running ARM binaries using 32 bit qemu-arm-static on x86_64 host. Since version 5.1 (include latest 6.1), QEMU cannot run GCC and some other things with an error `Allocating guest commpage: Operation not permitted`. The problem is NOT reproducible on QEMU 5.0, so probably the problem was caused by a [rework of init_guest_space or the following commits](https://gitlab.com/qemu-project/qemu/-/commit/ee94743034bfb443cf246eda4971bdc15d8ee066) a year ago.
+
+Also the problem is not reproducible for all users. It is known that it is reproduced on all Arch Linux host machines and some Debian, and probably depends on some kernel build parameters.
+
+The sysctl `vm.mmap_min_addr` parameter also affects the problem. The error varies depending on its value:
+```
+[0 ... 53248] - No error at all
+[53249 ... 61440] - Cannot allocate memory
+[61441 ... 65536 and higher] - Operation not permitted
+```
+Steps to reproduce:
+1. Download and extract attached tarball: [qemu-test-gcc.tgz](/uploads/0031fdf6705183626f646b78a281dd2a/qemu-test-gcc.tgz)
+2. `$ make # will build the docker container`
+3. `$ make run # will enter the container`
+4. Once in the container, run: `# /qemu-arm-static-50 /bin/bash /runme.sh`
+Additional information:
+A detailed description of the problem and feedback from other users is here: https://bugs.launchpad.net/qemu/+bug/1891748
diff --git a/results/classifier/108/other/690776 b/results/classifier/108/other/690776
new file mode 100644
index 00000000..624fa64e
--- /dev/null
+++ b/results/classifier/108/other/690776
@@ -0,0 +1,28 @@
+graphic: 0.780
+semantic: 0.712
+performance: 0.703
+device: 0.695
+network: 0.600
+vnc: 0.591
+permissions: 0.588
+files: 0.570
+socket: 0.538
+debug: 0.534
+PID: 0.533
+other: 0.511
+KVM: 0.434
+boot: 0.415
+
+Overwrite argv to set process title, eliminating 16-character prctl() limit.
+
+I've modified qemu to overwrite its arguments to set the process title, since its current prctl() method has a 16-character limit.
+
+I posted the original patch to qemu-devel, made the changes others suggested, then re-posted to qemu-devel. I flailed around a bit with the patch submission process and think I finally got it right, but haven't been able to gain the notice of a committer to have this pushed. Maybe this will get more attention when reported in the BTS.
+
+
+
+The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
+If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.
+
+[Expired for QEMU because there has been no activity for 60 days.]
+