3 ms·
I searched the release notes and manual but couldn't find an answer. Does anyone know if this release fixes the problem of not cleanly shutting down the guest O
by SonOfKyuss 9y ago
I searched the release notes and manual but couldn't find an answer. Does anyone know if this release fixes the problem of not cleanly shutting down the guest OS when the Windows host does an automated update/reboot? It's really annoying to have Windows run an update overnight and see that it did a dirty shutdown of my Linux dev instance guest.
Virtualbox has a "save state" option. It would be nice if it would perform a "save state" on all guests when the host reboots.
- Aloha 9y agoThis strikes me as a windows issue, not a VirtualBox one. How does windows kill applications that have not exited, how long does it wait to do so, etc?
- SonOfKyuss 9y agoThe VirtualBox process is notified of Windows shutdown and power management events. It can choose to save the state or "power down" the guest OS. There is a setting to manage the default action to take, but it doesn't seem to work reliably. https://www.virtualbox.org/manual/ch09.html#idm9348 https://www.virtualbox.org/manual/ch09.html#idm9348
- Aloha 9y agoI wonder if its taking too long to save state, so windows kills the process and proceeds with its reboot
- breakingcups 9y agoThat's probably it, Windows 10 is incredibly aggressive in killing applications when rebooting for an update. In corporate settings it's even worse, we're currently having a glitch where, no matter what our administrators specify as policy, computers will just randomly reboot sometime after Patch Tuesday for a reboot. Without notification, without a chance to save your work. Just poof.