Mac OS X guest

[notbad]

I used "sudo -s"

[takwing]

thanks all you expert!

I can go a little further....until when I issued the following command:

kextcache -a x86_64 -K /Volumes/Snow/mach_kernel -m /Volumes/Snow/Extra/Extensions.mkext /Volumes/Snow/Extra/Extensions


There were warnings saying something about dependencies cannot be found. Is this normal?
I, anyway, continued with the steps,.... create another VM, with the hdd with SnowLeopard installed mounted.
When starting the vm, I can select "Snow" and "boot" in the bootloader screen (I don't know how to name that boot selection screen)...
but then it crashes...

[notbad]

try to boot with: -v cpus=1

if you get a KP, look what it says.

[takwing]

try to boot with: -v cpus=1

if you get a KP, look what it says.

this is what I obtained:

[notbad]

Have you patched your VB with Black Trinitrons patches?

[takwing]

Have you patched your VB with Black Trinitrons patches?

update....
I can find it now.... I believe you are referrring to "the Patches of VB 3.1.4 PE Windows", which is named as VBx64.zip (I am using 64bit windows7).

After installing the patches,I now get the "unsupported CPU" error that I have encountered before (I am using iCore 5).
For Leopard, I solve this by installing the old voodoo kernel..... should I do the same this time?
or there is a better solution?

[notbad]

Download Empire EFI.iso, and try to boot with it. if it boots do what i have wrote from step 6 in my how to. or you can download i5 compactible kernel and install it, but I dont know how.

[JesusFreak316]

Has anyone gotten a retail snow leopard disk booting in Windows 7? The first post only mentions a hacked version that I would prefer not to use. I saw notbad got it working under linux with a beta OSE version and empireefi but I didn't see a 3.5.1 version for windows, I would rather not compile from source as my ubuntu guest needs usb, and empireefi gives me a black screen.

[mlobo]

Excellent NEWS !!!

System:

- FreeBSD Papi 8.0-STABLE FreeBSD 8.0-STABLE #0 r204106M: Sat Feb 20 03:29:09 UTC 2010
- 8 GRam
- nvidia 9800 GT
- virtualbox-ose-devel-3.1.51.r26899 (SVNned from FBSD ports)

- Mac: IATKOS v7 (as a 64 bit guest Mac)

Worked straight out of the install !!! no EFI boot loader ! just install, rebooted and use !!

And it is dam FAST !!

VBox rules !! Thanks everyone at SUN for this !!

[takwing]

>> - virtualbox-ose-devel-3.1.51.r26899 (SVNned from FBSD ports)

is there a version of this for Windows 7 64-bit platform?
If yes, where can I get it?

[takwing]

Download Empire EFI.iso, and try to boot with it. if it boots do what i have wrote from step 6 in my how to. or you can download i5 compactible kernel and install it, but I dont know how.

I have tried Empire EFI.iso (both legacy, v108, 1085), that does not work.
But may ask "how should I start booting the VM by using Empire EFI.iso?
What I did is:
- startup the vm with the iso file
- I can see 2 icons, one for Empire ISO, one for my SL hdd.
- I simply selection that hdd icon and press Enter
- I have also tried adding the boot option "-v cpus=1"

Why I am asking this is that I cannot use that method to boot up my Leopard hdd also (which can boot by itself).

I can see that there are people using a current build of v3.1.5.... but I just wonder if I can get a Windows version of it.

[takwing]

Strange problem - what am I doing wrong?

In my first trial of installation SL, I have Leopard installed in a snowtest.vdi. and SL in a snow.vdi.
The vm is named as Snowfx.

I now want to create another vm to boot up snowtest.vdi.
I have created the machine as Leopard....

I have modified Leopard.xml according to Snowfx.xml.
These 2 files are the same EXCEPT for the line:
<Machine uuid="{9031bcf0-4930-4780-8226-10084da05c43}" name="Leopard" OSType="FreeBSD" lastStateChange="2010-03-03T03:53:16Z">

I boot the Leopard machine. What I get is only the gray screen with the apple logo.
When I ''close" the machine, I found that the Leopard.xml fall-back to the old/default version (without my additional setting for booting Mac).

I supposed it should boot up!! This is because the 2 vm have the "SAME" machine.xml.

I have tested again that my Snowfx machine can boot up without any problem.

Can someone help me?

[the4thchild]

I realized that my .xml file would fall back to the original unless I closed VB first, then modified the .xml file, then restarted VB. Could this be the same situation as yours?

[notbad]

You have to close VB before editing the .xml file.

For those who want to create SL, but dont have Ubuntu I would suggest to create with Ubuntu liveCD according to my howto and save the .vdi file to your windows partition, then add the .vdi to your windows VB.

[takwing]

You have to close VB before editing the .xml file.

For those who want to create SL, but dont have Ubuntu I would suggest to create with Ubuntu liveCD according to my howto and save the .vdi file to your windows partition, then add the .vdi to your windows VB.

Your suggestion sounds reasonable.
A few problem that I have in my mind:
-By using the liveCD, how can I install VirtualBox (as the live CD cannot be modified in runtime)?
- Any how to save the .vdi file to windows partition? I need to mount my windows' share folder in Ubuntu?