VMware Mac OS X Guest Package for ESX, Workstation, Player, Server and Fusion

[macode]

Pretty certain it is because you used SCSI virtual drives. You need to use IDE virtual disk drive and remove SCSI support from the guest. So need to do 3 things:

 

1. Remove SCSI drive and add IDE drive

2. Ensure the line for SCSI is scsi0.present = "FALSE"

3. Remove this line from VMX file firmware = "efi"

 

Hi Donk,

 

thanks, now it is working. Great work!

[D-an-W]

I initially thought this was an ideal solution for me, wanting to create my own image after sucessfully using the pre made one floating about on various blogs etc but after reading the pdf I am not sure...

 

I run a triple boot system (See sig), also have Ubuntu loaded as a VM and the pre made Snow Leopard VMX running fine. My only gripes are the virtual HD was created in parts and I would like to rename the guest name from "Mac OS X Server 10.6" so I decided to try and make my own but I am unsure it would work?

 

I assume my hardware is compatable as I run Mac OS X 10.6.4 already!

 

Windows 7 (64bit)

VMware Player 3.1.0 build-261024

VMware Workstation 7.1.0 build-261024

[sofakng]

Are you supposed to comment out both the guestOS and guestOSAltName for ESXi 4.0U1?

 

If I comment out both of them it won't start and says Invalid Object.

 

If I leave guestOS and change it to darwin10-64 (for Snow Leopard) it says it's this:

 

Guest operating system `darwin10-64' is not

supported. Please select a guest operating system

from the General page on the Options tab of Virtual

Machine Settings.

[MSoK]

Are you supposed to comment out both the guestOS and guestOSAltName for ESXi 4.0U1?

 

If I comment out both of them it won't start and says Invalid Object.

 

If I leave guestOS and change it to darwin10-64 (for Snow Leopard) it says it's this:

 

Guest operating system `darwin10-64' is not

supported. Please select a guest operating system

from the General page on the Options tab of Virtual

Machine Settings.

Just comment out the guestOSAltName for guestOS use darwin or darwin-64, "10" is not supported as SL is not an option in ESX, as it is based on Workstation 6.5 code not 7 code, but will work with Donk's darwin 310b6 iso.

[D-an-W]

Any of the Guru's that frequent this thread know how to stop SL showing the vitual hard drive as an external one (With the Yellow icon)?

 

I assume it isn't done the same way as a hack build as the virtual HD thats created is a SCSI and not sATA?

 

Thanks for any help with this folks...

[Donk]

Just comment out the guestOSAltName for guestOS use darwin or darwin-64, "10" is not supported as SL is not an option in ESX, as it is based on Workstation 6.5 code not 7 code, but will work with Donk's darwin 310b6 iso.

 

 

Well ESXi 4.1 has darwin10 & EFI BIOS support now in vmx and vmx-debug executables. Will take another look once my machine is upgraded.

[MSoK]

Well ESXi 4.1 has darwin10 & EFI BIOS support now in vmx and vmx-debug executables. Will take another look once my machine is upgraded.

Donk,

 

So sounds like more of an update than you were initially expecting, this all sounds good for running SL under ESXi 4.1, just as it runs under Workstation. It also sounds like a modified version of Alberts unlocker may work, MSoK?

[Donk]

Donk,

 

So sounds like more of an update than you were initally expecting, this all sounds good for running SL under ESXi 4.1, just as it runs under Workstation. It also sounds like a modified version of Alberts unlocker may work, MSoK?

 

Yes it is more than I was expecting but sort of to Workstation 7.0 level rather than 7.1. There are more levels to patch in vSphere than Workstation but guess it is doable. From a cursory check vSphere Hypervisor (ESXi's new name), the vCenter daemons on ESXi, vCenter Server and vCenter Client.

[MSoK]

Yes it is more than I was expecting but sort of to Workstation 7.0 level rather than 7.1. There are more levels to patch in vSphere than Workstation but guess it is doable. From a cursory check vSphere Hypervisor (ESXi's new name), the vCenter daemons on ESXi, vCenter Server and vCenter Client.

Donk,

Should the VMware Tools for Darwin be usable under VMware vSphere Hypervisor, bit of a mouthful, I suspect we will stick with ESXi 4.1, or am I jumping the gun, do we need to wait for an update of your Darwin 310b6 iso.

[Donk]

Donk,

Should the VMware Tools for Darwin be usable under VMware vSphere Hypervisor, bit of a mouthful, I suspect we will stick with ESXi 4.1, or am I jumping the gun, do we need to wait for an update of your Darwin 310b6 iso.

 

Should work fine. I have a the release version almost good to go.

[MSoK]

Should work fine. I have a the release version almost good to go.

Brilliant,

Give me a nod when it is ready to go and I will try it on a virgin ESXi 4.1 build.

[kam224]

Hey guys,

I'm trying to get the shared folders working. I'm running windows 7 + snow leopard 10.6.3 + vmware 7

 

I'm trying to share a folder in my documents.

Heres what I've done:

Tried editing the services.sh file (and have undone and redone it a couple times)

Shared the folder I want shared in windows 7 to _vmware.user_

Enabled shared folders in vmware settings

Added that folder in vmware settings

 

Everything I run this command I get:

sudo ./services.sh --restart

 

 

VMware Tools: Shutting down VMware Tools:

umount: /Volumes/VMware Shared Folders: not currently mounted

VMware Tools: Starting VMware Tools:

mount: realpath /Volumes/Shared Folders: No such file or directory

 

If someone could help me out I'd really appreciate it.

Thanks

[Nihilator]

Hey Guys,

 

I have VMware Fusion running on a Hackintosh. I created a Mac OS X 10.6 Server guest and it works great under Fusion. The only thing I have found troublesome is that the hard drive within the Mac OS X 10.6 Server guest is orange.

 

The Mac OS X 10.6 Server guest is seeing the hard drive as an external (AKA: orange) drive. In the past, I have used a kext that fixes this problem on a Hackintosh. My questtion is:

 

Where do I place this kext within the Mac OS X 10.6 Server virtual machine? I don't want to place it in the S/L/E folder. This is not a clean method. I'm used to placing kext's on the EFI partition and letting my Hackintosh load them (via the Chameleon bootloader).

 

In the virtual world, we don't have a Chameleon bootloader. We have the Vmware Fusion bootloader with a modified "darwin.iso" file from Donk.

 

Is the VMware Fusion bootloader smart enough to load kexts from an EFI partition?

[D-an-W]

I simply replaced the Yellow icon with the correct one from my Hacintosh build (Multiboot) as AFAIK the kext files used to solve this problem are sATA based and the virtual drives are usually SCSI based...

[Nihilator]

I simply replaced the Yellow icon with the correct one from my Hacintosh build (Multiboot) as AFAIK the kext files used to solve this problem are sATA based and the virtual drives are usually SCSI based...

 

 

How are you replacing the icon? Are you doing a "Get Info" on your Hackintosh hard drive and then copying and pasting the icon to the "Get Info" window of your virtual machine hard drive?

 

I simply replaced the Yellow icon with the correct one from my Hacintosh build (Multiboot) as AFAIK the kext files used to solve this problem are sATA based and the virtual drives are usually SCSI based...

 

BTW:

 

I'm curious what we can do within a virtual machine:

 

Have you ever tried loading any non-Apple kext's within your virtual machine? If you have....are you loading them from the System/Library/Extensions folder or have you found a way to load them from the virtual machine's EFI partition?

 

Have you ever tried loading the Chameleon bootloader within a virtual machine. Will it work?

[Risner]

Should work fine. I have a the release version almost good to go.

 

Got the release out yet?

 

I've skimmed the last few pages, it looks like there is a workable solution now?

[luckman212]

I'm looking forward to this release too! Even tough I'm just running on Workstation 7.1, I'm hoping it finally stops these annoying popups from VMware warning me about my outdated tools version every time I startup.

 

even though I click that button, it ignores me and still comes back every time

will the new fusion 3.1 based tools fix this (I hope!)

[MSoK]

I'm looking forward to this release too! Even tough I'm just running on Workstation 7.1, I'm hoping it finally stops these annoying popups from VMware warning me about my outdated tools version every time I startup even though I click that button, it ignores me and still comes back every time will the new fusion 3.1 based tools fix this (I hope!)

Luckman,

What version of the darwin iso are you currently using as the 310b6 has the latest Fusion 3.1 VMware Tools, you can download it see the link below, and just mount the darwin.iso and install the VMware Tools, you may wish to use the uninstall option to remove your current tools, this should stop the update error, aslo check your Workstation preferences.

 

http://www.insanelymac.com/forum/index.php...t&p=1495893

 

Do not worry about the b6 designation, that is part of ongoing developments to test installing SL under ESXi 4.0.

[MSoK]

Luckman,

What version of the darwin iso are you currently using as the 310b6 has the latest Fusion 3.1 VMware Tools, you can download it see the link below, and just mount the darwin.iso and install the VMware Tools, you may wish to use the uninstall option to remove your current tools, this should stop the update error, aslo check your Workstation preferences.

 

http://www.insanelymac.com/forum/index.php...t&p=1495893

 

Do not worry about the b6 designation, that is part of ongoing developments to test installing SL under ESXi 4.0.

I have been asked the question "What is ESXi 4.x and do I need it?"

 

Well the answer is in general probably not, ESXi is a server based Hypervisor (sits between the hardware and an OS or GuestOS), so in a sense an OS, but with very limited local functionality. It is designed to be accessed via a remote VMware vSphere client, running on a networked PC. All creating of guestOS's is done from the client, and all access is remote. So in a nutshell great for Server OS's i.e. WIndows Server 2008 R2 etc. but not really relevant to desktop OS's (not completely true as Virtual Desktop Infrastructure VDI uses ESXi to deliver Windows Desktops, but requires additional, at a cost, components included in the View product).

 

So why, you ask are we all busting a gut to get Snow Leopard (SL) running under ESXi, well I guess for the challenge, but also to run the Server version of SL which offers other functions like file and printer sharing etc. Also to give a development / support environment for multiple server based OS's.

 

An ESXi box is a dedicated server environment and you need a separate PC/Laptop running Windows to access it and the guests installed on it.

 

VMWare Fusion, Workstation and Player run as an application under either OS X, Windows or Linux, and allow you to run a Host OS and Guest OS's at the same time and accessing the functinality of both locally, ESXi can only be accessed remotely either via the vSphere client or remote tools, and the guests can only be accessed again via the vShpere client or relevant remote access clients, i.e. RDP, VNC etc.

 

Hope this clarifies the situation, MSoK.

[D-an-W]

Thanks for clearing that up MSoK

[Donk]

Thanks for clearing that up MSoK

 

I have delayed the release for a few days to check out ESXi 4.1. This new version is sort of at Fusion 2.5 levels of functionality, but not quite to Fusion 3.1/Workstation 7.1/Player 3.1 levels. Things it does have are:

 

a. darwin10 & darwin10-64 guestos settings

b. LAPIC version now correct for SL (needed a kernel patcher in Beta 6)

c. EFI BIOS is present which is used with the unlocker, which is what I am now using for Workstation 7.1.0 http://www.insanelymac.com/forum/index.php?showtopic=220750

 

I am trying to see whether I can binary patch vmx and vmx-debug in ESXi 4.1 to natively enable the built-in support. Don't hold your breath as the locations used are different and the code less patchable. If I can by copying an oem.tgz to /bootbank could enable SL support. Still need some hacking on VMX files but no need for darwin.iso apart from tools installation (which really do nothing on ESXi).

 

I am also pretty busy with work so won't be answering much in the way of support questions for now. Sorry if you have been waiting for other answers about issues but there are only so many hours in the day. There are some other great folks here, such as MSoK and ArgVega, who have been helping out.

[D-an-W]

If I reboot my virtual Snow Leopard install I get a VMware file (folder?) on my desktop that doesn't link to anything, is this normal and can it be stopped possibly?

[ArgVega]

I have delayed the release for a few days to check out ESXi 4.1. This new version is sort of at Fusion 2.5 levels of functionality, but not quite to Fusion 3.1/Workstation 7.1/Player 3.1 levels. Things it does have are:

 

a. darwin10 & darwin10-64 guestos settings

b. LAPIC version now correct for SL (needed a kernel patcher in Beta 6)

c. EFI BIOS is present which is used with the unlocker, which is what I am now using for Workstation 7.1.0 http://www.insanelymac.com/forum/index.php?showtopic=220750

 

I am trying to see whether I can binary patch vmx and vmx-debug in ESXi 4.1 to natively enable the built-in support. Don't hold your breath as the locations used are different and the code less patchable. If I can by copying an oem.tgz to /bootbank could enable SL support. Still need some hacking on VMX files but no need for darwin.iso apart from tools installation (which really do nothing on ESXi).

 

I am also pretty busy with work so won't be answering much in the way of support questions for now. Sorry if you have been waiting for other answers about issues but there are only so many hours in the day. There are some other great folks here, such as MSoK and ArgVega, who have been helping out.

 

Haha thanks Donk, I wish though. You and MSoK are on a completely different level of understanding.

 

If I reboot my virtual Snow Leopard install I get a VMware file (folder?) on my desktop that doesn't link to anything, is this normal and can it be stopped possibly?

 

That depends on wether you use/want the use of shared folders between your host and guest. It is supposed to be a a mapping to your host drive on the guest os as a shared folder. This is so you can access the data of the host computer, from the guest os, since darwin tools don't support drag and drop.

 

If you want it removed so it doesn't place a shortcut on your desktop everytime it boots up, it involves removing a line from vmware-tools.sh. Let me know if you are interested and I can help you out.

[luckman212]

Luckman,

What version of the darwin iso are you currently using as the 310b6 has the latest Fusion 3.1 VMware Tools, you can download it see the link below, and just mount the darwin.iso and install the VMware Tools, you may wish to use the uninstall option to remove your current tools, this should stop the update error, aslo check your Workstation preferences.

Do not worry about the b6 designation, that is part of ongoing developments to test installing SL under ESXi 4.0.

thanks MSoK, I installed the 3.1b6 and yes it solved the problem. Can't believe i didnt try this sooner, thanks!

[D-an-W]

That depends on wether you use/want the use of shared folders between your host and guest. It is supposed to be a a mapping to your host drive on the guest os as a shared folder. This is so you can access the data of the host computer, from the guest os, since darwin tools don't support drag and drop.

 

If you want it removed so it doesn't place a shortcut on your desktop everytime it boots up, it involves removing a line from vmware-tools.sh. Let me know if you are interested and I can help you out.

 

I figured it was something like that but it doesn't actually do anything, here is what I mean...