[Solved] Ubuntu VM stuck paused in Guru Meditation, VERR_PGM_HANDLER_NOT_FOUND

[duaneunderwoodjr]

Hello,

I have an Ubuntu VM that I run in headless mode and then subsequently ssh in after it spins up. I'd gotten myself in a situation where the VM paused somehow and the bridged adapter changed, so the IP address listed in

Code: Select all

/VirtualBox/GuestInfo/Net/0/V4/IP

isn't correct. This was how I usually discovered the IP address to ssh into.

Typically, if the VM wasn't paused and the bridged adapter, I would reset the VM by right-clicking and selecting "Reset". When the VM comes back up, it acquires a new IP address from the correct bridged adapter and I'm able to ssh into it again.

This time, when I selected "Reset", it did not come back up but rather got stuck in Guru Meditation with a "Paused" symbol next to it. All right click options are grayed out. The last line in the log (see attached) is

Code: Select all

emR3Debug: rc=VERR_PGM_HANDLER_NOT_FOUND

Any suggestions on what next steps are? I'd rather not have to remove the VM and start fresh, but even if that's the case, I don't know how to do that because everything is grayed out.

[duaneunderwoodjr]

I ended up just killing the associated VirtualBox process that started the VM which put the VM in an "Aborted" state. I was then able to start it up again.

It looks like that might not be the recommended approach, but it worked in this case: viewtopic.php?f=6&t=92017#p442742

[socratis]

It looks like that might not be the recommended approach, but it worked in this case: viewtopic.php?f=6&t=92017#p442742

I was about to say that the "Reset" that you were doing, or the "kill the process" that you did are not recommended, but then you linked to my answer.

Think of your real desktop computer; do you Reset it or Kill the power? Usually you choose to Shutdown. Do the same for your VMs, corruption is round the corner if you keep on using these tactics...