Search results

I got no solution for it but a workaround. I added qm shutdown and qm start for this specific host around the qm snapshot. No real solution but at least does the task...

Last last two nights it happend again. Just the same result. Guest is all black, high CPU load, timeout on guest-fsfreeze-status and system dead. So only stop and start brings me back in business.

Tonight it happend again. This morning I found this VM at ~85% CPU usage (4 CPUs) and stuck. The local console returned from black after several returns and showed me: BUG: soft lockup - CPU#1 stuck for 4294876409s! [ksoftirqd/1:13] On the host: qm agent 10005 fsfreeze-status VM 10005 qmp...

So I installed the qemu-guest-agent, activated in proxmox and run the script. No freeze. May I was just lucky or it solved the problem. I'll keep an eye on it. But shouldn't the system run normaly after a snapshot? Without the agent it should just risk a iconsistent file system or am I wrong?

No it is not installed. But I can install it and give it another try to find out tonight.

Normaly I'm using pve-autosnap to generate snapshots on a regular base. On one cluster I got a weird problem: Whenever I snapshot my Debian system it instantly freezes. I can only stop this machine. There are absolutly no logs regarding this incident. The cpu load just raises. First I thought it...