summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/network/589315
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/network/589315
parent7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
downloademulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/network/589315')
-rw-r--r--results/classifier/gemma3:12b/network/58931519
1 files changed, 19 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/network/589315 b/results/classifier/gemma3:12b/network/589315
new file mode 100644
index 00000000..fc1b6974
--- /dev/null
+++ b/results/classifier/gemma3:12b/network/589315
@@ -0,0 +1,19 @@
+
+qemu: Improve error reporting when migration can't connect
+
+Tested with upstream qemu as of Jun 3 2010
+
+If the source qemu instance can't connect to the migration destination (say
+there is no listening QEMU instance, or port is blocked by a firewall), all we
+get is info migrate -> Migration status: failed. This is all we have to report
+back to libvirt users if their firewall is misconfigured, which is crappy.
+
+Ideally, if we can't connect, migration would fail immediately with a relevant
+message and strerror(). More info from 'info migrate' would be nice too, no
+idea how this will play with QMP though.
+
+As a slightly related issue, try entering
+
+migrate tcp:127.0.0.0:6000
+
+We get a 'migration failed' error, and then the monitor hangs!
\ No newline at end of file