PVE is killing my WinServer2025 VMs

D

dan.

New Member
Nov 4, 2025
3
0
1
I'm sorry if this has been answered, but I couldn't find anything when I searched before posting this. I really hope someone can help me with this. It's probably obvious, but I'm lost.
For the last couple of days proxmox is just killing my Windows Server 2025 VM's. It doesn't show that they were shutdown or anything. They are just running like normal, and then maybe half an hour or even a couple hours later I discover that they are just not running at all. They startup normally. This is NOT happening on my Windows 11 desktop VM's or my linux VM's which I am running at the same time. I have PowerToys installed on all of my windows instances (desktops and servers) with KEEP AWAKE INDEFINITELY and KEEP SCREEN ON enabled on all of them. That always worked for keeping my VMs from being suspended.

I have checked and I am definitely NOT running out of RAM. I've even tried shutting down most of my other VM's and the problem still occurs. I did find something weird by watching the live log and catching it killing my two Windows Servers. It looks like something about "cleanup" on the VM and then the VM doesn't get restarted? This is the part of the log that coincides with it killing them. The two Win Server 2025 VMs are 101 and 106.

Please help me stop this!
 

Attachments

It just did it again. So about every 30 minutes...

Nov 04 16:29:09 pve kernel: tap101i0: left allmulticast mode
Nov 04 16:29:09 pve kernel: fwbr101i0: port 2(tap101i0) entered disabled state
Nov 04 16:29:09 pve kernel: fwbr101i0: port 1(fwln101i0) entered disabled state
Nov 04 16:29:09 pve kernel: vmbr0: port 2(fwpr101p0) entered disabled state
Nov 04 16:29:09 pve kernel: fwln101i0 (unregistering): left allmulticast mode
Nov 04 16:29:09 pve kernel: fwln101i0 (unregistering): left promiscuous mode
Nov 04 16:29:09 pve kernel: fwbr101i0: port 1(fwln101i0) entered disabled state
Nov 04 16:29:09 pve kernel: fwpr101p0 (unregistering): left allmulticast mode
Nov 04 16:29:09 pve kernel: fwpr101p0 (unregistering): left promiscuous mode
Nov 04 16:29:09 pve kernel: vmbr0: port 2(fwpr101p0) entered disabled state
Nov 04 16:29:09 pve qmeventd[980]: read: Connection reset by peer
Nov 04 16:29:09 pve systemd[1]: 101.scope: Deactivated successfully.
Nov 04 16:29:09 pve systemd[1]: 101.scope: Consumed 10min 2.488s CPU time.
Nov 04 16:29:10 pve qmeventd[93916]: Starting cleanup for 101
Nov 04 16:29:10 pve qmeventd[93916]: Finished cleanup for 101
Nov 04 16:29:17 pve kernel: tap106i0: left allmulticast mode
Nov 04 16:29:17 pve kernel: fwbr106i0: port 2(tap106i0) entered disabled state
Nov 04 16:29:17 pve kernel: fwbr106i0: port 1(fwln106i0) entered disabled state
Nov 04 16:29:17 pve kernel: vmbr0: port 3(fwpr106p0) entered disabled state
Nov 04 16:29:17 pve kernel: fwln106i0 (unregistering): left allmulticast mode
Nov 04 16:29:17 pve kernel: fwln106i0 (unregistering): left promiscuous mode
Nov 04 16:29:17 pve kernel: fwbr106i0: port 1(fwln106i0) entered disabled state
Nov 04 16:29:17 pve kernel: fwpr106p0 (unregistering): left allmulticast mode
Nov 04 16:29:17 pve kernel: fwpr106p0 (unregistering): left promiscuous mode
Nov 04 16:29:17 pve kernel: vmbr0: port 3(fwpr106p0) entered disabled state
Nov 04 16:29:17 pve qmeventd[980]: read: Connection reset by peer
Nov 04 16:29:17 pve systemd[1]: 106.scope: Deactivated successfully.
Nov 04 16:29:17 pve systemd[1]: 106.scope: Consumed 4min 20.109s CPU time.
Nov 04 16:29:17 pve qmeventd[93972]: Starting cleanup for 106
Nov 04 16:29:17 pve qmeventd[93972]: Finished cleanup for 106
Nov 04 16:29:19 pve pvedaemon[88002]: <root@pam> successful auth for user 'root@pam'
 
You must log in or register to reply here.
Top Bottom