summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/kvm/391879
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
commitd0c85e36e4de67af628d54e9ab577cc3fad7796a (patch)
treef8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/gemma3:12b/kvm/391879
parent7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
downloadqemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/kvm/391879')
-rw-r--r--results/classifier/gemma3:12b/kvm/39187925
1 files changed, 25 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/kvm/391879 b/results/classifier/gemma3:12b/kvm/391879
new file mode 100644
index 000000000..bbdc5037b
--- /dev/null
+++ b/results/classifier/gemma3:12b/kvm/391879
@@ -0,0 +1,25 @@
+
+migrate exec ignores exit status
+
+Binary package hint: kvm
+
+Using
+
+  migrate "exec:cat > foo; false"
+
+in the monitor results in the state of the VM being written to foo, as expected, and the VM then being stopped. This is surprising, as I think it stands to reason that in case of a failed migrate-exec process, which is what a non-zero exit status implies to me, the VM should continue.
+
+== Version information
+
+$ lsb_release -rd
+Description:	Ubuntu 9.04
+Release:	9.04
+
+$ apt-cache policy kvm
+kvm:
+  Installed: 1:84+dfsg-0ubuntu11
+  Candidate: 1:84+dfsg-0ubuntu11
+  Version table:
+ *** 1:84+dfsg-0ubuntu11 0
+        500 http://gb.archive.ubuntu.com jaunty/main Packages
+        100 /var/lib/dpkg/status
\ No newline at end of file