On Mon, Mar 6, 2017 at 11:47 PM, Kenneth Marcy <kmm...@frontier.com> wrote: > > On 3/6/2017 4:21 PM, Mark Knecht wrote: > > Thanks Duncan. Very helpful. > > In this specific case I was, as best I know right now, down to nothing but the > Windows VM still running in Virtualbox and doing a kill didn't feel right being that > should the VM go down hard I'm left restoring from weekly backups. However It > might not have been out of line to have at least tried a kill -15 to see if I made any > progress. > > Again, I appreciate the the response. > > > I don't consider myself an OS guru, but were my machine having lockup problems, I would want to know how much free RAM is available, what programs are in memory, what programs are running, and which programs are hogging the CPU and other resources to the extent that nothing else gets to share them. > > Utility programs that yield this kind of information may be helpful in identifying culprit programs and their offending processes during operational pauses such as you described. > > > Ken >
I was using top in the console and then the 1 & z options. The machine has 24GB with only about 10GB used. It did not appear that it had ever swapped. The machine wasn't 'slow' - I could switch back and forth from KDE to the console normally. Just no mouse operation in KDE - sort of like KDE was under glass with the cursor above. As I say, the VM continued to operate normally and responded to the VBoxManage command issued from the console. Most likely this was a 1-time event but this conversation is helpful if it shows up a second time. Cheers, Mark
