1 files changed, 51 insertions, 0 deletions
diff --git a/results/classifier/118/device/1759492 b/results/classifier/118/device/1759492
new file mode 100644
index 000000000..59c22f205
--- /dev/null
+++ b/results/classifier/118/device/1759492
@@ -0,0 +1,51 @@
+device: 0.852
+graphic: 0.837
+virtual: 0.819
+mistranslation: 0.697
+semantic: 0.653
+user-level: 0.648
+performance: 0.638
+network: 0.566
+hypervisor: 0.561
+i386: 0.543
+peripherals: 0.515
+register: 0.509
+files: 0.508
+permissions: 0.505
+architecture: 0.492
+debug: 0.490
+vnc: 0.472
+risc-v: 0.470
+x86: 0.459
+ppc: 0.456
+PID: 0.443
+VMM: 0.439
+socket: 0.414
+boot: 0.385
+TCG: 0.362
+assembly: 0.328
+KVM: 0.312
+kernel: 0.303
+arm: 0.240
+
+suspend/resume is not supported for vm with tpm device
+
+I have used libvirt with qemu to create a vm with tpm device, when I suspend the vm and resume it, libvirt will
+raise error:
+libvirtError: internal error: process exited while connecting to monitor: Enter char_pty_open
+I find some materials:
+https://wiki.qemu.org/Features/TPM
+https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg05355.html
+They present qemu haven't supported tpm suspend/resume, Does someone have any advice on how to resolve the problem?
+
+qemu version: 2.10.2
+vm image version: centos 7.2
+
+Thanks
+
+The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
+If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+