[FIXED] Failed to load unit 'hda' when restoring session

[andrea123z]

Hi pentagonik
I found this forum because I'm dealing with the same problem

- Fedora 23 x64
- Virtualbox latest stable
- Windows 10
- same hda error posted at the beginning

Then I followed your suggestion and installed the testing release and actually the error message slightly changed now, but the issue remains.
BTW I can reproduce this issue every time I save the vm sessions instead of turn off the system.

Failed to load unit 'hda' (VERR_SSM_LOADED_TOO_LITTLE).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

EDIT: downgrading to Virtualbox 4.3 fixes the problem

Any help is appreciated
BR
Andrea

[pentagonik]

@andrea123z Which VBox version was used when saving the state? What happens if you save the state with the test build and restore run from that saved state again?

[jrc55]

I have a similar problem in another forum thread and I'm moving to here because mpack said ....

>We prefer not to have duplicated discussions on this site, so it would be best if those with HDA saved state problem participated the other discussion since a dev is already involved there.

Host is Win 8.1 with 16 GB
Guest is Fedora KDE 64 with guest additions. 3GB memory
This is a clean install in a VM guest of a Fedora 23 KDE 64bit made with 5.0.12. I cannot restore to a snapshot I made using it.

I have tried the 5.0.13.r104845 but that did not fix the problem. The guest was updated also. VBox throws a ...
Failed to load unit 'hda' (VERR_INVALID_PARAMETER)
see attached.
If it matters .... this attachment was for trying to start the VM using a snapshot made with the 5.0.13.

If there is a sequence of events I should follow regarding old/new snapshots/etc then please advise.

[murrayb]

Hi pentagonik,

Yesterday, I created a new virtual machine with Virtual box: VirtualBox-5.0.12-104815-Win.exe on Host: Windows 7 Professional 64 bit and installed guest Windows 10 professional 64 bit.
I made a few snapshots as I did that, and later as I installed some applications. The VM was running the whole time I worked. (there were some re-boots). At the end of the day, I shut down VirtualBox.

Today, I tried restarting those snapshots, and found the message box reported in the original post "Failed to load unit 'hda' (VERR_SSM_LOADED_TOO_LITTLE)".

Then google led me to this thread.

I then tried installing the version VirtualBox-5.0.13-104845-Win.exe you suggested.

When I tried restarting a snapshot, I got a different message:

Code: Select all

Failed to open a session for the virtual machine Win10Pro_x64_1511.

Unsupported version 5 of data unit 'hda' (instance #0, pass 0xffffffff) (VERR_SSM_UNSUPPORTED_DATA_UNIT_VERSION).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

The attachment Logs.5.0.13.104845.zip has some log from this.

Then I tried installing VirtualBox-5.0.10-104061-Win.exe. Attempts to start a snapshot failed with the same message:

Code: Select all

Unsupported version 5 of data unit 'hda' (instance #0, pass 0xffffffff) (VERR_SSM_UNSUPPORTED_DATA_UNIT_VERSION).

The attachment Logs.5.0.10.zip has some log from that.

Then with VirtualBox-5.0.10-104061-Win.exe, I created a new VM, and installed windows 10 in it. I made a snapshot after install. I was able to restart from this snapshot.

[andrea123z]

I can confirm that I used the same VBox test version to save the session and restore and eventually I got the same error.

[michaln]

Then I tried installing VirtualBox-5.0.10-104061-Win.exe. Attempts to start a snapshot failed with the same message:

Code: Select all

Unsupported version 5 of data unit 'hda' (instance #0, pass 0xffffffff) (VERR_SSM_UNSUPPORTED_DATA_UNIT_VERSION).

The attachment Logs.5.0.10.zip has some log from that.

We'll fix that as soon as you supply us with a time machine. That's what happens when you try to load a newer saved state with an older VirtualBox version.

The other problems look like real bugs though.

[harley-peter]

The same problem here on a Linux Host but it seems that this is only a Windows 10 problem. I use a Windows 7 and a Linux VM too and these VMs work.

[pentagonik]

Please have a try at this test build again:

https://www.virtualbox.org/download/tes ... 91-Win.exe

If you need a specific Linux build, please just let me know. Thanks.

[TimThein]

I just installed the test build without upgrading the extension pack. Tried starting a saved session and test build failed. Tried discarding saved session, started VM normally, saved session after logging in, and tried to start saved session. Test build failed again. Here's the error I get:

Failed to start the virtual machine Windows 10 Enterprise (64 bit) Developer.

Failed to load unit 'hda' (VERR_SSM_STRUCTURE_MAGIC).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

[TimThein]

I thought 'hda' referred to the Intel HD Audio controller and so I disabled the audio in my VM's settings after discarding its saved state. I booted up the VM, logged in, saved the state and restored the state successfully.
So, it seems audio is causing the problem, but I have another VM with audio enabled with no problems restoring its state. I re-enabled the audio on the VM with the problem and I've been able to successfully save and restore its state multiple times without any problems.
So, now it seems that to fix this issue for now, you should disable the VM's audio, start the VM, save and restore the VM's execution state, shutdown the VM, and finally re-enable VM's audio.

BTW, I downgraded back to 5.0.12 before I did all of the above.

[jrc55]

Tim,

Your fix partially works for me. Please let me know if you see anything wrong below ...
1. discard state from a snapshot that fails to restore..
2. change to audio off
3. boot and create a new snapshot. That snapshot can be successfully restored. Good info and maybe critical to the final solution.
4. shutdown
5. turn back on the audio
6. boot and create a new snapshot. For me that snapshot can NOT be successfully restored. But I'm not sure why it would. I'm back where I started from before these tests.

I too was using 5.0.12
Thanks for your time.

[pentagonik]

I just installed the test build without upgrading the extension pack. Tried starting a saved session and test build failed. Tried discarding saved session, started VM normally, saved session after logging in, and tried to start saved session. Test build failed again. Here's the error I get:

Failed to start the virtual machine Windows 10 Enterprise (64 bit) Developer.

Failed to load unit 'hda' (VERR_SSM_STRUCTURE_MAGIC).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Can you please provide a VBox.log? Still can't reproduce this locally. Thanks.

[pentagonik]

Successfully reproduced; a new test build will be available soon.

[pentagonik]

Please try one of these newest build available here which should fix the issue:

https://www.virtualbox.org/download/tes ... ux_x86.run
https://www.virtualbox.org/download/tes ... _amd64.run
https://www.virtualbox.org/download/tes ... x86_64.rpm
https://www.virtualbox.org/download/tes ... x86_64.rpm
https://www.virtualbox.org/download/tes ... x86_64.rpm
https://www.virtualbox.org/download/tes ... nOS.tar.gz
https://www.virtualbox.org/download/tes ... 00-Win.exe
https://www.virtualbox.org/download/tes ... 98-OSX.dmg

[gwiesenekker]

Thank you! What is the recommended procedure to install/uninstall this test build on an Ubuntu dpkg managed VirtualBox installation?

Gijsbert