Dear all,
when performing maintenance on my 30+ PVE servers, I use to "Bulk suspend" all VMs and then reboot the host.
Almost every time during that suspend process, one or more VMs are reporting a timeout. This will cause the VM to stay locked with a yellow traffic cone symbol.
Note: Successfully suspended VMs show a black traffic cone.
In reality these VMs were successfully suspended.
Unlocking the VM causes the traffic cone to disappear (looks like it is shut down), "qm start xxx" will report resume from suspend and all is working fine.
Nevertheless the lock is causing the autostart to fail!
I'd expect the VM to eventually unlock once the process has finished and and show a proper symbol/state in GUI.
Upon reboot all VMs shall start normally.
With the current behaviour it's a bit cumbersome since manual intervention is required to eventually get them booting.
Am I doing something wrong?
BTW: It would be great to see the naming streamlined. Calling the same action either "suspend" (bulk action) or "hibernate" is strange.
In my eyes there is no difference if you perform a task for one or multiple targets ;-)
Best regards,
Bernhard
when performing maintenance on my 30+ PVE servers, I use to "Bulk suspend" all VMs and then reboot the host.
Almost every time during that suspend process, one or more VMs are reporting a timeout. This will cause the VM to stay locked with a yellow traffic cone symbol.
Note: Successfully suspended VMs show a black traffic cone.
In reality these VMs were successfully suspended.
Unlocking the VM causes the traffic cone to disappear (looks like it is shut down), "qm start xxx" will report resume from suspend and all is working fine.
Nevertheless the lock is causing the autostart to fail!
I'd expect the VM to eventually unlock once the process has finished and and show a proper symbol/state in GUI.
Upon reboot all VMs shall start normally.
With the current behaviour it's a bit cumbersome since manual intervention is required to eventually get them booting.
Am I doing something wrong?
BTW: It would be great to see the naming streamlined. Calling the same action either "suspend" (bulk action) or "hibernate" is strange.
In my eyes there is no difference if you perform a task for one or multiple targets ;-)
Best regards,
Bernhard