it’s me… henry

VirutalBox and OSX has come a long way.  I got iATKOS S3 rev 2 and installed it on VirtualBox.  My experience with the installation was actually pretty good.  Nothing to painful and very straight forward.  But after it was done installing and onto the first boot, it would just hang…  I kept reading over and over the forums but nothing was specific to VirtualBox and iATKOS S3 rev 2.

What I do know (from reading different posts from different forums) is that a 32-bit system needs be installed, VirtualBox settings needs to have an additional “ExtraDataItem”, fakesmc and EVO Reboot needs to be unchecked.

Oh, as a side note, I’m running the host in a Linux (Ubuntu 10.04 specifically) environment.  There is no Mac OSX, there’s Mac OSX Server and Mac OSX Server 64-bit.  I used Mac OSX Server for the guest.

Reading somewhere, you need to install atleast one 32-bit app/binary for thesystem to boot into a 32-bit system.  In the boot options of the installer, choose the 32-bit and it will.

All the other stuff is self explanatory.  But after the initial boot, it just hangs.  Digging around, this person made a comment that the kernel they used “qoopz 10.3.0″ worked for them.  I tried the qoopz kernel with the other settings and then it worked.  I booted perfectly.

Now, I just need to install VirtualBox Additional Tools.  But overall, the install went fast, and from what I can tell, OSX runs a lot faster than before.

So, I’ve been using VirtualBox for a while and everything is good.  Then recently, VirtualBox would randomly crash.  What happens WinXP will boot, then it will start, but the screen size is really small (640×480).  So after I boot up, I would try to resize the desktop, but once I got into the display properties, it would crash.  In VirtualBox, it says WinXP is “aborted”.  Googling at what “aborted” meant, it says that it’s just a random crash.

Thinking what changed previously… I remember I’ve been using RDP a lot more, so I disabled it.  That gave me a little time to do something, but the screensize is still 640×480.  So I went to display properties, and it crashed.  I turned RDP back on cause that’s the not cause of it.

Still thinking now….  I look at my firewall (firestarter) and it was “red”.  So I looked and it was blocking NTP (port 123).  So I enabled it to see if that helps.  And now… no more crashing.