From the hosts terminal/command window type VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use " " if the name has a space in it.
Note if the host is Windows you need to be in the directory that has VBoxManage.exe for the command to work.
Hi Perryg,
I have exactly the same problem after having upgrade to version 4.3.4. How can I access to the "host terminal command window" in the Virtual Box? I don't see any option like that...
Perryg wrote:It means you updated VirtualBox while the guest was in effect running but hibernated.
Use the discard feature in the main window and try again.
Hi Perryg,
Where is that option and what is exactly what I have to do again, execute the command or reinstalling the update? I cannot see such option in my VBox control panel (it is in Spanish, but anyway I cannot see it).
This is done on an individual guest. Click the guest that is not shut down but in saved state and discard that state. Only thing that will be lost is what has not been saved, like an open document that was not saved. Either way this has to be done if you want to run the guest. At the moment it is not mutable and can not be reset.
Perryg wrote:This is done on an individual guest. Click the guest that is not shut down but in saved state and discard that state. Only thing that will be lost is what has not been saved, like an open document that was not saved. Either way this has to be done if you want to run the guest. At the moment it is not mutable and can not be reset.
OK, i understand but, is not possible to fix the problem by doing any other action but not discarding the state of the vms? I'm configuring some important things (work things) using a Windows Server in one of my vms and I cannot discard it at all. Could I install a previous version of VB and run it properly as before?
Perryg wrote:Worth a try I guess. Other than that I don't know what to tell you.
Good luck, and please shut down the guest/s before upgrading in the future.
Thanks Perryg. In your opinion, what version would be the most appropriate to install taking in account the actual one is 4.3.4r91027 and also that I don't remember the version that was installed before?
I would think that it would have to be the exact same version you had before. You may get away with 4.2.18 or .20.
At this point there are no promises it will work or make things worse.
I have just "upgraded" to 4.2.20 and it works again. What I don't understand is why it didn't work after having updated to the latest version of VB if it is supposed that virtual machines are independent and can be executed everywhere...