VM geht in immer wieder in suspended mode

[drnicolas]

Ich habe gestern das Upgrade auf die aktuelle 8.1-Version gemacht. und auch einige VM mit der aktuellen guest-Tools Version 240 ausgestattet (2 VMs)

Eine der VMs (Windows 10/32) läuft ohne Probleme.

Die zweite (Windows 11/64) geht jeweils nach einiger Zeit von allein in den suspended mode, kann dann aber resumed werden

Hier kommt mal das Log:
Dec 29 11:44:54 pve-main pvedaemon[742068]: <root@pam> successful auth for user 'root@pam'
Dec 29 11:50:38 pve-main pveproxy[766304]: worker exit
Dec 29 11:50:38 pve-main pveproxy[1807]: worker 766304 finished
Dec 29 11:50:38 pve-main pveproxy[1807]: starting 1 worker(s)
Dec 29 11:50:38 pve-main pveproxy[1807]: worker 790301 started
Dec 29 11:52:10 pve-main pvedaemon[791347]: starting vnc proxy UPIDve-main:000C1333:008F991E:658EA4DA:vncproxy:102:root@pam:
Dec 29 11:52:10 pve-main pvedaemon[751964]: <root@pam> starting task UPIDve-main:000C1333:008F991E:658EA4DA:vncproxy:102:root@pam:
Dec 29 11:57:02 pve-main pvedaemon[737043]: worker exit
Dec 29 11:57:04 pve-main pvedaemon[1798]: worker 737043 finished
Dec 29 11:57:04 pve-main pvedaemon[1798]: starting 1 worker(s)
Dec 29 11:57:04 pve-main pvedaemon[1798]: worker 794266 started
Dec 29 11:58:22 pve-main pvedaemon[742068]: worker exit
Dec 29 11:58:22 pve-main pvedaemon[1798]: worker 742068 finished
Dec 29 11:58:22 pve-main pvedaemon[1798]: starting 1 worker(s)
Dec 29 11:58:22 pve-main pvedaemon[1798]: worker 795088 started
Dec 29 11:59:54 pve-main pvedaemon[794266]: <root@pam> successful auth for user 'root@pam'
Dec 29 12:01:32 pve-main pveproxy[779842]: worker exit
Dec 29 12:01:32 pve-main pveproxy[1807]: worker 779842 finished
Dec 29 12:01:32 pve-main pveproxy[1807]: starting 1 worker(s)
Dec 29 12:01:32 pve-main pveproxy[1807]: worker 796702 started
Dec 29 12:14:29 pve-main proxmox-backup-[1547]: pve-main proxmox-backup-proxy[1547]: write rrd data back to disk
Dec 29 12:14:29 pve-main proxmox-backup-[1547]: pve-main proxmox-backup-proxy[1547]: starting rrd data sync
Dec 29 12:14:29 pve-main proxmox-backup-[1547]: pve-main proxmox-backup-proxy[1547]: rrd journal successfully committed (25 files in 0.021 seconds)
Dec 29 12:14:54 pve-main pvedaemon[751964]: <root@pam> successful auth for user 'root@pam'
Dec 29 12:14:58 pve-main pvedaemon[751964]: <root@pam> end task UPIDve-main:000C1333:008F991E:658EA4DA:vncproxy:102:root@pam: OK
Dec 29 12:14:58 pve-main pvedaemon[803380]: starting vnc proxy UPIDve-main:000C4234:0091AF95:658EAA32:vncproxy:103:root@pam:
Dec 29 12:14:58 pve-main pvedaemon[795088]: <root@pam> starting task UPIDve-main:000C4234:0091AF95:658EAA32:vncproxy:103:root@pam:
Dec 29 12:15:01 pve-main pvedaemon[795088]: <root@pam> end task UPIDve-main:000C4234:0091AF95:658EAA32:vncproxy:103:root@pam: OK
Dec 29 12:15:02 pve-main pvedaemon[751964]: <root@pam> starting task UPIDve-main:000C4255:0091B0FD:658EAA36:vncproxy:102:root@pam:
Dec 29 12:15:02 pve-main pvedaemon[803413]: starting vnc proxy UPIDve-main:000C4255:0091B0FD:658EAA36:vncproxy:102:root@pam:
Dec 29 12:16:07 pve-main pvedaemon[751964]: worker exit
Dec 29 12:16:07 pve-main pvedaemon[1798]: worker 751964 finished
Dec 29 12:16:07 pve-main pvedaemon[1798]: starting 1 worker(s)
Dec 29 12:16:07 pve-main pvedaemon[1798]: worker 803975 started
Dec 29 12:16:18 pve-main pveproxy[1807]: worker 781674 finished
Dec 29 12:16:18 pve-main pveproxy[1807]: starting 1 worker(s)
Dec 29 12:16:18 pve-main pveproxy[1807]: worker 804048 started
Dec 29 12:16:18 pve-main pveproxy[804047]: got inotify poll request in wrong process - disabling inotify
Dec 29 12:17:01 pve-main CRON[804373]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Dec 29 12:17:01 pve-main CRON[804374]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Dec 29 12:17:01 pve-main CRON[804373]: pam_unix(cron:session): session closed for user root
Dec 29 12:28:57 pve-main pveproxy[796702]: worker exit
Dec 29 12:28:57 pve-main pveproxy[1807]: worker 796702 finished
Dec 29 12:28:57 pve-main pveproxy[1807]: starting 1 worker(s)
Dec 29 12:28:57 pve-main pveproxy[1807]: worker 810269 started
Dec 29 12:30:03 pve-main pvedaemon[794266]: <root@pam> starting task UPIDve-main:000C5F3E:0093111D:658EADBB:vncproxy:102:root@pam:
Dec 29 12:30:03 pve-main pvedaemon[810814]: starting vnc proxy UPIDve-main:000C5F3E:0093111D:658EADBB:vncproxy:102:root@pam:
Dec 29 12:30:03 pve-main pveproxy[804047]: worker exit
Dec 29 12:30:54 pve-main pvedaemon[794266]: <root@pam> successful auth for user 'root@pam'
Dec 29 12:32:18 pve-main pvestatd[1770]: got timeout
Dec 29 12:32:23 pve-main pvestatd[1770]: status update time (7.772 seconds)
Dec 29 12:32:28 pve-main pvestatd[1770]: got timeout
Dec 29 12:32:34 pve-main pvestatd[1770]: status update time (8.304 seconds)
Dec 29 12:34:31 pve-main pveproxy[790301]: worker exit
Dec 29 12:34:32 pve-main pveproxy[1807]: worker 790301 finished
Dec 29 12:34:32 pve-main pveproxy[1807]: starting 1 worker(s)
Dec 29 12:34:32 pve-main pveproxy[1807]: worker 813174 started
Dec 29 12:40:21 pve-main pvedaemon[794266]: <root@pam> end task UPIDve-main:000C5F3E:0093111D:658EADBB:vncproxy:102:root@pam: OK



Woher könnte das kommen?
mir fällt auf, dass suspended VM den Proxmox-Boot-Screen zeigt

 

[W3isserWolf]

Ich hatte das Problem, wenn die VM in den Energiesparmodus geht.
So wie du das schilderst solltest du mal in die Energiesparpläne schauen.
Am besten "Energiesparplaneinstellungen bearbeiten" suchen und den "Energiesparmodus nach": Niemals einstellen.

 

[drnicolas]

Das scheint es tatsächlich gewesen zu sein.
Danke

 

[W3isserWolf]

Kein Problem.
Hat mich auch Stunden gekostet bis ich mal Windows 10 und ne Windows Server Installation verglichen habe.

Grüße
W3isserWolf