1 files changed, 42 insertions, 0 deletions
diff --git a/results/classifier/118/virtual/1341032 b/results/classifier/118/virtual/1341032
new file mode 100644
index 000000000..167c8ce35
--- /dev/null
+++ b/results/classifier/118/virtual/1341032
@@ -0,0 +1,42 @@
+virtual: 0.814
+x86: 0.811
+graphic: 0.695
+architecture: 0.590
+performance: 0.506
+debug: 0.490
+device: 0.425
+semantic: 0.413
+network: 0.350
+mistranslation: 0.347
+boot: 0.256
+i386: 0.238
+VMM: 0.228
+hypervisor: 0.222
+permissions: 0.200
+PID: 0.198
+user-level: 0.166
+socket: 0.149
+register: 0.145
+vnc: 0.140
+files: 0.139
+peripherals: 0.130
+risc-v: 0.083
+kernel: 0.082
+TCG: 0.077
+ppc: 0.069
+KVM: 0.059
+arm: 0.051
+assembly: 0.008
+
+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
+