1 files changed, 61 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/118/kernel/1939179 b/results/classifier/zero-shot/118/kernel/1939179
new file mode 100644
index 00000000..f704bee2
--- /dev/null
+++ b/results/classifier/zero-shot/118/kernel/1939179
@@ -0,0 +1,61 @@
+kernel: 0.939
+device: 0.784
+user-level: 0.768
+mistranslation: 0.761
+semantic: 0.725
+graphic: 0.706
+hypervisor: 0.612
+files: 0.597
+performance: 0.491
+ppc: 0.419
+register: 0.403
+architecture: 0.388
+socket: 0.371
+virtual: 0.359
+vnc: 0.330
+boot: 0.319
+PID: 0.307
+network: 0.299
+permissions: 0.297
+i386: 0.288
+arm: 0.277
+risc-v: 0.272
+x86: 0.268
+debug: 0.224
+assembly: 0.207
+VMM: 0.194
+TCG: 0.190
+peripherals: 0.145
+KVM: 0.083
+
+qemu-ga fsfreeze crashes the kernel
+
+Hello,
+
+Still required your attention, duplicate from:
+https://bugs.launchpad.net/bugs/1807073
+https://bugs.launchpad.net/bugs/1813045
+
+We use mainly Cloudlinux, Debian and Centos.
+We experienced many crashes on our qemu instances based on Cloudlinux during a snapshot.
+The issue is not related to CloudLinux directly, but to Qemu agent, which does not freeze the file system(s) correctly. What is actually happening:
+
+When VM backup is invoked, Qemu agent freezes the file systems, so no single change will be made during the backup. But Qemu agent does not respect the loop* devices in freezing order (we have checked its sources), which leads to the next situation:
+1) freeze loopback fs
+              ---> send async reqs to loopback thread
+2) freeze main fs
+3) loopback thread wakes up and trying to write data to the main fs, which is still frozen, and this finally leads to the hung task and kernel crash.
+
+Moreover, a lot of Proxmox users are complaining about the issue as well:
+https://forum.proxmox.com/threads/error-vm-100-qmp-command-guest-fsfreeze-thaw-failed-got-timeout.68082/
+https://forum.proxmox.com/threads/problem-with-fsfreeze-freeze-and-qemu-guest-agent.65707/
+
+We are currently in progress of retiring this bug tracker here... could you please open a new ticket on gitlab instead:
+
+ https://gitlab.com/qemu-project/qemu/-/issues
+
+Thanks and sorry for the inconvenience.
+
+https://gitlab.com/qemu-project/qemu/-/issues/520
+... thanks!
+