summary refs log tree commit diff stats
path: root/results/classifier/118/permissions/1700380
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-16 16:59:00 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-06-16 16:59:33 +0000
commit9aba81d8eb048db908c94a3c40c25a5fde0caee6 (patch)
treeb765e7fb5e9a3c2143c68b0414e0055adb70e785 /results/classifier/118/permissions/1700380
parentb89a938452613061c0f1f23e710281cf5c83cb29 (diff)
downloademulator-bug-study-9aba81d8eb048db908c94a3c40c25a5fde0caee6.tar.gz
emulator-bug-study-9aba81d8eb048db908c94a3c40c25a5fde0caee6.zip
add 18th iteration of classifier
Diffstat (limited to 'results/classifier/118/permissions/1700380')
-rw-r--r--results/classifier/118/permissions/170038051
1 files changed, 51 insertions, 0 deletions
diff --git a/results/classifier/118/permissions/1700380 b/results/classifier/118/permissions/1700380
new file mode 100644
index 00000000..721d3662
--- /dev/null
+++ b/results/classifier/118/permissions/1700380
@@ -0,0 +1,51 @@
+permissions: 0.986
+x86: 0.952
+socket: 0.942
+network: 0.935
+virtual: 0.931
+register: 0.903
+PID: 0.897
+semantic: 0.884
+user-level: 0.880
+device: 0.878
+graphic: 0.869
+architecture: 0.858
+debug: 0.844
+mistranslation: 0.842
+performance: 0.830
+vnc: 0.822
+ppc: 0.737
+hypervisor: 0.652
+risc-v: 0.608
+arm: 0.607
+boot: 0.606
+TCG: 0.576
+VMM: 0.557
+i386: 0.539
+assembly: 0.533
+files: 0.531
+peripherals: 0.527
+KVM: 0.359
+kernel: 0.306
+
+commit snapshot image got Permission denied error
+
+qemu 2.9.0, adm64, start image with -snapshot param, make some changes in the image, then:
+
+$telnet localhost 7000
+
+(qemu) commit virtio0
+'commit' error for 'virtio0': Permission denied
+
+Nerver met this problem before, commit is ok. I recently compiled v2.9.0, so is there some new param in qemu-qemu-system-x86_64 to avoid commit Permission denied?
+
+Regards.
+
+only the winxp guest image get this error, linux guest do not.
+
+v2.9.0 must start the image with full path can commit the snapshot changes, <v2.3 no need to.
+
+close this report.
+
+Closing, according to comment #2
+