summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/hypervisor/975
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/hypervisor/975
parent7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
downloadqemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/hypervisor/975')
-rw-r--r--results/classifier/gemma3:12b/hypervisor/97539
1 files changed, 39 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/hypervisor/975 b/results/classifier/gemma3:12b/hypervisor/975
new file mode 100644
index 000000000..e95f22854
--- /dev/null
+++ b/results/classifier/gemma3:12b/hypervisor/975
@@ -0,0 +1,39 @@
+
+LXD with QEMU 6.2.0 (and 7.0.0-rc3) breaks during stateful migration
+Description of problem:
+
+Steps to reproduce:
+```
+sudo snap install --lxd
+sudo lxd init --auto
+lxc init images:ubuntu/20.04/cloud v1 --vm
+Creating v1
+lxc config device override v1 root size.state=2GiB
+Device root overridden for v1
+lxc config set v1 migration.stateful=true
+lxc start v1
+sleep 10
+lxc exec v1 -- uptime
+ 22:05:54 up 0 min,  0 users,  load average: 0.07, 0.02, 0.00
+lxc snapshot v1 --stateful
+Error: Migration call failed
+lxc snapshot v1 --stateful
+Error: Monitor is disconnected
+```
+
+The first attempt at `lxc snapshot v1 --stateful` caused this in the `lxc info v1 --show-log` log output:
+
+```
+qemu-system-x86_64: qemu_savevm_state_complete_precopy_non_iterable: bdrv_inactivate_all() failed (-1)
+```
+
+The second attempt caused this:
+
+```
+qemu-system-x86_64: ../block.c:6757: bdrv_inactivate_recurse: Assertion `!(bs->open_flags & BDRV_O_INACTIVE)' failed.
+```
+
+Which crashed QEMU completely and caused the VM to die.
+Nothing relevant showed up in dmesg, so this wasn't caused by an obvious seccomp or apparmor policy issue.
+Additional information:
+Originally reported by Stephane Graber at https://github.com/lxc/lxd/issues/9875