https://www.zdnet.com/article/heres-ano ... ng-system/
By Jack Wallen on Aug. 28, 2023:
Let me paint a picture for you.
I was running a virtual instance of another Linux operating system this morning with VirtualBox. Everything was going fine (as it usually does) until it wasn't. The virtual operating system prompted me for my user password (to run an admin task). When I started typing the admin password, things went a bit south.
Essentially, what happened was VirtualBox locked up my desktop. It wasn't a full-blown lockup, as I could still move my mouse. I couldn't, however, click on anything or interact with the desktop in any way (besides moving the cursor).
Sometimes, it's just a matter of waiting for whatever is happening in the background to finish and control will be handed back over. That did not happen. No matter how long I waited, the desktop remained unresponsive.
I know what you're thinking. All I had to do was power down the machine, restart it, and get back to whatever it was I was doing.
For any given MacOS or Windows user, that's the logical process when the desktop locks up. But this is Linux and with Linux…there is always a way.
I wasn't 100% certain that VirtualBox was the culprit, but I was fairly certain (as that's what I was using when the lockup occurred). And because this isn't my first (or last) go around the block, I knew there was a much easier solution. Besides, Linux users are not fond of either shutting down or rebooting their computers. We like to brag about our uptime. I've had Linux desktop computers stay up for over a year and servers even longer. It's a point of pride.
Of course, I don't really bother with such things any longer and if I feel a reboot is necessary (especially when a new kernel is installed), I won't hesitate.
Today was one of those days where I really didn't feel like rebooting my machine. First off, the power switch has gone out and, in order to restart the machine, I have to remove the case and press a hard-to-reach switch for the machine to power back on. (I'm working on getting a replacement power switch as I type.)
So, when my desktop locked up (without an easy means to reboot), what did I do?
Something your operating system probably can't do.
Here's how it happened:
I logged into my MacBook Pro.
I opened the terminal app.
I used Secure Shell to remote into my desktop, using the command ssh 192.168.1.62.
I checked to see which application was abusing my system resources with the top command.
With the app in question found, I located the Process ID (PID) with the command ps aux | grep Virtual, which gave me the PIDs for both the VirtualBox application and the virtual machine.
I killed the processes with the command kill PID (where PID was the ID for each VirtualBox instance).
I closed the SSH connection with the exit command.Once both VirtualBox instances were closed, I had control of my desktop once again. No reboot needed.
