virtualbox.org

Hi,

After upgrading to version 6.0.0 I'm getting the following error when traying to start from a saved state:

Fallo al abrir una sesión para la máquina virtual Windows XP.

The VM session was aborted.

Result Code: NS_ERROR_FAILURE (0x80004005)
Componente: SessionMachine
Interfaz: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

I had no issues with Version 5.2.22. Downgrading...

Was the saved state created with 6.0.0 as well? Or was the saved state from a previous version?

I am having the same problem after upgrading to Version 6, only on a Windows XP guest. I have upgraded the guest additions, no change. I have also saved from V6, no change.

Saved for version 6.

Can both of you post the "recipe" of the VM, the ".vbox" file?

1. Right-click on the VM in the VirtualBox Manager. Select "Show in Finder/Explorer/Whatever".
2. ZIP the selected ".vbox" file and attach it to your response.

Attached two zip files. Seems like the error is displayed when I have some applications running on XP guest.

Linux Mint 19 XFCE 64-bit as my host, guest OS is Windows XP SP3. I receive the same error.

Seems like Virtualbox 6.0 is very buggy and not actually ready for production. In the Windows host section of this forum, they also cannot restore saved snapshots.

Funny... I can't reproduce it on my OSX (10.11.6) host, with any VM that I threw at it.

Did you try opening an application and then saving the sate? Starting XP guest with no apps opened it start with no error. I can post screenshots.

Madbyte wrote:Did you try opening an application and then saving the sate?

Why would that make a difference, I don't get it...

But to answer your question, I saved and restored in several "weird" points, highly unusual and rather risky; during boot/shutdown/reboot, during the GAs installation. What application did you have in mind? I only have Firefox and CCleaner on my XP VM...

I understand your point. I was testing and I found very few times it not crash doing this: Opening and saving the guest immediately, and then closing the Administrator, therefore it was a coincidence there was no apps opened on guest. But most of times I'm getting the error msg.