Recent content by gbr

Does the release of 6.3 solve this issue? Anyone here that had the issue and upgraded? Gerald

I had ballooning off on guests that locked up.

My apologies, then. There's been no Proxmox employee interaction on here for quite a while, so I thought you'd dropped it. Gerald

I moved everything to base Ubuntu with KVM and libvirtd/virt-manager. I didn't have any containers, just KVM machines. Now, I can actually go on holidays without things locking up on me. I started Proxmox on version2. Pity they won't accept there is an issue here.

I have had to move away from Proxmox. 25% of my servers are now on Ubuntu 20.04 with libvirtd and cockpit, Yes, I lose functionality, but at least my VMs stay up. I'd move back to Proxmox in a heartbeat if they solved this issue. Gerald

Right, which means that it's a PVE 6 bug that no one wants to admit exists.

So, I managed to catch a VM as it locked up. It's IOWAIT time on disk access was using all of the CPUs, which matches what the Proxmox people have mentioned as a potential problem. I have my disk images on NFS. The thing is, none of the other VMs showed the same IOWAIT, including one that uses...

Hoping for an answer so I can move forward. I get machines locking and not being able to restart because of this almost every day.

So is this systemd timeout issue being looked at, or has it been decided it's not an issue by Proxmox?

Why would I start a new thread, when this one contains all the history of the issue? A VM locks up. It can't be reset. qm stop <vmid> from command line sends a sigkill. The VM cannot be restarted due to systemd timeout. Migration works, but you have to click the stop button to get it to migrate...

Up to date, and still having issues. PVE has gone from a remarkably stable product to ultra flakey. Thanks systemd. I'm either going to have to roll back to PVE 5.x or leave Proxmox entirely. This instability is seriously hurting my production servers.

I get roughly one VM a day, across multiple Linux OSs. No Windows yet. I'm going to start monitoring IOWait to see if that is an issue. I've been running NFS for storage for years, and have not seen this issue. Plus, none of my other VMs are down, so I can't see it being an NFS issue.

Hey Proxmox folk... What can I do to help you solve this issue? Gerald

So, the same VM is down this morning. No backups, no stress, just stopped responding at 8:40 AM. It no longer listens to any commands from the web interface, and shows as running, but it clearly isn't. root@pve-4:~# qm status 150 status: running root@pve-4:~# qm terminal 150 unable to find a...

This also stop backups from running when the backup reached the failed VM. Any chance there's some forward motion on this? Anything i can do on my end to help?