virtualbox.org

Hello everybody.

I'm posting to report this issue : I can't restore a machine from "saved state", I always get this error :

----------------------------------------------------
Apertura di una sessione per la Macchina Virtuale Windows XP non riuscita.

No error info.

Codice 'uscita: NS_ERROR_CALL_FAILED (0x800706BE)
Componente: ProgressProxy
Interfaccia: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
----------------------------------------------------

There are Messages from Console App :

25/10/13 16:24:18,223 ReportCrash[1868]: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
25/10/13 16:24:18,000 kernel[0]: VBoxNetFlt: was detached from 'en0' (441008192)
25/10/13 16:24:18,000 kernel[0]: VBoxDrv: host_vmxoff -> vmx_use_count=0
25/10/13 16:24:18,936 WindowServer[111]: CGXFilterEventToConnection : Invalid connection
25/10/13 16:24:18,936 WindowServer[111]: CGXFilterEventToConnection : Invalid connection
25/10/13 16:24:18,936 WindowServer[111]: CGXFilterEventToConnection : Invalid connection
25/10/13 16:24:18,936 WindowServer[111]: CGXFilterEventToConnection : Invalid connection
----------------------------------------------------

I also attached VirtualBox Log file and OSX Crash Diagnostic file.

I'm currently using VirtualBox 4.3.0 rev. 89960 running on OSX Mavericks (10.9),
but this is an old issue I also had in OSX Mountain Lion, with every VirtualBox versions after 4.1.18 (which was the last working version succeeding in restoring machines saved states).
I have the same issue on four different iMacs, with Windows XP or Windows 7 as guest operating system.

I tried changing my VMs with every configurable CPU / Video options, but never succeeded in restoring a VM with any Vbox vesion after 4.1.18.

Thanks.
Gabriel

Update:

It's the Quit VirtualBox VM menu command ( or CMD+Q shortcut ) that's (apparently) broken ( in every version after 4.1.18 )
since I can successfully resume machines that were saved from command line :
For the record, saving from command line I have the same issue described here :
viewtopic.php?f=8&t=58155 - VirtualBox closes but leaves VM's icon on the Dock, and zombies processes
(but that's a different problem)

Unfortunately, shutting down OSX calls exactly the Quit VirtualBox VM menu command, so it would be great to fix it !

Thanks.

I've been seeing this exact same error trying to restore a saved state for a Win7 guest in my Linux (kernel 3.12) host ever since upgrading to VirtualBox 4.3. Everything worked fine prior to that.

Update :
same error with 4.3.2

3vi1 wrote:I've been seeing this exact same error trying to restore a saved state for a Win7 guest in my Linux (kernel 3.12) host ever since upgrading to VirtualBox 4.3. Everything worked fine prior to that.

thanks for you feedback

Have you tried saving state from command line ? Does it work for you too ?

I haven't tried from the command line. Further testing shows that the crash I'm seeing is dependent on whether or not 3D video acceleration is enabled for the guest. If I disable it, I can save/restore fie. Enabled, restore always crashes at 93% (SIGSEGV in _mesa_pack_uint_z_row).

So, while I also get an error in progressproxy, it's probably a different bug.

Hello everybody,
I've been using ver. 4.3.4 for some days, and this issue seems to have been fixed

Thanks

I am still experiencing this error running an Ubuntu 13.10 virtual machine in an Ubuntu 13.10 host using VB 4.3.8. The error _seems_ to only occur if I have VB Additions installed. Is this really fixed for everyone else?

Thanks.

Hi @ewh,
I've never had this issue again with any version later than 4.3.4 (I'm running VB under 4 different Macs).

Please note that this is the forum for VB running under OSX host, it's better if you search here : viewforum.php?f=7

I'm sorry I posted in the OSX forum. The OSX forum is the only forum which seems to have a thread displaying the identical behavior I'm seeing in Linux. I'll try the same operations on OSX Mavericks and observe if I can reproduce the issue on Mac with 4.3.8. Depending on my observations, I may open up a new thread on the Linux forum and reference this thread for historical purposes (even though things are occurring on a different host OS).

Thanks.