Page 1 of 1

VM Paused - cannot resume

Posted: 4. Aug 2012, 05:30
by Oak
Hi all,

I have Vista in virtualbox under Linux and I left it runnig over the night. Now it says "[Paused]" and it's not responding inside the vm to any clicks or key combinations.

So I tried:

Code: Select all

VBoxManage controlvm 'Windows Vista' resume
(yes, "Vinows Vista" is correct name of the vm) which runs without reporting any error, however the VM stays "[Paused]".

Can you advice, what to do now?

Regards,

Oak

Re: VM Paused - cannot resume

Posted: 4. Aug 2012, 09:53
by mpack
VMs can pause themselves in error situations, e.g. check how much disk space is left on the host partition the virtual disk is located on.

Re: VM Paused - cannot resume

Posted: 4. Aug 2012, 10:15
by Oak
Aaaah, you're right, altghough I have enough space in /home/, the vbox doesn't run under the user so I had to run it under the root and / is not set for such high disk usage.
Well, I guess the only way to fix it is compeletely dump all the work done so far and start from scratch??
:-(

Thanks for pointing out to the right direction.

Oak

Re: VM Paused - cannot resume

Posted: 4. Aug 2012, 11:51
by mpack
No, you don't need to discard the work already done - just unregister the VM (in UI: right click VM, select "Remove", tell it not to delete physical files) and then move the VM folder to somewhere with more space, then Machine|Add... to re-register.

Re: VM Paused - cannot resume

Posted: 18. Jun 2020, 17:58
by adamf663b
I have this hapenning with a win10 host and ubuntu guest.
Sometimes after win10 wakens from being suspended, the VM is stuck paused.
Both the virtual manager and cli hang.
killing the virtual machine manager and restarting has it started hung. (spinning circle pointer)

The only way I have found to recover is to kill the vm through the win10 process manager.

I am running virtualbox Version 6.1.8 r137981 (Qt5.6.2)
with an ubuntu 18.4 guest.

Re: VM Paused - cannot resume

Posted: 19. Jun 2020, 09:53
by mpack
Let's leave sleeping dogs alone. Locking this 8 year old topic.