virtualbox.org

Okay..

New user here.

I've installed VirtualBox 5.0.12. I'm running OSX 10.11.2 (El Capitan).

Launched the app and went through steps to set up a box (called it "Snow Leopard 10.6.4"). I have the 10.6.4 install disc in my drive (Mid 2010 iMac 21.5 inch with 8G RAM). When prompted I chose the default: "Host Drive 'HL-DT-ST DVDRW GA32N'"

The solid black window got a little larger and a pop-up with a green arrow and a message I can't remember came up and then went away.

Now, I'm staring a window that's solid black, title bar reads "Snow Leopard 10.6.4 [Running]" with little icons at the bottom right and I don't have any idea what to do next!

How do I get the system to install into the VM?

Please Help!

In order to better understand the problem you need to submit some more information. Please read the following: Minimum information needed for assistance. As far as the VBox.log.zip goes, here's what you do:
- Start the VM.
- Record the error message. EXACTLY. Post a screenshot if you have to.
- Shut down the VM.
- Right-click on the VM in the VirtualBox Manager.
- Select "Show Log..."
- Save it, ZIP it and attach it in your response.

On top of that, we'd like to see the "recipe" of the VM.
- Right-click on the VM in the VirtualBox Manager.
- Select "Show in Finder".
- Save it, ZIP it and attach it in your response.

Okay,

There aren't any error messages. The drop downs have large green arrows to the left.

I can't yet post screen shots as I'm new.

I have attached the two zips you requested.

Jim

you can attach screen shots if they aren't too large.

00:00:13.847898 Host RAM: 8192MB total, 1821MB available
...
00:00:14.110147   RamSize           <integer> = 0x00000000e7700000 (3 882 876 928, 3 GB)

You allocated too much memory for your guest. Memory which you cannot afford. Reduce the memory to 1536 MB, increase the Video RAM to 32 MB and close any applications that are eating memory on your host.

@Orion's Bell
BTW, what program did you use to zip the log and the vbox files? From my end (10.9.5) they don't look like "normal" zip files, i.e. dbl-click does not deflate them. I had to use a 3rd party app to get the job done...

socratis wrote:@Orion's Bell
BTW, what program did you use to zip the log and the vbox files? From my end (10.9.5) they don't look like "normal" zip files, i.e. dbl-click does not deflate them. I had to use a 3rd party app to get the job done...

iZip. Can't afford Stuffit.

You can Zip a file on Macs by just right clicking the file and choose Compress from the menu. You don't need a third party program.

Orion's Bell wrote:iZip. Can't afford Stuffit.

How about the built-in right-click on the file(s)/folder(s) and selecting "Compress ..."? No need for using 3rd party, incompatible-generating-data apps.

Edit: Beaten at the finish line

I'm quick like a bunny.

So, I made the suggested changes.

Per the manual, I created a 100G partition on my drive.

Now when I run the VM I get here:



Now what?

One thing that I missed in the first time was the fact that you've selected "MacOS_64" as your template and not the more appropriate "MacOS106_64". Change that. If the boot process fails, maybe your Mac is too new. Take a look at OSX on OSX and see some tips on changing the CPUID (look for posts from rpmurray). Again, post the .vbox and the appropriate log.

socratis wrote:One thing that I missed in the first time was the fact that you've selected "MacOS_64" as your template and not the more appropriate "MacOS106_64". Change that. If the boot process fails, maybe your Mac is too new. Take a look at OSX on OSX and see some tips on changing the CPUID (look for posts from rpmurray). Again, post the .vbox and the appropriate log.

I'm on a mid-2010 21.5" iMac with 3.2Ghz Intel Core i3

New VM - selected Snow Leopard 10.6 for the template

RAM set to 1536
VRAM to 32

I choose to run the new VM. After choosing the internal DVD drive (only choice), I get a momentary Error message:



Then after a few moments it goes away and I'm now stuck at this:



I'm an interface specialist. I worked at Apple in '89 (Hypercard 2.0 team). Also tech support at Symantec in the early 90's, but this stuff is very techy for me.

PLEASE HELP!

socratis wrote:Take a look at OSX on OSX and see some tips on changing the CPUID (look for posts from rpmurray). Again, post the .vbox and the appropriate log.

You missed a couple of things. Especially the bold one...

I would think changing the CPUID would be critical. Just saying.