diff options
Diffstat (limited to 'gitlab/issues/target_missing/host_missing/accel_missing/881.toml')
| -rw-r--r-- | gitlab/issues/target_missing/host_missing/accel_missing/881.toml | 30 |
1 files changed, 0 insertions, 30 deletions
diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/881.toml b/gitlab/issues/target_missing/host_missing/accel_missing/881.toml deleted file mode 100644 index 66fb3ce87..000000000 --- a/gitlab/issues/target_missing/host_missing/accel_missing/881.toml +++ /dev/null @@ -1,30 +0,0 @@ -id = 881 -title = "qemu-ga fs-freeze causes VM to" -state = "opened" -created_at = "2022-02-21T09:08:44.827Z" -closed_at = "n/a" -labels = ["Guest Agent"] -url = "https://gitlab.com/qemu-project/qemu/-/issues/881" -host-os = "Debian 11 (Proxmox 7.1-10)" -host-arch = "AMD64" -qemu-version = "QEMU emulator version 6.1.1 (pve-qemu-kvm_6.1.1)" -guest-os = "Debian 11" -guest-arch = "AMD64" -description = """I have fresh install of Debian 11 and installed MariaDB 10.7 from MariaDB's Repo. Guest is fully up to date. -When Proxmox goes to do a backup it will call fs-freeze to the VM via the agent which then causes the backup process to hang and the VM will lockup or causes kernel message such as `**task qemu-ga:370 blocked for more than 120 seconds**`. The VM from what I can tell no longer is able to write to disk, and the only fix is to force reset the VM. - -The issue doesn't happen when the VM has first started or the agent has been restart from what I can tell, but if you leave it and wait for the nightly backup to run of the VM, it will then cause this issue to happen. - -There are other reports of this happening on the [proxmox forums](https://forum.proxmox.com/threads/snapshot-backup-not-working-guest-agent-fs-freeze-gets-timeout.99887/) More details on this topic. Other reports with the issue with MariaDB 10.6. - -My other Debian 11 VMs which were also setup recently, do not experience this problem, only difference is this VM is running the MariaDB. I have Gitlab, Docker, Mailcow, PowerDNS, OPNsense (each of these separate VM) in the other VMs and they do not experience this issue. All these VMs are running Debian 11. - -Agent Info -``` -qemu-guest-agent/stable,stable-security,now 1:5.2+dfsg-11+deb11u1 amd64 -```""" -reproduce = """1. Install Proxmox (although I would assume any QEMU 6.1.1) -2. Create a Debian 11 guest with MariaDB 10.7 from MariaDB repo -3. Wait good few hours -4. Issue a backup or fs-freeze""" -additional = "n/a" |