Version 6.0.0 Snapshot Bug

Discussions related to using VirtualBox on Windows hosts.
hqngl
Posts: 6
Joined: 6. Jul 2013, 00:18

Re: Version 6.0.0 Final Snapshot Bug

Post by hqngl »

I can confirm this: https://www.virtualbox.org/ticket/18265#comment:5
It only crashes if IO APIC is disabled.
gotenks
Posts: 4
Joined: 29. Jan 2019, 10:50

Re: Version 6.0.0 Final Snapshot Bug

Post by gotenks »

I can confirm this bug exists in 6.0.4 too, regardless of I/O APIC status ...
Jacob Klein
Posts: 696
Joined: 20. Nov 2013, 01:07

Re: Version 6.0.0 Final Snapshot Bug

Post by Jacob Klein »

In addition to the ticket here:
https://www.virtualbox.org/ticket/18265

I also have another ticket that may be the same issue, with a .zip file to easily reproduce the issue, located here:
https://www.virtualbox.org/ticket/18212

I'm surprised we're at 6.0.4 and this hasn't been fixed yet!
gibibit
Posts: 5
Joined: 4. Feb 2019, 20:33

VirtualBox v6.0.4 guest additions make restore saved state lock up and freeze

Post by gibibit »

I confirm that restoring saved state fails every time if VirtualBox Guest Additions v6.0.4 is active when the state is saved.

Restoring saved state fails in all variations of these properties:

VirtualBox: v6.0.4
Host OS: Mac OS 10.13.6
Guest OS: both Debian 9 and Windows 10, 64-bit
Guest chipset: both PIIX3 ICH9
Guest Enable I/O APIC: both on and off
Guest additions: v6.0.4

BUT restoring works if I use an old VM with Guest Additions v5.2.18!
IT ALSO WORK if I save state when the guest machine is in the GRUB bootloader, before the Guest Additions v6.0.4 is active.

The cancel button does not actually close the restore dialog and cancel it. The only way to close the VM restoring dialog and the VM window is to Force-Quit the application from the Mac OS process manager.
gibibit
Posts: 5
Joined: 4. Feb 2019, 20:33

Re: Version 6.0.0 Final Snapshot Bug

Post by gibibit »

Actually it works if I change the display adapter for the VM to "VBoxVGA" instead of "VMSVGA" or "VBoxSVGA". So it is something related to these new display adapters.

And if 3D acceleration is disabled with VBoxSVGA or VMSVGA, it also works OK. 2D acceleration with Windows on VBoxSVGA works fine, in particular as long as 3D acceleration is disabled.

See also the what appears to be the same issue in the Mac OS X forum, thread titled "VirtualBox crash restoring VM after saving state".
oferlaor
Posts: 7
Joined: 11. Feb 2019, 16:08

Re: Version 6.0.0 Final Snapshot Bug

Post by oferlaor »

I have the identical problem.

Tried the fixes proposed in the forums: changing the graphics controller and IO APIC and mouse controller.

No change. I still can't save current state and go back to it. When I load it I get 97% and then E_FAIL.
gotenks
Posts: 4
Joined: 29. Jan 2019, 10:50

Re: Version 6.0.0 Final Snapshot Bug

Post by gotenks »

Tired waiting for the fix. Returned to 5.2.26, which works flawlesly ...
Schaffstein
Posts: 13
Joined: 5. Mar 2018, 14:33

Re: Version 6.0.0 Final Snapshot Bug

Post by Schaffstein »

Same problem here. Win 7 Pro Host. Just upgraded from last Virtualbox 5 to 6.04
Any XP guest crashes when resuming from saved state.
Win7 and Win10 guests seem to work fine.
wat
Posts: 28
Joined: 28. Mar 2010, 21:48
Primary OS: MS Windows 10
VBox Version: OSE other
Guest OSses: Ubuntu-various

Re: Version 6.0.0 Final Snapshot Bug

Post by wat »

Can confirm turning io apic on or off, 2 or 1 cpus has no effect, it ends up failing to restore the machine state in xp guest on windows 10 host.
Schaffstein
Posts: 13
Joined: 5. Mar 2018, 14:33

Re: Version 6.0.0 Final Snapshot Bug

Post by Schaffstein »

Can also confirm trying different graphic adatpers and graphics memory has no effect, it ends up failing to restore the machine state in xp guest at 97% on windows 7 pro host.

Since it is 100% reproducable I really hope that this can be fixed SOON! I need save and restore running machines quickly by saving the state to work efficiently!

PLEASE fix it ...
andyp73
Volunteer
Posts: 1631
Joined: 25. May 2010, 23:48
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation

Re: Version 6.0.0 Final Snapshot Bug

Post by andyp73 »

Schaffstein wrote:Since it is 100% reproducable I really hope that this can be fixed SOON! I need save and restore running machines quickly by saving the state to work efficiently!

PLEASE fix it ...
The developers may or may not be working on this, they don't really tell us what is coming and when. If you want to be able to impact how soon it gets fixed then you need to purchase some licenses and a support contract.

-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Jacob Klein
Posts: 696
Joined: 20. Nov 2013, 01:07

Re: Version 6.0.0 Final Snapshot Bug

Post by Jacob Klein »

My testing indicates that the
"97% hang when restoring final snapshot" bug
... which I was tracking here https://www.virtualbox.org/ticket/18212
... is RESOLVED for me in:
... Oracle VirtualBox v6.0.5 Test Build 129220

Can someone else test and confirm, please? ;)

Test Builds can be downloaded from here:
https://www.virtualbox.org/wiki/Testbuilds

Thanks,
Jacob Klein
JayEm
Posts: 35
Joined: 15. Jul 2014, 21:20

Re: Version 6.0.0 Final Snapshot Bug

Post by JayEm »

Jacob Klein wrote:Can someone else test and confirm, please? ;)
Still crashing here.
Jacob Klein
Posts: 696
Joined: 20. Nov 2013, 01:07

Re: Version 6.0.0 Final Snapshot Bug

Post by Jacob Klein »

Does yours hang at 97%? Or does it do something different like immediately crash?

My problem was that it was hanging forever at 97%. And that problem is now fixed I think.

Sorry if I confused 2 separate problems.
JayEm
Posts: 35
Joined: 15. Jul 2014, 21:20

Re: Version 6.0.0 Final Snapshot Bug

Post by JayEm »

Oh, ok. Mine is crashing, not hanging. It seems to be a second, different problem.
Last edited by socratis on 9. Mar 2019, 04:32, edited 1 time in total.
Reason: Removed unnecessary verbatim quote of the whole previous message.
Post Reply