add 18th iteration of classifier

1 files changed, 36 insertions, 0 deletions

diff --git a/results/classifier/118/graphic/1040 b/results/classifier/118/graphic/1040
new file mode 100644
index 000000000..b5c819692
--- /dev/null
+++ b/results/classifier/118/graphic/1040
@@ -0,0 +1,36 @@
+graphic: 0.986
+device: 0.857
+performance: 0.826
+mistranslation: 0.818
+virtual: 0.816
+risc-v: 0.812
+socket: 0.799
+VMM: 0.785
+vnc: 0.760
+semantic: 0.758
+register: 0.734
+hypervisor: 0.719
+network: 0.716
+files: 0.665
+architecture: 0.636
+kernel: 0.615
+PID: 0.599
+arm: 0.569
+ppc: 0.525
+permissions: 0.518
+TCG: 0.505
+x86: 0.473
+debug: 0.448
+KVM: 0.434
+boot: 0.413
+i386: 0.413
+user-level: 0.342
+peripherals: 0.330
+assembly: 0.286
+
+Windows Server 2016 VM totally freezes spontaneously during the day a couple of times for 1-5 minutes. There is no any logs in it during the freeze
+Description of problem:
+Windows Server 2016 VM totally freezes spontaneously during the day a couple of times for 1-5 minutes. There is no any logs inside VM during the freeze. Timestamp of the last log written into journal is right before the freeze and the pretty next log is right after the freeze is gone. Looks like "black hole". No ping from from the host toward the VM. There is no way to connect to the VM even via spice on virt-manager as well. Seems like the VM is suspending. Htop on the host during the time of the freeze shows 100% load of all eight cores dedicated to the VM. But the host system is available and reachable, the lxc's inside this host is available and reachable as well.
+
+
+![12h_12m_59s_17_Mar_22__1_](/uploads/8874ad0220751fa253f8794c2eb6c2d5/12h_12m_59s_17_Mar_22__1_.png)