You are not logged in.
This particular problem seems to come and go with various VirtualBox versions (or there's another pattern that's independent of the version): when starting a "saved" guest the progress bar goes to 99%, sits there for 5-10 seconds and then fails to load. An error dialog shows "Failed to load unit 'pgm'" and the log shows either:
00:00:38.286836 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_REC_TERM_CRC)}, preserve=false aResultDetail=0
00:00:38.307436 Power up failed (vrc=VERR_SSM_INTEGRITY_REC_TERM_CRC, rc=NS_ERROR_FAILURE (0X80004005))
00:00:38.808665 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:00:38.808728 GUI: Aborting startup due to power up progress issue detected...or, in some cases:
00:00:31.250749 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_DECOMPRESSION)}, preserve=false aResultDetail=0
00:00:31.250850 Power up failed (vrc=VERR_SSM_INTEGRITY_DECOMPRESSION, rc=NS_ERROR_FAILURE (0X80004005))
00:00:31.751913 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:00:31.751967 GUI: Aborting startup due to power up progress issue detected...I have not been able to fully reproduce this, but anecdotally, I find the problem occurs more often when I save the guest, then put the host to sleep (the host is a laptop), resume the host and then try to start the guest from the Saved state. I also find that if I restart the host after this problem occurs and then start the guest from Saved state, it works again. Obviously, discarding the saved state always "works", but that's effectively hard-resetting the guest.
There are a couple of bugs logged upstream:
https://www.virtualbox.org/ticket/12680 - closed/fixed
https://www.virtualbox.org/ticket/8970 - new, but opened 7 years ago
Is anyone else running into this same problem, and is the pattern similar: (sometimes when) sleeping the host makes the problem appear and (sometimes when) restarting the host, the problem goes away?
Offline
To add to this, I was wondering if reloading the kernel modules instead of having to restart would also fix the issue, but running 'vboxreload' has no effect. In my case, rebooting the host is the only way to fix it.
Offline
Same problem here.
Offline