blob: b30d9379e4916b89a0c9af61da3d1df131426519 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
device: 0.784
semantic: 0.725
graphic: 0.706
files: 0.597
other: 0.509
performance: 0.491
socket: 0.371
vnc: 0.330
boot: 0.319
PID: 0.307
network: 0.299
permissions: 0.297
debug: 0.224
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!
|