2 files changed, 85 insertions, 0 deletions
diff --git a/results/classifier/108/other/1524 b/results/classifier/108/other/1524
new file mode 100644
index 000000000..f620c8947
--- /dev/null
+++ b/results/classifier/108/other/1524
@@ -0,0 +1,52 @@
+device: 0.695
+graphic: 0.678
+KVM: 0.535
+vnc: 0.491
+PID: 0.462
+semantic: 0.447
+performance: 0.368
+debug: 0.363
+socket: 0.338
+network: 0.332
+files: 0.256
+permissions: 0.192
+boot: 0.145
+other: 0.042
+
+error while loading state for instance 0x0 of device 'kvm-tpr-opt',load of migration failed: Operation not permitted
+Description of problem:
+when i save and restore a guest,it report the error: "error while loading state for instance 0x0 of device 'kvm-tpr-opt',load of migration failed: Operation not permitted"
+Steps to reproduce:
+1.virsh save test ccc.img
+
+2.virsh restore ccc.im
+
+
+it report error:
+
+[root@TOS-9772 ~]# virsh save test ccc.img
+
+[root@TOS-9772 ~]# virsh restore ccc.img
+
+error: Failed to restore domain from ccc.img
+
+error: internal error: qemu unexpectedly closed the monitor: qmp_cmd_name: query-hotpluggable-cpus, arguments: {}
+
+qmp_cmd_name: query-cpus-fast, arguments: {}
+
+qmp_cmd_name: query-iothreads, arguments: {}
+
+qmp_cmd_name: expire_password, arguments: {"protocol": "spice", "time": "never"}
+
+qmp_cmd_name: balloon, arguments: {"value": 1073741824}
+
+qmp_cmd_name: migrate-incoming, arguments: {"uri": "fd:29"}
+
+{"timestamp": {"seconds": 1677661413, "microseconds": 275227}, "event": "MIGRATION", "data": {"status": "setup"}}
+
+{"timestamp": {"seconds": 1677661413, "microseconds": 275600}, "event": "MIGRATION", "data": {"status": "active"}}
+
+2023-03-01T09:03:33.316549Z qemu-system-x86_64: error while loading state for instance 0x0 of device 'kvm-tpr-opt'
+
+2023-03-01T09:03:33.317076Z qemu-system-x86_64: load of migration failed: Operation not permitted
+{"timestamp": {"seconds": 1677661413, "microseconds": 317297}, "event": "MIGRATION", "data": {"status": "failed"}}
diff --git a/results/classifier/108/other/1524637 b/results/classifier/108/other/1524637
new file mode 100644
index 000000000..8e8d1cc33
--- /dev/null
+++ b/results/classifier/108/other/1524637
@@ -0,0 +1,33 @@
+device: 0.805
+graphic: 0.727
+semantic: 0.679
+permissions: 0.631
+socket: 0.449
+files: 0.430
+performance: 0.428
+other: 0.411
+network: 0.411
+debug: 0.362
+vnc: 0.352
+KVM: 0.302
+PID: 0.298
+boot: 0.179
+
+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".
+