summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/108/other/1341032
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/zero-shot/108/other/1341032')
-rw-r--r--results/classifier/zero-shot/108/other/134103227
1 files changed, 27 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/1341032 b/results/classifier/zero-shot/108/other/1341032
new file mode 100644
index 000000000..081b52762
--- /dev/null
+++ b/results/classifier/zero-shot/108/other/1341032
@@ -0,0 +1,27 @@
+graphic: 0.695
+performance: 0.506
+debug: 0.490
+device: 0.425
+semantic: 0.413
+network: 0.350
+boot: 0.256
+permissions: 0.200
+PID: 0.198
+other: 0.160
+socket: 0.149
+vnc: 0.140
+files: 0.139
+KVM: 0.059
+
+no-shutdown does not fire SHUTDOWN event for some guests
+
+Currently using: qemu-x86_64 version 2.0.0
+Steps to reproduce: Create virtual machine with the arguments -no-shutdown, such as used by libvirt. Attach to the json event system. Load a guest such as Ubuntu 14.04 and run the 'halt' command. Guest ceases to execute, qemu freezes CPUs however no SHUTDOWN event is fired to the monitor.
+
+Now load a guest such as finnix or Debian 7. Run the same sequence of steps and note that the SHUTDOWN event is fired to the monitor.
+
+This seems like a qemu bug as the execution of the guest has ceased.
+
+Thanks
+Michael
+