1 files changed, 48 insertions, 0 deletions
diff --git a/results/classifier/118/device/1524637 b/results/classifier/118/device/1524637
new file mode 100644
index 000000000..5c475be15
--- /dev/null
+++ b/results/classifier/118/device/1524637
@@ -0,0 +1,48 @@
+device: 0.805
+kernel: 0.786
+architecture: 0.737
+x86: 0.730
+graphic: 0.727
+semantic: 0.679
+mistranslation: 0.648
+permissions: 0.631
+socket: 0.449
+files: 0.430
+performance: 0.428
+ppc: 0.421
+network: 0.411
+virtual: 0.406
+peripherals: 0.400
+register: 0.396
+arm: 0.388
+risc-v: 0.383
+hypervisor: 0.369
+i386: 0.363
+debug: 0.362
+user-level: 0.355
+vnc: 0.352
+KVM: 0.302
+PID: 0.298
+TCG: 0.265
+VMM: 0.264
+boot: 0.179
+assembly: 0.178
+
+system_powerdown/system_reset not working when exec stop on hmp
+
+system_powerdown/system_reset stops working in qemu for centos kernels if KVM is enabled.
+
+qemu versioin: 2.4
+linux kernel versioin: 4.2.5
+
+How to reproduce:
+
+1. qemu-system-x86_64 -enable-kvm -drive if=none,id=drive0,file=/media/sda5/image/fc21/fc21.raw -device virtio-blk-pci,drive=drive0,iothread=iothread0 -machine smm=off -object iothread,id=iothread0 -monitor stdio
+2. Enter stop in the qemu console, we can see the vm is stopped.
+3. Enter system_powerdown in the qemu console
+4. Nothing happens.
+
+Can you please give a prompt or something else when the vm isn't allowed to powerdown or reset?
+
+Looking through old bug tickets ... I don't think this was really a bug. If you stop your guest, of course the guest operating system can not powerdown anymore. It should powerdown once you resume your guest with "cont".
+