virtualbox.org

Upgraded to VBox 6.0 a few days back and now i'm having issues with the best part of VBox: Fast resuming.

The error shown:
---------------------------
VirtualBoxVM.exe - Application Error
---------------------------
The exception Breakpoint

A breakpoint has been reached.

(0x80000003) occurred in the application at location 0x00007FF9C1197888.

This is presented at the very last step of the resuming and i can see the resumed state, but the guest crashes and VM is in Aborted state. I have tried to uninstall VBox en reinstalling and setting up new VMs. But this error still shows up. Its mostly 32-bit Windows guests that are effected, but i also have one 32-bit guest that it works with. I have tried fiddeling with all settings that i can come to think of but without any luck. Is this die to the guest or the host (Windows 10)? All Guest addons updated of course.

Any tips that may point me in any direction? dump log attached.

/Johan

Take a look at the Known Issues in the "Discuss the 6.0.0 release". It looks like you may be seeing something similar to #18263 Restoring 32bit Windows7 VM Saved State Fails.

Can you upgrade to 6.0.2 and see if the problem is still there? Otherwise "Discard" the saved state...

6.0.2 Does not work.

The proposed workaround, is that to add a SATA controller and boot .vdi on SATA instead of IDE?

It might work with Windows7 32-bit guests though. Havent seen the issue on them since 6.0.2.

But i run some WinXP aswell and they do not work when saving state. Either with 6.0.2 and/or SATA-controller.

Exactly the same to my virtualbox 6.0.2. installed on Windows 8.1 64Bits Host and Windows XP 32Bits Guest previously in saved state... version 5.2.22 didn't have this problem.
Thanks

I can confirm this issue on Windows XP 32bits. I even recreatred a new virtual machine for Windows XP, and the problem persisted.

I've experienced the same issues, whether using previous VirtualBox versions, or the current. I reverted to V 6, and thought it had solved the issue; ran my 32-bit Win XP VM just fine, took 25 snapshots, and paused numerous times from which the VM awakened just fine, during several days of installing and removing old programs within the XP installation. Absolutely nothing has been modified, either in my VirtualBox settings, or my actual 64-bit Win 7 Ultimate machine.
Now, once again, all of a sudden, the "Paused" VM inevitably crashes at the 98% restore point, as a ghostly image of the paused moment is tantalizingly event behind the initializing screen. I can then successfully restart the VM, which must re-boot to the XP within the VM, but now the restart is excruciatingly slow, or seems to nearly freeze after logging in, when previously the VM was always about ten times faster than the old full licensed XP laptop my .vhd was created from.
As a living human being at some point must have actually written "a breakpoint has been reached," or at the very least defined the meaning of each word in the sentence, I was expecting informative responses here from folks who worked on the Virtualbox development, to the extent that this frequent occurrence might be clarified.
Silly me. Instead, the inevitable forum input has advice along the lines of "try this, it should work," "I tried, it didn't help," "I tried, it did," "That didn't help, so I messed around here and there and now it's working again," etc.
If we knew what a breakpoint was, and how one goes about reaching one, that would be at least a grounding place to obtain some sort of footing. I have seen very little within a variety of logs to provide consistent help, including logs with errors, for snapshots and saved states which were having no troubles at all.
I suppose I get what I paid for - free.

I did convert my XP VM to SATA per recommend solution. No regrets doing so (found solution online how to do it), but doing so did not eliminate recovery from saved point issue. Currently running 6.0.4 (had issue since 6.0). No need to add error dialogues since I'm not the only one getting this error. Can say that 64-bit LUbuntu OS doesn't have the recovery issue and neither does my minimalized Win10 OS. Hope there will be a solution or viable work-a-round to this issue, but it's only a pain when I recover. After recovery and error, the XP VM will boot normally but my desktop icons then have to be re-arranged (a pain, but not really an issue at this time).

edit:

Forgot to add that my XP VM also loses shares with host OS until I open an Explorer session and click on my mapped share drive. That's strange too, but at least there's a quick work-a-round.

Currmudgeon wrote:I was expecting informative responses here from folks who worked on the Virtualbox development

You and me and the rest of the people here or out there, that don't have a support contract, don't have any expectations; the developers have to take care of their customers first. The problem will be fixed, but don't expect a minute-by-minute play.

Currmudgeon wrote: Instead, the inevitable forum input has advice along the lines of "try this, it should work," "I tried, it didn't help," "I tried, it did," "That didn't help, so I messed around here and there and now it's working again," etc.

If you have anything more solid, more definitive than this, then do share. We're all in the same boat you know...

Currmudgeon wrote:Now, once again, all of a sudden, the "Paused" VM inevitably crashes at the 98% restore point

There are a couple of workarounds, and they are solid advice, take it from me:

1. Don't use saved states until this is resolved. That one works 100%.
2. Stick with 5.2.26 until this is resolved. This one works 100% too.

lylejk wrote:I did convert my XP VM to SATA per recommend solution

Please note that there are several sources for the restoration of saved-state VMs, it's not just the LsiLogic one. That's why there are several open tickets (and way more duplicates) that are still open...

Thanks for the reply, socratis; I agree that not recovering from set point until a "fix" is found is sound. I just hibernate my host and all recovers when my PC wakes. The programmers have always addressed issues since I've been using VirtualBox (started back in 2008 with my then XP OS as host; lol). Best way to protect an OS (host) imo. My current system's getting old and I'm currently doing research on dedicated container/docker OS (lots of folk like CoreOS for instance). Might go that route, but my crutch is still Windows. Probably, in the end, I'll chicken out and stick with Win10 and run VirtualBox for sandbox purposes as I have since 2008 (currently have Win98, Android, LUbuntu, and, of course, XP VMs). I should have joined this forum a long time ago; have often watched this forum for years. Appreciate tremendously the work that's been put in to keeping VB viable for as long as it has been.