Slackware 14.1 froze my system.

[ZenHacker]

I tried installing Slackware 14.1 64-bit from the ISO file provided at http://mirrors.slackware.com/slackware/ ... -14.1-iso/. When I logged into the install program as root, my entire system became virtually unresponsive. I checked the memory and CPU usage with top, and it showed the VirtualBox VM process as using only slightly more memory than the Kernel Task, and less CPU time. I thought this was rather odd. How could it be freezing my system with these stats? To free up resources, I sent the TERM signal to one of my Google Chrome Helper processes, since those tend to be the main memory hogs in my system; obviously the Chrome processes weren't the real culprits this time, but I figured getting rid of one or two of them might help alleviate the problem. I now have about 53 megabytes free memory and the VirtualBox VM is sleeping. I'm kind of afraid that if I start it again, my system will become once again unresponsive. My question is why is this happening, and what can I do to fix it?

EDIT: I'm using Mac OS X El Capitain as my host, if that is at all relevant.

[Perryg]

Minimal information needed to be able to help

[ZenHacker]

Okay, I'm trying to upload a zip of the log file for this VM, like those instructions said, but I'm having trouble compressing it. I've used the following commands, with corresponding errors:

Code: Select all

bash-3.2$ zip VBox.log
	zip warning: missing end signature--probably not a zip file (did you
	zip warning: remember to use binary mode when you transferred it?)
	zip warning: (if you are trying to read a damaged archive try -F)

zip error: Zip file structure invalid (VBox.log)

bash-3.2$ zip -B VBox.log

zip error: Invalid command arguments (short option 'B' not supported)

bash-3.2$ zip VBox.log --binary

zip error: Invalid command arguments (long option 'binary' not supported)

Note: I've used zip instead of gzip because I'm not sure if people using Windows would be able to view a gzipped file without special software.

[Perryg]

Most of us that can make heads or tails about this can read just about anything you can send. Just qzip it or what ever compression program is native to your host.

[ZenHacker]

Okay, I've gzipped it. I don't know how to attach it to a post. I can't find an "upload" option.

EDIT: Never mind. I found it.

[Perryg]

Look below the reply window.

[ZenHacker]

I got it. The file is attached to my previous post.

[Perryg]

00:00:07.765996 Host RAM: 4096MB total, 619MB available
00:00:08.553139 RamSize <integer> = 0x0000000020000000 (536 870 912, 512 MB)

I don't see anything that indicates that this hung or crashed in the log file, but I would try closing some programs and free up memory and see if it works.

[ZenHacker]

Okay, I'll try that. Thank you.

[mpack]

Most of us that can make heads or tails about this can read just about anything you can send. Just qzip it or what ever compression program is native to your host.

That said, I congratulate the OP on being one of the few (in fact the only one I can think of) to even consider what we can use. Most just throw us obscure zip variant, tgz, lzh, rar, bz2 etc all without a second thought.

... but yes, in part because of this we can in fact handle all those and more.

[socratis]

@ZenHacker
For future reference, on OSX, the easiest way is to right-click on a single or multiple files or folders that you want to compress and select "Compress <file>" from the context menu. If you want to zip a file from the command line, use:

Code: Select all

zip VBox.log.zip VBox.log

More information, in the Terminal: man zip