Search results

... the Proxmox development team claims that they cannot reproduce the problem. As said before, I find it not credible. Here is the umpteenth VM in freeze after reboot. Can't reproduce ... let's say my average is about 30-35 VMs freezing once a month ... either I'm particularly unlucky or...

I hope in Qemu 6.2. I find the questions asked by the Proxmox Support team strange. It seems this thread is not even being read. Several tickets have been opened, claiming that the problem was never replicated by them. They ask for information that is evident if this thread is read. But...

Any updates related to this issue (which is really becoming more than just a problem)? We are close to the next patch on Tuesday (which results in a massive reboot of many Windows VMs), can we need further help to identify the cause?

The simulation should be done like this: snapshot of the VM with RAM, try to restart it, if the problem occurs then THAT SNAPSHOT refers to the tests, because it contains the state of the machine and the RAM. Since the problem does not occur methodically and above all not immediately it is...

No, that's not my problem. On all my clusters that exhibit this behavior there is perfect alignment between "date" and "hwclock". But the problem arises.

Bad news. I will prepare myself psychologically for the next MS$ update and the related bloodbath of VMs that will stuck during the night following the automatic reboot.

I confirm that with the latest version of the virt-io driver 0.1.215 the problem occurs anyway, indeed, it also occurs on vm not configured with paravirtualized devices (for example sata), see above. Perhaps only the change of the kernel can be the solution (maybe if the cause is identified we...

Doing so there is a problem. If the backup of the VM is given to you, it is very likely that post restore is working correctly. The snapshot with RAM should also be delivered to you. this is because if the VM does not have suitable boundary conditions the problem does not occur. IMHO

Any tests with version 7.1-11? The list of updated packages does not include QEMU and/or the kernel, so I assume the problem remains. I'm terrified of finding dozens and dozens of VMs crashed on boot at the next reboot for Windows updates. Sigh

I can confirm. The problem does NOT show up on 2008r2. 8 VMs (with extended update service) did not have any problems rebooting after a month of uptime. And never in the past have they given it. The problem occurs from 2012 onwards. Who knows, some low-level interaction that doesn't show up with...

sorry, has anyone tried the 5.15 kernel on non-production systems? The problem also occurs with that kernel version?

For me (in different clusters) the problem occurs on Host with different physical CPU (always Intel) and with different virtual CPU in the VMs. There doesn't seem to be a link with the CPU type.

I can confirm. On our clusters, servers 2012, 2016 and 2019 have the same problem. 2008r2 servers (with active extended support from Microsoft) have never experienced this problem.

Sorry for the duplicate, the problem is exactly the same of the this one: https://forum.proxmox.com/threads/windows-vms-stuck-on-boot-after-proxmox-upgrade-to-7-0.100744/

Dual Xeon gold for Host. The problem It also comes with different (older) CPUs On different clusters.

Hi everyone, sorry for the duplicate post, I've exactly the same problem: https://forum.proxmox.com/threads/proxmox-7-1-10-windows-vm-after-reboot-does-not-always-start.106537/ Luca

I forgot Often a stop-start of the VM is decisive and restarts regularly. This is the option configuration, VMs use guest agents.

Hi, for some months I have a problem, on several clusters. Proxmox 7.1.10 enterprise repositories, running kernel (now) Linux 5.13.19-5-pve #1 SMP PVE 5.13.19-13 (Tue, 08 Mar 2022 07:32:25 +0100) When I reboot a WIndows VM (usually during updates) it does not always (it is not predictable)...

OK, I've reproduced the problem exactly: - Proxmox 7.0.14+1 - n.2 nodes NFS share 10 gbps to NetAPP datastore dedicated to NFS, 10 gbps trunk for VM and management. 1 gbps dedicated and isolated link for corosync. - Upload in GUI 3 Gbyte ISO image - I'm connected to node 1. After 35% process...

Yes, can I confirm... Proxmox CE 7.0.14+1, when upload 8 Gbyte ISO to share NFS through the node n.1, block transfer and the node become irresponsive (the node n.2 response correctly). Luca