Hi FB2000,FB2000 wrote:Windows has a hard limit to how long the service controller could wait when system reboots. The time limit is specified in the WaitToKillServiceTimeout value of the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control. Your PauseShutdown value should never exceed this time limit.
Based on that, I would say just stay with 'savestate', unless you are sure 'acpipowerbutton' can be done with in the time limit.
Apologies for asking this question again but I still cant get how the "Pauseshutdown" works in VBoxVmService in relation to the "WaitToKillServiceTimeout" of Windows. Once the PC is issued the shutdown command, whether using the Power button or via Windows, is it that:
a) the guest VM initiates the shutdown sequence simultaneously with the Pauseshutdown delay then tells Windows WaitToKillServiceTimeout to start countdown after the Pauseshutdown delay has expired?
b) Windows WaitToKillServiveTimeout is initiated, the guest VM initiates the shutdown sequence after the Pauseshutdown delay has expired then waits for Windows WaitToKillServiceTimeout to expire and shutdown?
My guest VMs are booting much better now after adjusting these two variables but some guests still take more time to do a savestate than others. I am concerned that these guests might get caught in the middle of the Windows WaitToKillServiceTimeout and get shutdown inappropriately. In such cases, I would either shorten the Pauseshutdown value or increase the WaitToKillServiceTimeout value to give more time to the guest VMs to do their thing.
Kindly explain. Thanks!