Search results

The VM have been live migrated to an updated host

pveversion -v |grep qemu libproxmox-backup-qemu0: 1.3.1-1 pve-qemu-kvm: 7.0.0-2 qemu-server: 7.2-4

"On Qemu 7.0 ?" are you referring to the Machine version in the GUI? - Its not a solution to upgrade the machine version because of the issues with missing drives / network setting after change the Machine version to 7.0

Just testet with a VM with Qemu uptime of 11 days, and OS uptime 111days. The proxmox host running 7.2-7, and the VM is stocked on reboot - dont think the bug is fixed..

What machine version are your VMs running?

@tuxis Here is the output from a new, and a old rbd image seems to be the same root@ecs-rgv-pve-int-1:~# rbd --pool rbd-ssd --image vm-132-disk-0 info rbd image 'vm-132-disk-0': size 60 GiB in 15360 objects order 22 (4 MiB objects) snapshot_count: 0 id...

We have now testet downgrade to kernel 5.11.22-7 but we still seeing the reboot issues. I have now testet to create a new VM (with same settings) and importet the RDB disk from one of the VM now working. The newly created VM boots and reboots just fine. It looks like it just VMs created before...

the manual reboot is made from the OS, just to verify that is not the windows update causing the issue

Yes all hosts Yes Yes we are running over 200VM on this 2 clusters on same time Yes we are running ceph with 9 SSD OSD's ind each node running over 2x25Gbit We have not testet on all VMs, but we see the issue typical when VMs are trying to reboot after windows patch - but manuel reboot are...

We have the same issue on 2 different Proxmox clusters upgraded from 6 to 7. We are running around 200 Windows VM on the clusters. I have today tried to upgrade one of the cluster to the newest version including upgrade to pve-kernel-5.15 Still the same issue :(