Recent content by mxscbv

Has anything changed since then? Can we safely use KernelCare with the latest PVE?

I'm interested in this, too.

Hello When I rename a firewall security group (on the cluster/dc level), it won't get renamed on the VM level and thus the security group no longer applies to that VM. Is that a bug or intended behaviour? Thanks.

Thank you Fabian! Alternatively, enabling 'krbd' also fixes the issue for now. :)

Many thanks for the suggestion!

cpool is a ceph pool in my cluster.

Yes, it happens reliably 100% of the time. The PBS load is ~0% (nothing happening), same with the node. The issue happens regardless of whether the VM is on or off. agent: 1 balloon: 131072 bios: ovmf boot: order=scsi0;net0 cores: 35 efidisk0: cpool:vm-110-disk-2,efitype=4m,size=528K memory...

Yes, but I don't quite understand what to do now. Do we need to downgrade pve-qemu-kvm on all our nodes? If yes, will it affect stability of the cluster? @Fabian_E would be great to hear some recommendations.

@GrueneNeun Try apt install pve-qemu-kvm=6.1.1-2, restart the VM, and then back up again.

Moving to pve-qemu-kvm=6.2.0-1 reproduces the unable to connect to VM error

Upon doing the first couple of tests, it seems like there are no 'unable to connect to VM' errors anymore after the downgrade, when both backing up to CephFS and Proxmox Backup Server.

Same.

Confirmed. Works in 7.1-1.

7.1 I believe its a bug anyway, so 'assistance' won't help that much.

Will anyone from Proxmox visit this thread? This is a critical issue as we can't make any backups now.