1 files changed, 51 insertions, 0 deletions
diff --git a/results/classifier/118/none/1616706 b/results/classifier/118/none/1616706
new file mode 100644
index 000000000..96533644b
--- /dev/null
+++ b/results/classifier/118/none/1616706
@@ -0,0 +1,51 @@
+virtual: 0.713
+device: 0.590
+mistranslation: 0.542
+semantic: 0.537
+performance: 0.531
+graphic: 0.488
+network: 0.455
+architecture: 0.422
+permissions: 0.410
+socket: 0.361
+KVM: 0.333
+hypervisor: 0.332
+risc-v: 0.313
+files: 0.309
+register: 0.309
+i386: 0.303
+vnc: 0.296
+boot: 0.286
+user-level: 0.284
+x86: 0.272
+PID: 0.271
+debug: 0.268
+arm: 0.262
+ppc: 0.254
+VMM: 0.208
+peripherals: 0.185
+kernel: 0.153
+TCG: 0.135
+assembly: 0.102
+
+watchdog doesn't bring down the VM
+
+Qemu-kvm version : QEMU emulator version 1.5.3 (qemu-kvm-1.5.3-105.el7), Copyright (c) 2003-2008 Fabrice Billard
+
+Qemu version: Virsh command line tool of libvirt 1.2.17
+
+I have the VM stuck in bios (efi shell), but i don't see the watchdog in the host bringing it down?
+
+Couple of questions:
+
+1. Does the watchdog functionality requires the driver in adminvm to trigger the reload? or qemu detects it in the host and causes the reload.
+
+2. Does this work reliably? I have seen cases where in i have the watchdog daemon in the VM shut, still don't see the VM going down (I put the action in the XML file as power off)
+
+Thanks
+Amit
+
+qemu-kvm-1.5.3-105.el7 isn't supported by the upstream community; if you need support with this Red Hat version, you'll have to go through Red Hat.
+
+The most recent version of qemu supported upstream is 2.6.1 and soon, 2.7.0.
+