Save State stuck at 0% since recent update (Arch Linux, Vbox 7.0.16r162802)

[HansWerner]

Any idea how to tmp fix this? I can not downgrade nor upgrade to a newer version. It's rolled out by default. No possibility to avoid it. Funny enough, saving some machines work, others not.

Related Ticket:
Somehow Bugtracker links are not allowed here but the Ticket ID: 22059

BTW: the Bugtracker is not indexed in Google, really hard to find anything, even with the provided search.

/E:
Initially version 7.0.16r162802 is causing the issue, now it's also 7.0.18-1

/E1: Found out that all versions above 7.0.14 seem to be affected.

/E2: Temp fix is downgrading, a tiny script for doing so, can be found here:
viewtopic.php?p=548061#p548061

[HansWerner]

Update Today!



I did a

Code: Select all

pacman -Syuuu

and general update and saw this:

virtualbox-guest-iso-7.0.18-1
virtualbox-host-dkms-7.0.18-1

Code: Select all

pacman -Q | grep virtualbox

virtualbox 7.0.18-1
virtualbox-guest-iso 7.0.18-1
virtualbox-host-dkms 7.0.18-1

and

Code: Select all

00:01:35.613975 PDMR3Suspend: 2 714 444 ns run time

00:01:35.613986 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'

00:01:35.613998 Console: Machine state changed to 'Paused'

00:01:36.538584 GUI: Request for close-action to save VM state.

00:01:36.538600 GUI: Saving VM state..

00:01:36.544810 Console: Machine state changed to 'Saving'

00:01:36.545387 Changing the VM state from 'SUSPENDED' to 'SAVING'

-- after that no log --

It seems to do the successful saving as long win11 is not loaded!

The image tag of the phpBB Board seems to be broken:
https://i.ibb.co/tb4tCZv/ORACLE-VBOX-DEBUGGING.png

If win11 is loaded, it gets stuck at 0%.

[lemppari]

I have same problem. Running Virtualbox 7.0.18-162988~Debian~bookworm on Debian host (kernel 6.1.90-1). Guest is Windows Server 2019. Savestate starts and hangs on "0%..."

[bucht]

same issue here.
host machine is arch linux, vb 7.0.18 r162988.
I can save win7 guest, but not win10.

[HansWerner]

I am very thankful for your replies, did you try to shrink or grow vdi (vm disk) sizes? I tried to figure out whether this was the issue. To my surprise it was not, I tried it with a fully fresh Tiny11 and it caused no issues. What I am even more surprised about, we can not debug it and there is no logout put where it gets stuck. Is it a EFI host?

[RonSMeyer1]

I posted about this in the "Using Virtual Box" section. I'm on a Linux Mint host. I cannot save the Windows 10 VM. I have not changed the 'vdi' since the Microsoft debacle in January, when their updates failed because the recovery partition that they themselves allocated at install, was too small. My computer is old and does not have EFI.

I've reverted to 7.0.14.

[HansWerner]

I've reverted to 7.0.14.

How did you revert? BTRFS tools or something like that?

[HansWerner]

With Tiny11 it worked until now, after I've installed everything and ran Windows update (meanwhile the whole machine got stuck when it was running!)

Now it's again stuck in the save state at 0%
https://i.ibb.co/4VfkMHt/grafik.png

Might it be the missing KB5036980???
OR is it the mapped network drive?

No clues in the logs

Code: Select all

00:01:53.321212 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners
00:01:53.321446 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary
00:01:53.321528 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
00:01:53.321534 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=1, Machine-state=6
00:01:53.321554 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
00:01:53.321559 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=1, Machine-state=6
00:02:12.170204 VMMDev: Guest Log: Shared Clipboard: WM_CLIPBOARDUPDATE failed with VERR_ACCESS_DENIED
00:02:39.408595 Console: Machine state changed to 'OnlineSnapshotting'
00:02:39.429124 Saving state of VM, reason 'Snapshot'
00:02:39.429176 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:02:39.433766 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:02:40.400456 PDMR3Suspend: 971 230 656 ns run time
00:02:40.400471 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:02:40.400781 Changing the VM state from 'SUSPENDED' to 'SAVING'
00:04:13.173796 SSM: Cancelled pending operation
00:06:25.454237 GUI: UIMachineView::sltPerformGuestResize: Omitting to send size-hint 1279x959 to guest-screen 0 because frame-buffer is already of the same size.
00:06:25.482005 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:06:26.916666 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:06:50.302280 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:06:51.257090 VMMDevNotifyGuest: fAddEvents=0x80 ignored because enmVMState=18

Seemingly something changed in vbox making it overall really unstable! :O How did that even pass Software testing?

[RonSMeyer1]

I've reverted to 7.0.14.

How did you revert? BTRFS tools or something like that?

There is a link on the download page for older versions. I just uninstalled 7.0.18, and installed 7.0.14. When you start the VM, it recognizes the guest additions are not in sync and asks you to install the one that's currently running, just like always.

[HansWerner]

guest additions are not in sync and asks you to install the one that's currently running,

So you are talking not about vbox host dkms, you are talking about the guest additions?

[HansWerner]

Dude you saved my ass! Your hint lead me to a temp solution!

As root:

Code: Select all

/usr/bin/rcvboxdrv stop
kill -9 $(pgrep -i vbox && pgrep -i virtualbox);
wget "https://download.virtualbox.org/virtualbox/7.0.10/VirtualBox-7.0.10-158379-Linux_amd64.run" 
chmod u+x VirtualBox-7.0.10-158379-Linux_amd64.run
./VirtualBox-7.0.10-158379-Linux_amd64.run
usermod -a -G vboxusers hostuser

The old version can be found by using the https://www.virtualbox.org/wiki/Download_Old_Builds_7_0 page (just type "Vbox 7.0 old version" in ur fav search eninge). Then "all distributions" on your selected version in this case 7.0.10.

I recommend to use 7.0.14, I tested it and it works. 7.0.16 has the "stuck in 0% saving state" bug!

[HansWerner]

[RonSMeyer1]

guest additions are not in sync and asks you to install the one that's currently running,

So you are talking not about vbox host dkms, you are talking about the guest additions?

I did not say that.

But to make it clear: "There is a link on the download page for older versions. I just uninstalled 7.0.18 on the host, and installed 7.0.14 on the host." Use the option to uninstall the program but not the data files (VMs, config etc).

After you have uninstalled 7.0.18 on the host and installed 7.0.14 on the host system, the guest additions in the VM will still be 7.0.18. When you start the VM, it recognizes the guest additions are 7.0.18 but are not in sync with the 7.0.14 host that you just reinstalled. It will ask you to install the guest additions which match the 7.0.14 host that is now currently running, just like it always does when you change versions. You do that, just like you always do..

[HansWerner]

After you have uninstalled 7.0.18 on the host and installed 7.0.14 on the host system, the guest additions in the VM will still be 7.0.18. When you start the VM, it recognizes the guest additions are 7.0.18 but are not in sync with the 7.0.14 host that you just reinstalled. It will ask you to install the guest additions which match the 7.0.14 host that is now currently running, just like it always does when you change versions. You do that, just like you always do..

Thanks for reminding us about that. I did not experience that but over here I have to reinstall them manually all the time. The popup usually does not work. Funny enough in my case it did not even complain about the version differences. However, yes, you should reinstall the guest additions.

Maybe someone can automate that via bash/CLI. Sadly, I do not have time for doing so.

[HansWerner]

I kindly reposted it! For all versions above 7.0.14 in the bug tracker: https://www.virtualbox.org/ticket/22071