Guest OS no longer appearing upon Start

[dmatsumoto]

I've got Windows XP 32bit installed as the guest OS on my computer, which is running VBox 3.2.10 for x64. Everything has been running perfectly for quite some time. Then today, I started my guest OS, and after the usual restoring progress box (my snapshot was created while the guest OS was running), nothing happened. If I click on the snapshot in the VBox GUI and then click "Show", I get a white box partially displayed in my screen. When I click on it, it then gives me the title bar, but the dialog contents are still white.

The VM is actually running, because I eventually decided to RDP to it, and it worked just fine. It's just that I can't access the guest OS via the normal GUI.

I can start up my other guest OSes and they work as expected. I checked the log file for the problematic snapshot, and there's nothing out of the ordinary (as far as I can tell). No errors at all. The last lines in the log look like this once the guest is started:

00:00:08.177 HGCM: restoring [VBoxSharedFolders]
00:00:08.177 SharedFolders host service: connected, u32ClientID = 19
00:00:08.177 SharedFolders host service: loading state, u32ClientID = 19
00:00:08.178 SharedFolders host service: success
00:00:08.178 HGCM: restoring [VBoxGuestControlSvc]
00:00:08.178 HGCM: restoring [VBoxGuestPropSvc]
00:00:08.178 HGCM: restoring [VBoxSharedClipboard]
00:00:08.178 Guest Additions information report: additionsVersion = 0x00010004, osType = 0x00033000
00:00:08.179 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000009b90000 w=1280 h=868 bpp=32 cbLine=0x1400
00:00:08.183 Changing the VM state from 'LOADING' to 'SUSPENDED'.
00:00:08.183 Changing the VM state from 'SUSPENDED' to 'RESUMING'.
00:00:08.183 Changing the VM state from 'RESUMING' to 'RUNNING'.
00:00:08.255 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000009b90000 w=1280 h=868 bpp=32 cbLine=0x1400
00:00:08.371 2D video acceleration is disabled.
00:00:13.255 PCNet#0: The link is back up again after the restore.

Very weird!!!

[dmatsumoto]

I have solved my problem, and figured I'd post it here in case anyone else ran into the same issue.

Since I had RDP access, I decided that I'd try to shut down the OS before starting up the VM again. After doing this and waiting a *long* time for the VBox GUI to acknowledge that the VM was stopped, I started it up again and it worked!

Phew.