summary refs log tree commit diff stats
path: root/results/classifier/zero-shot-user-mode/instruction/1255
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-08 13:28:15 +0200
committerChristian Krinitsin <mail@krinitsin.com>2025-07-08 13:28:28 +0200
commit5aa276efcbd67f4300ca1a7f809c6e00aadb03da (patch)
tree9b8f0e074014cda8d42f5a97a95bc25082d8b764 /results/classifier/zero-shot-user-mode/instruction/1255
parent1a3c4faf4e0a25ed0b86e8739d5319a634cb9112 (diff)
downloadqemu-analysis-5aa276efcbd67f4300ca1a7f809c6e00aadb03da.tar.gz
qemu-analysis-5aa276efcbd67f4300ca1a7f809c6e00aadb03da.zip
restructure results
Diffstat (limited to 'results/classifier/zero-shot-user-mode/instruction/1255')
-rw-r--r--results/classifier/zero-shot-user-mode/instruction/125517
1 files changed, 17 insertions, 0 deletions
diff --git a/results/classifier/zero-shot-user-mode/instruction/1255 b/results/classifier/zero-shot-user-mode/instruction/1255
new file mode 100644
index 000000000..c4658610e
--- /dev/null
+++ b/results/classifier/zero-shot-user-mode/instruction/1255
@@ -0,0 +1,17 @@
+instruction: 0.680
+runtime: 0.179
+syscall: 0.141
+
+
+
+32bit qemu-arm fails to run systemctl "Allocating guest commpage: Cannot allocate memory"
+Description of problem:
+I am using a bare minimal install of the latest 32 bit version of debian with only ssh installed. I have compiled qemu from the latest git with "./configure --target-list=arm-linux-user --static --disable-pie". When I try to run systemctl from the latest version of raspbian, I experience the error: "Allocating guest commpage: Cannot allocate memory".
+Steps to reproduce:
+1. Download and extract the included systemctl and required libs. [systemctl+libs.tgz](/uploads/a2834ed651a981fded4bcc19ea9ca31b/systemctl+libs.tgz)
+2. run "qemu-arm -L ./ systemctl --version"
+Additional information:
+- I think this is related to [Issue 690](https://gitlab.com/qemu-project/qemu/-/issues/690).
+- When I run "qemu-arm -L ./ -B 0x20000 systemctl --version" there is no error.
+- The error still happens when setting vm.mmap_min_addr to 0.
+- The error does not occur on v5.0.0, but does occur on v5.1.0 and v6.1.0.