Help - Search - Members - Calendar
Full Version: VMware Mac OS X Guest Package for ESX, Workstation, Player, Server and Fusion
InsanelyMac Forum > OSx86 Project > Multi Booting and Virtualisation
Pages: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17
Donk
Update 1: Edited 3 posts into one

Update 2: The files can now be found here:

http://www.filedropper.com/vmware-darwin-200
http://www.filedropper.com/vmware-darwin-voodoo
http://www.filedropper.com/darwin-wks7 (Workstation 7 and Snow Leopard support)


Update 2: Would everyone make sure they add or change lines in VMX to this. It solves quite a few problems:

monitor.virtual_exec = "hardware"
monitor.virtual_mmu = "software"


So after months of testing here is a new version of the package to run retail Mac OS X in VMware. This release supports the following products:
  • VMware Workstation 6.5 (Windows & Linux)
  • VMware Player 2.5 (Windows & Linux)
  • VMware Server 2.0 (Windows & Linux)
  • VMware Fusion 2.0 (Mac OS X)
  • VMware ESX 4.0
  • VMware ESXi 4.0
It is compatible with the other methods that have been previously described in the forums. I have attached the manual to the post.

Problem Resolution

To help me understand some of the issues that are being seen can I ask everyone who has a problem to post the following information please when first logging the problem:

  • VMware product and version being used
  • Host operating system
  • Host CPU
  • Vanilla Leopard or other distro
  • Version of Leopard 10.5.6, 10.5.7 etc.
  • Please attach the VMX file
  • Please attach the latest vmware.log file

(Please remember I have stated that I do not support anything other than vanilla with this method.)

For manual clarifications and additional updates from testing; e.g. ESX configuration please use your judgement as to whether to post this information. Also remember I do this in my spare time, and have full time job, family and other interests, so I will answer when I can.

Experimental Package for Core 2 Quad and Core i7

Various issues have been raised with these processors. I have put together an experimental update to the package which uses the Voodoo 2 alpha 3 kernel. If you are having issues then please try the changes. If you are not experiencing any problems do not use this package until such time as it is rolled into the main one. If you have a non-Core processor but that is VT-x enabled such as P4D, then this may also be useful to you.

If you do try it then read the manual and the update PDFs thoroughly before starting.
rschultz101
virtualbox 3.0 beta possible

first thanks for the post !

have not done any testing yet, but VB 3.0 might also be a good candidate, .. it's free

don't have vt-x on my desktop,... so need to upgrade,...

can you maybe try, to use your working VM image, and give VB 3.0 a shot ?

it be nice to be able to fire up an VM at work with leo in it,...
Donk
QUOTE (rschultz101 @ Jun 26 2009, 07:06 PM) *
virtualbox 3.0 beta possible

first thanks for the post !

have not done any testing yet, but VB 3.0 might also be a good candidate, .. it's free

don't have vt-x on my desktop,... so need to upgrade,...

can you maybe try, to use your working VM image, and give VB 3.0 a shot ?

it be nice to be able to fire up an VM at work with leo in it,...


Sorry don't use VirtualBox and not sure it supports enough of the hardware required to make this work.
Desserts
QUOTE (Donk @ Jun 26 2009, 05:56 PM) *
So after months of testing here is a new version of the package to run retail Mac OS X in VMware. This release supports the following products:
  • VMware Workstation 6.5 (Windows & Linux)
  • VMware Player 2.5 (Windows & Linux)
  • VMware Server 2.0 (Windows & Linux)
  • VMware Fusion 2.0 (Mac OS X)
  • VMware ESX 4.0
  • VMware ESXi 4.0
It is compatible with the other methods that have been previously described in the forums. I have attached the manual to the post and the package is available at http://www.mediafire.com/?sharekey=2528947...04e75f6e8ebb871.


Donk,

Thanks for this it works so smoothly!

Can I provide some feedback for changes to your manual?

Section 4.1.1:
Consider a new item to explain a bit more clearly about running id and show which number one needs. In line 3 I was unsure what the UID of the guest user was!

I struggled to get into the boot screen that allowed me to enter boot options like -v -f -x. Could you add instructions how to do this?

Chris
Donk
QUOTE (Desserts @ Jun 27 2009, 11:54 AM) *
Donk,

Thanks for this it works so smoothly!

Can I provide some feedback for changes to your manual?

Section 4.1.1:
Consider a new item to explain a bit more clearly about running id and show which number one needs. In line 3 I was unsure what the UID of the guest user was!

I struggled to get into the boot screen that allowed me to enter boot options like -v -f -x. Could you add instructions how to do this?

Chris


Of course feedback is great. Manual was a little hurried written over the last 3 days. If I didn't get it done now it would have been weeks before I could release as about to hit a busy spot at work and then family holiday.

1. To get the uid open a terminal prompt as the user you have logged into Leopard. At the prompt type id and you should get output like this:

uid=501(donk) gid=20(staff) groups=20(staff),98(_lpadmin),81(_appserveradm),79(_appserverusr),80(admin)

I have highlighted the number that is required. If a single user system it is likely to be 501.

2. Get the boot prompt requires some quick key presses as the timeout values in VMware's booter is very quick. The best way is to make sure that the guest has focus at the BIOS screen and hold down the Alt key (Windows/Linux) or Option key (Mac OS X). This brings up the prompt as shown in the first attached screenshot. Press the key you need and then immediately press the F8 key. This should give you the usual boot prompt. The timeout is hardcoded in the booter somewhere and would need to be patched to fix. I agree it is a bit fast but normally don't need it and so speeds up regular boots.
SnoutWeezel
Superb work + beautiful guide, Donk, thanks muchly, will try it out ASAP

What do you think are the prospects for SNLx64 in latest VMware Workstation on W7x64 ?

Cheers, SW


CODE
PS: errata for v1.1 ...

4.3 Sound
... "the only KNOW(N) driver"

bottom of p.10: "This can ..." end of sentence MIA
Donk
QUOTE (SnoutWeezel @ Jun 28 2009, 11:35 PM) *
Superb work + beautiful guide, Donk, thanks muchly, will try it out ASAP

What do you think are the prospects for SNLx64 in latest VMware Workstation on W7x64 ?

Cheers, SW


CODE
PS: errata for v1.1 ...

4.3 Sound
... "the only KNOW(N) driver"

bottom of p.10: "This can ..." end of sentence MIA


Snow Leopard appears to be a no-go. I have tried the WWDC seed and it needs additional support from VMware (which I think is coming but it is in the products under beta test).

Thanks for corrections to manual, will update in a week or so, once I get more feedback.
Yuan Chen
Hi, donk

When I install the darwin into the VMware system by the command setup.cmd install (I use admin)

it work fine

but When I open my guest system and power on it say that the CPU have block or something.

while I uninstall it. it work normal
Click to view attachment Click to view attachment

my vm setting
CODE
.encoding = "windows-1252"
config.version = "8"
virtualHW.version = "7"
scsi0.present = "TRUE"
memsize = "512"
ide0:0.present = "TRUE"
ide0:0.fileName = "MacOSX-000001.vmdk"
ide1:0.present = "TRUE"
ide1:0.fileName = "G:"
ide1:0.deviceType = "cdrom-raw"
floppy0.autodetect = "TRUE"
ethernet0.present = "TRUE"
ethernet0.connectionType = "nat"
ethernet0.wakeOnPcktRcv = "FALSE"
ethernet0.virtualDev = "e1000"
sound.present = "TRUE"
sound.fileName = "-1"
sound.autodetect = "TRUE"
mks.enable3d = "TRUE"
pciBridge0.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "TRUE"
roamingVM.exitBehavior = "go"
displayName = "MacOSX"
guestOS = "darwin"
nvram = "MacOSX.nvram"
virtualHW.productCompatibility = "hosted"
ft.secondary0.enabled = "TRUE"
tools.upgrade.policy = "useGlobal"

extendedConfigFile = "MacOSX.vmxf"

floppy0.fileName = "A:"

floppy0.present = "FALSE"

ethernet0.addressType = "generated"
uuid.location = "56 4d c7 a7 0a 45 c4 50-79 a8 61 af 30 b6 52 b6"
uuid.bios = "56 4d c7 a7 0a 45 c4 50-79 a8 61 af 30 b6 52 b6"
ide0:0.redo = ""
vmotion.checkpointFBSize = "134217728"
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
scsi0.pciSlotNumber = "-1"
ethernet0.pciSlotNumber = "32"
sound.pciSlotNumber = "33"
vmci0.pciSlotNumber = "34"
ethernet0.generatedAddress = "00:0c:29:b6:52:b6"
ethernet0.generatedAddressOffset = "0"
vmci0.id = "817255094"

debugStub.linuxOffsets = "0x0,0xffffffff,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0"

tools.syncTime = "FALSE"
isolation.tools.hgfs.disable = "FALSE"
sharedFolder.maxNum = "1"
sharedFolder0.present = "TRUE"
sharedFolder0.enabled = "TRUE"
sharedFolder0.readAccess = "TRUE"
sharedFolder0.writeAccess = "TRUE"
sharedFolder0.hostPath = "D:\Nguyen\Downloads\Compressed\Mac"
sharedFolder0.guestName = "Mac"
sharedFolder0.expiration = "session"

ide1:0.startConnected = "TRUE"
ich7m.present = "TRUE"
smc.present = "FALSE"
keyboard.vusb.enable = "TRUE"
mouse.vusb.enable = "TRUE"
Donk
QUOTE (Yuan Chen @ Jun 29 2009, 10:20 AM) *
Hi, donk

When I install the darwin into the VMware system by the command setup.cmd install (I use admin)

it work fine

but When I open my guest system and power on it say that the CPU have block or something.

while I uninstall it. it work normal


As explained in the document you need to have a supported CPU. What CPU do you have and have you checked it on the Intel web site linked to in the manual?
Yuan Chen
QUOTE (Donk @ Jun 29 2009, 06:10 PM) *
As explained in the document you need to have a supported CPU. What CPU do you have and have you checked it on the Intel web site linked to in the manual?


Intel Core 2 Quad Q6600

is this CPU don't support. so is there anyway I can do. I just want to have the ability to copy & paste between host and guest.

Thanks.
Donk
QUOTE (Yuan Chen @ Jun 29 2009, 11:18 AM) *
Intel Core 2 Quad Q6600

is this CPU don't support. so is there anyway I can do. I just want to have the ability to copy & paste between host and guest.

Thanks.


It should be supported but I have had several reports it currently isn't working. Some things to check out:

1. VT-x is enabled in the BIOS
2. Change you VMX file and make sure you have these settings:

guestos = "darwin-64"
monitor.virtual_exec = "hardware"
monitor.virtual_mmu = "software"
Yuan Chen
I have config the vmx file

guestos = "darwin-64"
ich7m.present = "TRUE"
smc.present = "FALSE"
keyboard.vusb.enable = "TRUE"
mouse.vusb.enable = "TRUE"
monitor.virtual_exec = "hardware"
monitor.virtual_mmu = "software"

Click to view attachment

but still the same.

I don't know what you mean
VT-x is enabled in the BIOS
How to check that. BIOS in host or guest
Donk
QUOTE (Yuan Chen @ Jun 29 2009, 12:24 PM) *
I have config the vmx file

guestos = "darwin-64"
ich7m.present = "TRUE"
smc.present = "FALSE"
keyboard.vusb.enable = "TRUE"
mouse.vusb.enable = "TRUE"
monitor.virtual_exec = "hardware"
monitor.virtual_mmu = "software"

Click to view attachment

but still the same.

I don't know what you mean
VT-x is enabled in the BIOS
How to check that. BIOS in host or guest


You need to check on the real machine's BIOS settings. I can't tell you what it will say as different BIOSes have different areas for configuring it. You can also run the program Processor Check for 64-Bit Compatibility to cross check the settings. http://www.vmware.com/download/ws/drivers_tools.html
VMErik
QUOTE (Donk @ Jun 26 2009, 07:56 PM) *
So after months of testing here is a new version of the package to run retail Mac OS X in VMware. This release supports the following products:
  • VMware Workstation 6.5 (Windows & Linux)
  • VMware Player 2.5 (Windows & Linux)
  • VMware Server 2.0 (Windows & Linux)
  • VMware Fusion 2.0 (Mac OS X)
  • VMware ESX 4.0
  • VMware ESXi 4.0
It is compatible with the other methods that have been previously described in the forums. I have attached the manual to the post and the package is available at http://www.mediafire.com/?sharekey=2528947...04e75f6e8ebb871.


Excellent job !

A few little points to add into the documentation concerning the ESX(i) configurations:
If you want to verify whether or not your CPU is compatible, the best method is to use the VMware cpuid utility, available at: http://www.vmware.com/download/shared_utilities.html. It's an ISO image. Burn it to a CD, boot your machine and look for the line "Supports 64 bit VMware". If it's yes, you're good to go, if it's no, stop beating your head against the desk and find another machine. Side note: Xeon based HP DL380 G4's are a no go, but DELL PE2950 gen III with Xeon 5450's work peachy.

When you copy up the vmware-darwin-200 package to the ESX server, make sure that you put it on local storage and don't run the commands over and over again from a shared volume since your backups will be overwritten each time you run it on another server. Note that you will have to run this script on all the servers in a cluster in order for an OSX VM to be able to move freely and reboot from any of the ESX servers.

Do NOT run the "setup.sh --install" twice or you will start getting messages that darwinGuest is not a supported GuestOS.

On ESX Server I used the LSI Parallel card and that didn't work. The disks show up, but as read only. Switching to IDE seems to be the only currrent choice on ESX for the moment. You're limited to 2 disks with that configuration, but you can always add the GlobalSAN iSCSI driver for direct iSCSI attachments later if required (or NFS or whatever turns your crank).

Congratulations guys - awesome work!
Donk
QUOTE (VMErik @ Jun 29 2009, 04:05 PM) *
Excellent job !

A few little points to add into the documentation concerning the ESX(i) configurations:
If you want to verify whether or not your CPU is compatible, the best method is to use the VMware cpuid utility, available at: http://www.vmware.com/download/shared_utilities.html. It's an ISO image. Burn it to a CD, boot your machine and look for the line "Supports 64 bit VMware". If it's yes, you're good to go, if it's no, stop beating your head against the desk and find another machine. Side note: Xeon based HP DL380 G4's are a no go, but DELL PE2950 gen III with Xeon 5450's work peachy.

When you copy up the vmware-darwin-200 package to the ESX server, make sure that you put it on local storage and don't run the commands over and over again from a shared volume since your backups will be overwritten each time you run it on another server. Note that you will have to run this script on all the servers in a cluster in order for an OSX VM to be able to move freely and reboot from any of the ESX servers.

Do NOT run the "setup.sh --install" twice or you will start getting messages that darwinGuest is not a supported GuestOS.

On ESX Server I used the LSI Parallel card and that didn't work. The disks show up, but as read only. Switching to IDE seems to be the only currrent choice on ESX for the moment. You're limited to 2 disks with that configuration, but you can always add the GlobalSAN iSCSI driver for direct iSCSI attachments later if required (or NFS or whatever turns your crank).

Congratulations guys - awesome work!


Good points and a flaw in my testing as I only had one standard alone server I could use. I will setup a test cluster under VMware Workstation and try to test in future.

For ESX it is easy to upload to the actual COS and use it's storage, but ESXi is not the same as it resets the storage after reboot. I will do a little testing this week on that, but have a busy schedule at work.

Thanks for the LSILogic heads-up. Again OK on hosted products but didn't have enough time for ESX.

Keep the feedback coming!
camiloa
Hi Donk

Thx for this new great manual...

Im having some problems that after reading almost all of your topics, i couldnt find the solution.

I correctly install ToH rc2 and now im trying to boot from HD using darwin but im getting the following error.



Im using the following config
I also tried using other-64, darwin-64, -legacy -f ...

Im using Workstation 6.5 in a Intel Core 2 T8100. I run the Vwware 64bit program and looks like my laptop is capable to run 64bit guest.

Thanks a lot in advance,

Camilo



CODE
.encoding = "windows-1252"
config.version = "8"
virtualHW.version = "7"
numvcpus = "1"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
memsize = "1024"
ide0:0.present = "TRUE"
ide0:0.fileName = "Darwin.vmdk"
ide1:0.present = "TRUE"
ide1:0.fileName = "auto detect"
ide1:0.deviceType = "cdrom-raw"
floppy0.startConnected = "FALSE"
floppy0.autodetect = "TRUE"
ethernet0.present = "TRUE"
ethernet0.connectionType = "hostonly"
ethernet0.virtualDev = "e1000"
ethernet0.wakeOnPcktRcv = "FALSE"
usb.present = "TRUE"
ehci.present = "TRUE"
sound.present = "TRUE"
sound.fileName = "Realtek HD Audio output"
sound.autodetect = "FALSE"
mks.enable3d = "FALSE"
pciBridge0.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "TRUE"
roamingVM.exitBehavior = "go"
displayName = "Darwin"

nvram = "Darwin.nvram"
virtualHW.productCompatibility = "hosted"
ft.secondary0.enabled = "TRUE"
tools.upgrade.policy = "useGlobal"

extendedConfigFile = "Darwin.vmxf"

ethernet0.addressType = "generated"
uuid.location = "56 4d 99 a0 b3 16 cd c8-9e bc 90 26 17 1d 5e fd"
uuid.bios = "56 4d 99 a0 b3 16 cd c8-9e bc 90 26 17 1d 5e fd"
ide0:0.redo = ""
vmotion.checkpointFBSize = "16777216"
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
scsi0.pciSlotNumber = "16"
usb.pciSlotNumber = "32"
ethernet0.pciSlotNumber = "33"
sound.pciSlotNumber = "34"
ehci.pciSlotNumber = "35"
vmci0.pciSlotNumber = "36"
ethernet0.generatedAddress = "00:0c:29:1d:5e:fd"
ethernet0.generatedAddressOffset = "0"
vmci0.id = "387800829"
tools.remindInstall = "FALSE"

ide1:0.autodetect = "TRUE"
floppy0.fileName = "A:"

guestOS = "darwin"
ich7m.present = "TRUE"
smc.present = "FALSE"
keyboard.vusb.enable = "TRUE"
mouse.vusb.enable = "TRUE"

ide1:0.startConnected = "TRUE"
usb:0.present = "TRUE"
usb:1.present = "TRUE"
usb:1.deviceType = "hub"
usb:0.deviceType = "mouse"
monitor.virtual_exec = "hardware"
monitor.virtual_mmu = "hardware"

debugStub.linuxOffsets = "0x0,0xffffffff,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0"

usb.generic.autoconnect = "TRUE"
sound.startConnected = "TRUE"

vmi.present = "FALSE"

disable_acceleration = "FALSE"

usb.generic.allowHID = "TRUE"
Yuan Chen
QUOTE (Donk @ Jun 29 2009, 09:57 PM) *
You need to check on the real machine's BIOS settings. I can't tell you what it will say as different BIOSes have different areas for configuring it. You can also run the program Processor Check for 64-Bit Compatibility to cross check the settings. http://www.vmware.com/download/ws/drivers_tools.html


I have checked for 64-Bit Compatibility.
It's compatible.
Click to view attachment
RobertJordan
Donk,

Awesome to see this! Excitedly, I gave it a try. I have a Intel Core2Duo E8200 machine running VistaBusiness x64 with VMWare Server 2.0.1 on it. Using the VMware-guest64check-6.0.0-45731.exe, it says I'm x64 capable.

I installed 10.5.6 on a 20GB partition (note: I had to make Disk Utility use a Guid Partition Table instead of the default) and it looked like it was working.

It starts up and sits at the startup screen with the Apple icon with the spinner animating, but that's it.

What should I do to debug?

(also, how do I emulate the command-v on startup to get a verbose boot?)

Thanks so much!

RJ


QUOTE (Donk @ Jun 26 2009, 10:56 AM) *
So after months of testing here is a new version of the package to run retail Mac OS X in VMware. This release supports the following products:
  • VMware Workstation 6.5 (Windows & Linux)
  • VMware Player 2.5 (Windows & Linux)
  • VMware Server 2.0 (Windows & Linux)
  • VMware Fusion 2.0 (Mac OS X)
  • VMware ESX 4.0
  • VMware ESXi 4.0
It is compatible with the other methods that have been previously described in the forums. I have attached the manual to the post and the package is available at http://www.mediafire.com/?sharekey=2528947...04e75f6e8ebb871.
RobertJordan
A follow up... I was able to get into a place to hit F8 and then -v to get a verbose boot.

It appears to be hanging, repeating lines like this

CODE
VMWare[0x44580b00]::joinPMtree - could not find the hub device
...
(a few of those, then a bunch of...)
localhost com.apple.launcd[1] (com.apple.SystemStarter): Failed to count the number of files in "/System/Library/StartupItems": No such file or directory


Seems like a USB issue?

Here are my additions/changes to the .vmx file:

CODE
guestOS = "darwin-64"
ich7m.present = "TRUE"
smc.present = "FALSE"
keyboard.vusb.enable = "TRUE"
mouse.vusb.enable = "TRUE"
monitor.virtual_exec = "hardware"
monitor.virtual_mmu = "software"


Any ideas?

Thanks!

- RJ
VMErik
QUOTE (Donk @ Jun 29 2009, 06:55 PM) *
Good points and a flaw in my testing as I only had one standard alone server I could use. I will setup a test cluster under VMware Workstation and try to test in future.

For ESX it is easy to upload to the actual COS and use it's storage, but ESXi is not the same as it resets the storage after reboot. I will do a little testing this week on that, but have a busy schedule at work.

Thanks for the LSILogic heads-up. Again OK on hosted products but didn't have enough time for ESX.

Keep the feedback coming!


A couple of secondary points to look into. I had originally installed my VM on the internal storage of the ESX Server and since this machine will be getting reinstalled, I copied the VM using the regular VMware tools over to an iSCSI volume. I tried to boot and ended up with the regular PXE boot so I checked the vmx file and found that it had been modified by ESX and replaced darwin-64 with other.

I replaced the original darwin-64 value and tried to start the machine and am now getting:
CODE
Power On virtual machine
OSXS
The guest operating system 'darwin64Guest' is not supported.
Administrateur
VC-VSPHERE
01/07/2009 10:25:28
01/07/2009 10:25:28
01/07/2009 10:25:28


I'm going to try and rebuild a new VM on the iSCSI datastore and re-use the existing disk to see if that works, but this is an annoying problem since it means that you have to be extra careful and using the standard VMware tools to manage an OSX VM.
RobertJordan
Whew! I finally got MacOS X on a VM - Thank you so much, Donk!

I ended up pulling the monitor.* lines in the VMX file and reinstalling MacOS X on the vhd.

I've been able to update to 10.5.7, but every so often it hangs and I get these:



Where it says "You need to restart your computer. Hold down the Power button for several seconds or press the Restart button."

Ideas as to how I should diagnose this one?
Donk
Problem Resolution

To help me understand some of the issues that are being seen can I ask everyone who has a problem to post the following information please when first logging the problem:
  1. VMware product and version being used
  2. Host operating system
  3. Host CPU
  4. Vanilla Leopard or other distro
  5. Version of Leopard 10.5.6, 10.5.7 etc.
  6. Please attach the VMX file
  7. Please attach the latest vmware.log file
(Please remember I have stated that I do not support anything other than vanilla with this method.)

For manual clarifications and additional updates from testing; e.g. ESX configuration please use your judgement as to whether to post this information. Also remember I do this in my spare time, and have full time job, family and other interests, so I will answer when I can.
Donk
QUOTE (RobertJordan @ Jul 1 2009, 11:59 AM) *
Whew! I finally got MacOS X on a VM - Thank you so much, Donk!

I ended up pulling the monitor.* lines in the VMX file and reinstalling MacOS X on the vhd.

I've been able to update to 10.5.7, but every so often it hangs and I get these:



Where it says "You need to restart your computer. Hold down the Power button for several seconds or press the Restart button."

Ideas as to how I should diagnose this one?


One tip from VMware is to switch of a the power management settings so that the virtual machine does not go to sleep. That can cause this issue. I have also used the Caffeine application to ensure the guest stays awake.
RobertJordan
QUOTE (Donk @ Jul 1 2009, 07:47 AM) *
One tip from VMware is to switch of a the power management settings so that the virtual machine does not go to sleep. That can cause this issue. I have also used the Caffeine application to ensure the guest stays awake.


Good call on Caffeine 1.0.4, I'll try that and let you know what happens.

There's some oddness sometimes with keyboard repeating (appears as if a key's stuck), but I'll have to watch for it to happen and capture some logs.

Thanks again for the awesome effort, Donk!

RJ


Host: Intel Core2Duo E8200, Vista Business x64, VMWare Server 2.0.1,
Guest: Leopard 10.5.6 (updated to 10.5.7)
Donk
QUOTE (RobertJordan @ Jul 1 2009, 04:13 PM) *
Good call on Caffeine 1.0.4, I'll try that and let you know what happens.

There's some oddness sometimes with keyboard repeating (appears as if a key's stuck), but I'll have to watch for it to happen and capture some logs.

Thanks again for the awesome effort, Donk!

RJ
Host: Intel Core2Duo E8200, Vista Business x64, VMWare Server 2.0.1,
Guest: Leopard 10.5.6 (updated to 10.5.7)


Switch to PS2 keyboard by editing VMX file change keyboard.vusb.enable to FALSE. the tools iso image will then load the Voodoo PS2 Controller for you.

QUOTE (Yuan Chen @ Jun 30 2009, 11:33 PM) *
I have checked for 64-Bit Compatibility.
It's compatible.
Click to view attachment


I'm pretty certain it is a problem with VMware due to something I have seen, but am under NDA. Not sure what to suggest next. Let me have a think about it, as maybe a different kernel may be possible. Voodoo kernel 2 alpha 3 is available and it is supposed to fix some FSB frequency issues with theses processors. Whilst it is possible to add to the CD image booting is a PITA.

QUOTE (camiloa @ Jun 30 2009, 08:55 PM) *
Hi Donk

Thx for this new great manual...

Im having some problems that after reading almost all of your topics, i couldnt find the solution.

I correctly install ToH rc2 and now im trying to boot from HD using darwin but im getting the following error.



Im using the following config
I also tried using other-64, darwin-64, -legacy -f ...

Im using Workstation 6.5 in a Intel Core 2 T8100. I run the Vwware 64bit program and looks like my laptop is capable to run 64bit guest.

Thanks a lot in advance,

Camilo


Well this work is only for retail Leopard and I don't test other distros. However I think you should at least try with the following settings in your VMX file:

guestOS = "darwin-64"
ich7m.present = "TRUE"
smc.present = "FALSE"
keyboard.vusb.enable = "FALSE"
mouse.vusb.enable = "TRUE"
usb:0.present = "TRUE"
usb:1.present = "TRUE"
usb:1.deviceType = "hub"
usb:0.deviceType = "mouse"
monitor.virtual_exec = "hardware"
monitor.virtual_mmu = "software"
usb.generic.allowHID = "FALSE" <-- never use this unless you have more than one keyboard and mouse!
RobertJordan
QUOTE (Donk @ Jul 1 2009, 10:55 AM) *
Switch to PS2 keyboard by editing VMX file change keyboard.vusb.enable to FALSE. the tools iso image will then load the Voodoo PS2 Controller for you.


Caffeine has been working for me so far... none of those odd hangs. Great recommendation.

Also, I changed the keyboard.vusb.enable to "FALSE" and no intermittent sticky key repeats since then.

Followed the instructions to modify the Boot.plist for a larger screen - worked as written.

Awesome job, Donk!

RJ
RobertJordan
Hi, Donk,

Here's another one... I want to attach my iPod Touch to the VM. When I attach it to the VMWare server host, I can't tell if it's connected or not (I assume that if it's working ok, iTunes would pop up). I tried firing up the USB Prober app, but I'm not savvy enough to determine whether the device is attached or not.

Attached is my vmx and a snip of the vmware.log that shows me plugging in the device, removing it and plugging it back in. (zip)

If there's another way to detect that it's attached, please let me know.

Thanks!

RJ

Host: Intel Core2Duo E8200, Vista Business x64, VMWare Server 2.0.1,
Guest: Leopard 10.5.6 (updated to 10.5.7)
luckman212
Hello,
cheers for this, it is just a thing of pure beauty !!
installed 10.5.6 retail dvd and updated to 10.5.7 no problem on vmware 6.5.2 win x64 host.

question #1: I tried to follow the instructions to install the AppleAC97Audio.kext to enable sound but the os complains that the .kext cannot be used:

what to do? unsure.gif


question #2: how can i increase screen res >greater than 1024 x 768?
display prefs only shows this single res.

cheers
Donk
QUOTE (luckman212 @ Jul 2 2009, 05:46 AM) *
Hello,
cheers for this, it is just a thing of pure beauty !!
installed 10.5.6 retail dvd and updated to 10.5.7 no problem on vmware 6.5.2 win x64 host.

question #1: I tried to follow the instructions to install the AppleAC97Audio.kext to enable sound but the os complains that the .kext cannot be used:

what to do? unsure.gif


question #2: how can i increase screen res >greater than 1024 x 768?
display prefs only shows this single res.

cheers

1. You need to check the permissions on the extension. There are also tools that you can find at ~PCwiz's site to ensure extensions are correctly loaded. (OSx86 Tools Utility)

2. In the manual section 4.2
luckman212
QUOTE (Donk @ Jul 2 2009, 02:11 AM) *
1. You need to check the permissions on the extension. There are also tools that you can find at ~PCwiz's site to ensure extensions are correctly loaded. (OSx86 Tools Utility)

2. In the manual section 4.2


Thanks!!! I got the sound working (sort of, it kind of echos but hey its better than nothing!!) and the resolution I took care of by modifying the com.apple.Boot.plist

wink.gif
Embio
I have followed the instructions for the Hackintosh in my sig, but I am left looking at a spinning beach ball and Leopard client wallpaper sad.gif

If I boot verbose, everything seems fine until that point, same with Snow 10a380. The VMX file is as created by Fusion 2.0.4

any ideas?
Donk
QUOTE (Embio @ Jul 2 2009, 03:09 PM) *
I have followed the instructions for the Hackintosh in my sig, but I am left looking at a spinning beach ball and Leopard client wallpaper sad.gif

If I boot verbose, everything seems fine until that point, same with Snow 10a380. The VMX file is as created by Fusion 2.0.4

any ideas?


Please post the details I requested earlier in the thread. I can't diagnose problems wit this level of information.

QUOTE (RobertJordan @ Jul 2 2009, 02:05 AM) *
Hi, Donk,

Here's another one... I want to attach my iPod Touch to the VM. When I attach it to the VMWare server host, I can't tell if it's connected or not (I assume that if it's working ok, iTunes would pop up). I tried firing up the USB Prober app, but I'm not savvy enough to determine whether the device is attached or not.

Attached is my vmx and a snip of the vmware.log that shows me plugging in the device, removing it and plugging it back in. (zip)

If there's another way to detect that it's attached, please let me know.

Thanks!

RJ

Host: Intel Core2Duo E8200, Vista Business x64, VMWare Server 2.0.1,
Guest: Leopard 10.5.6 (updated to 10.5.7)


USB on VMware isn't something I have a great dal of experience with, basically just plugging in USB keys. I would fire up iTunes and see if it there, as the log file seems to indicate it is connected. It is possible to record a USB trace and analyze it with a tool from VMware, but again no expertise in that.

Sorry can't be more help on this, but let me know what you see.
gcornford
QUOTE (VMErik @ Jun 29 2009, 12:05 PM) *
... but DELL PE2950 gen III with Xeon 5450's work peachy.


VMErik,

I have a very similar hardware configuration as you, Dell PE2950 gen 3 /w Xeon 5420s running ESXi 4, but I'm getting a "Local APIC version 0x11, 0x14 or more expected" error message when booting my Leopard OSX Install DVD.

Could you share your vmx config file?
RobertJordan
Donk,

Here's another wierdness.. Even with Caffeine, I sometimes get a hang. Any ideas?



Jul 02 18:34:11.161: vcpu-1| UHCI: Global Reset
Jul 02 18:34:11.262: vcpu-1| UHCI: HCReset
Jul 02 18:34:24.977: vcpu-0| Guest: Loaded @ 0x26ca261a: Info 0x26ca4560 Name com.vmware.kext.VMwareIOFramebuffer Version 1.0.4 KEXT_BUNDLE_VERSION at Apr 7 2009 19:56:20
Jul 02 18:35:20.167: vcpu-0| Guest: IOFB: start
Jul 02 18:35:20.252: vcpu-1| Guest: SVGADev: Init: SVGA_CAP_TRACES failed
Jul 02 18:36:16.196: vcpu-1| GuestRpc: Channel 0, guest application toolbox-dnd.
Jul 02 18:36:17.866: vcpu-0| GuestRpc: Channel 1, guest application toolbox.
Jul 02 18:36:17.866: vcpu-0| TOOLS sending 'OS_PowerOn' (3) state change request
Jul 02 18:36:17.866: vcpu-0| TOOLS Unable to send OS_*: tools failed to interpret cmd
Jul 02 18:36:17.867: vcpu-0| TOOLS ToolsCapabilityGuestConfDirectory received /etc/vmware-tools
Jul 02 18:36:17.903: vcpu-0| TOOLS setting the tools version to '7461'
Jul 02 18:36:17.956: vcpu-0| Guest: toolbox: Version: build-159196
Jul 02 18:36:17.957: vcpu-0| TOOLS unified loop capability requested by 'toolbox'; now sending options via TCLO
Jul 02 18:36:17.958: vcpu-0| Failed to copy tools version manifest file. hgfsError = 1.
Jul 02 18:36:17.958: vcpu-0| TOOLS installed version 7461, available version 7397
Jul 02 18:36:17.958: vcpu-0| TOOLS will not be autoupgraded.
Jul 02 18:36:17.958: vcpu-0| TOOLS Setting autoupgrade-checked TRUE.
Jul 02 18:36:40.662: mks| MKS switching absolute mouse on
Jul 02 18:41:46.921: mks| MKS switching absolute mouse off
Jul 02 18:41:47.151: mks| MKS switching absolute mouse on
Jul 02 18:41:47.518: mks| MKS switching absolute mouse off
Jul 02 18:41:47.745: mks| MKS switching absolute mouse on
Jul 02 18:41:48.279: mks| MKS switching absolute mouse off
Jul 02 18:41:48.591: mks| MKS switching absolute mouse on
Jul 02 18:41:49.573: mks| MKS switching absolute mouse off
Jul 02 18:41:49.945: mks| MKS switching absolute mouse on
Jul 02 18:41:55.287: mks| MKS switching absolute mouse off
Jul 02 18:41:57.521: mks| MKS switching absolute mouse on
Jul 02 18:41:57.866: mks| MKS switching absolute mouse off
Jul 02 18:42:01.681: mks| MKS switching absolute mouse on
Jul 02 18:42:01.904: vcpu-0| Msg_Hint: msg.monitorevent.halt (sent)
Jul 02 18:42:01.904: vcpu-0| The CPU has been disabled by the guest operating system. You will need to power off or reset the virtual machine at this point.

Jul 02 18:42:01.904: vcpu-0| ---------------------------------------
Jul 02 18:42:20.979: vmx| GuestRpcSendTimedOut: message to toolbox-dnd timed out.
Jul 02 18:42:20.979: vmx| GuestRpcSendTimedOut: message to toolbox timed out.
Jul 02 18:42:35.979: vmx| GuestRpcSendTimedOut: message to toolbox-dnd timed out.
Jul 02 18:42:35.979: vmx| GuestRpc: app toolbox-dnd's second ping timeout; assuming app is down
Jul 02 18:42:35.979: vmx| GuestRpcSendTimedOut: message to toolbox timed out.
Jul 02 18:42:35.979: vmx| GuestRpc: app toolbox's second ping timeout; assuming app is down
Jul 02 18:51:44.043: mks| MKS switching absolute mouse off


edit:

trying this in the .vmx

paevm = "TRUE"
Donk
QUOTE (RobertJordan @ Jul 3 2009, 02:12 AM) *
Donk,

Here's another wierdness.. Even with Caffeine, I sometimes get a hang. Any ideas?



Jul 02 18:34:11.161: vcpu-1| UHCI: Global Reset
Jul 02 18:34:11.262: vcpu-1| UHCI: HCReset
Jul 02 18:34:24.977: vcpu-0| Guest: Loaded @ 0x26ca261a: Info 0x26ca4560 Name com.vmware.kext.VMwareIOFramebuffer Version 1.0.4 KEXT_BUNDLE_VERSION at Apr 7 2009 19:56:20
Jul 02 18:35:20.167: vcpu-0| Guest: IOFB: start
Jul 02 18:35:20.252: vcpu-1| Guest: SVGADev: Init: SVGA_CAP_TRACES failed
Jul 02 18:36:16.196: vcpu-1| GuestRpc: Channel 0, guest application toolbox-dnd.
Jul 02 18:36:17.866: vcpu-0| GuestRpc: Channel 1, guest application toolbox.
Jul 02 18:36:17.866: vcpu-0| TOOLS sending 'OS_PowerOn' (3) state change request
Jul 02 18:36:17.866: vcpu-0| TOOLS Unable to send OS_*: tools failed to interpret cmd
Jul 02 18:36:17.867: vcpu-0| TOOLS ToolsCapabilityGuestConfDirectory received /etc/vmware-tools
Jul 02 18:36:17.903: vcpu-0| TOOLS setting the tools version to '7461'
Jul 02 18:36:17.956: vcpu-0| Guest: toolbox: Version: build-159196
Jul 02 18:36:17.957: vcpu-0| TOOLS unified loop capability requested by 'toolbox'; now sending options via TCLO
Jul 02 18:36:17.958: vcpu-0| Failed to copy tools version manifest file. hgfsError = 1.
Jul 02 18:36:17.958: vcpu-0| TOOLS installed version 7461, available version 7397
Jul 02 18:36:17.958: vcpu-0| TOOLS will not be autoupgraded.
Jul 02 18:36:17.958: vcpu-0| TOOLS Setting autoupgrade-checked TRUE.
Jul 02 18:36:40.662: mks| MKS switching absolute mouse on
Jul 02 18:41:46.921: mks| MKS switching absolute mouse off
Jul 02 18:41:47.151: mks| MKS switching absolute mouse on
Jul 02 18:41:47.518: mks| MKS switching absolute mouse off
Jul 02 18:41:47.745: mks| MKS switching absolute mouse on
Jul 02 18:41:48.279: mks| MKS switching absolute mouse off
Jul 02 18:41:48.591: mks| MKS switching absolute mouse on
Jul 02 18:41:49.573: mks| MKS switching absolute mouse off
Jul 02 18:41:49.945: mks| MKS switching absolute mouse on
Jul 02 18:41:55.287: mks| MKS switching absolute mouse off
Jul 02 18:41:57.521: mks| MKS switching absolute mouse on
Jul 02 18:41:57.866: mks| MKS switching absolute mouse off
Jul 02 18:42:01.681: mks| MKS switching absolute mouse on
Jul 02 18:42:01.904: vcpu-0| Msg_Hint: msg.monitorevent.halt (sent)
Jul 02 18:42:01.904: vcpu-0| The CPU has been disabled by the guest operating system. You will need to power off or reset the virtual machine at this point.

Jul 02 18:42:01.904: vcpu-0| ---------------------------------------
Jul 02 18:42:20.979: vmx| GuestRpcSendTimedOut: message to toolbox-dnd timed out.
Jul 02 18:42:20.979: vmx| GuestRpcSendTimedOut: message to toolbox timed out.
Jul 02 18:42:35.979: vmx| GuestRpcSendTimedOut: message to toolbox-dnd timed out.
Jul 02 18:42:35.979: vmx| GuestRpc: app toolbox-dnd's second ping timeout; assuming app is down
Jul 02 18:42:35.979: vmx| GuestRpcSendTimedOut: message to toolbox timed out.
Jul 02 18:42:35.979: vmx| GuestRpc: app toolbox's second ping timeout; assuming app is down
Jul 02 18:51:44.043: mks| MKS switching absolute mouse off


edit:

trying this in the .vmx

paevm = "TRUE"


Did you also switch the energy saving settings off as well? Don't think the paevm setting will do anything in this scenario and it is implicit in the darwin-64 setting.
Donk
Intel Q6600 Processor

I have had multiple reports that there are issues with this processor, and maybe some other quad cores, both in this thread and the previous work I did on using VMware for Mac OS X. At the moment I am not sure what the issue is. If anyone want to help me out with this then please let me know. Would probably require debug logs from VMware, and possibly have to try Voodoo Kernel 2 alpha 3, in a test darwin.iso. I don't have access to a system with the CPU, so would have tor ely on accurate feedback from those who want to get involved.
Embio
Donk, I seem to remember facing this trouble last year. When I used a Server ISO with no kexts in extensions it booted just fine, but was very unstable. Perhaps it is one of the Intel Management kexts we should be looking at?

my vmware.log:

Jul 03 13:26:12.631: vcpu-2| SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8
Jul 03 13:26:17.327: vcpu-2| UHCI: Global Reset
Jul 03 13:26:17.427: vcpu-2| UHCI: HCReset
Jul 03 13:29:49.584: vcpu-0| HostSMCRead: Unable to find the service.
Jul 03 13:29:49.586: vcpu-0| HostSMCRead: Unable to find the service.
Jul 03 13:34:31.390: vmx| TOOLS setting the tools version to '0'
Jul 03 13:36:31.643: vcpu-1| SCSI-DEV scsi0:0: Unsupported command START STOP UNIT issued. --ok
Jul 03 13:36:32.666: vmx| ide1:0: Command LOAD/UNLOAD MEDIUM took 1.023 seconds (ok)
Jul 03 13:36:52.668: vcpu-0| SCSI-DEV scsi0:0: Unsupported command START STOP UNIT issued. --ok
Jul 03 13:49:35.144: mks| MKS switching absolute mouse on
Donk
QUOTE (Embio @ Jul 3 2009, 11:59 AM) *
Donk, I seem to remember facing this trouble last year. When I used a Server ISO with no kexts in extensions it booted just fine, but was very unstable. Perhaps it is one of the Intel Management kexts we should be looking at?

my vmware.log:

Jul 03 13:26:12.631: vcpu-2| SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8
Jul 03 13:26:17.327: vcpu-2| UHCI: Global Reset
Jul 03 13:26:17.427: vcpu-2| UHCI: HCReset
Jul 03 13:29:49.584: vcpu-0| HostSMCRead: Unable to find the service.
Jul 03 13:29:49.586: vcpu-0| HostSMCRead: Unable to find the service.
Jul 03 13:34:31.390: vmx| TOOLS setting the tools version to '0'
Jul 03 13:36:31.643: vcpu-1| SCSI-DEV scsi0:0: Unsupported command START STOP UNIT issued. --ok
Jul 03 13:36:32.666: vmx| ide1:0: Command LOAD/UNLOAD MEDIUM took 1.023 seconds (ok)
Jul 03 13:36:52.668: vcpu-0| SCSI-DEV scsi0:0: Unsupported command START STOP UNIT issued. --ok
Jul 03 13:49:35.144: mks| MKS switching absolute mouse on


Unfortunately there is nothing in the log extract here. I did a post http://www.insanelymac.com/forum/index.php...t=#entry1189918 on the details that would be useful for me to track down these issues. Can you get the data requested there please? Before you do though, can you set the following line in your vmx file:

monitor = "debug"

Run until you get the error, shutdown guest and post the details.
JFGOOFY
Hi Donk:

First thank you for all of your efforts and work.

I am running vSphere 4.0 Enterprise and cannot seem to get past one thing. I followed the instructions and modified the vmx file as stated in the instructions. I ran the setup.sh script (only once). When starting the OSX machine I get an error stating that "The guest operating system 'darwin64Guest' is not supported".

Can you tell me what I did wrong.

Thank you.
toto1234
This is awesome. Even legendary smile.gif Thanks so much.
rkbrown04
Donk, just read through the entire thread and of course have a Sony Vaio laptop that I am trying to load the Mac OS in a VMWare Workstation. There is a setting for the CPU under the advanced button that enables the bios VT-x setting for the Execution Mode and allows you to set the Perferred Mode. I have a choice that reads "Intel VT-x or AMD-V". I would give you a screen copy but I can not get the editor here to accept a paste. Do you think this would work. I have tried with varying success. but during the load of the os I see multiple fails during the mkdir and such and sometimes I get to the Utility menu but cannot do anything when I get there. It seems to think that the disk is write protected.

Thanks for any help.
Rick
I have attached a word doc with a screen capture of the settings page from VMWare.
R
Donk
QUOTE (rkbrown04 @ Jul 6 2009, 12:57 PM) *
Donk, just read through the entire thread and of course have a Sony Vaio laptop that I am trying to load the Mac OS in a VMWare Workstation. There is a setting for the CPU under the advanced button that enables the bios VT-x setting for the Execution Mode and allows you to set the Perferred Mode. I have a choice that reads "Intel VT-x or AMD-V". I would give you a screen copy but I can not get the editor here to accept a paste. Do you think this would work. I have tried with varying success. but during the load of the os I see multiple fails during the mkdir and such and sometimes I get to the Utility menu but cannot do anything when I get there. It seems to think that the disk is write protected.

Thanks for any help.
Rick
I have attached a word doc with a screen capture of the settings page from VMWare.
R


Can you post the information I requested here please? http://www.insanelymac.com/forum/index.php...p;#entry1189918

Note that Sony Vaio's usually do not enable VT-x in the BIOS and so aren't usable for anything that requires it.
VMErik
QUOTE (VMErik @ Jul 1 2009, 10:42 AM) *
A couple of secondary points to look into. I had originally installed my VM on the internal storage of the ESX Server and since this machine will be getting reinstalled, I copied the VM using the regular VMware tools over to an iSCSI volume. I tried to boot and ended up with the regular PXE boot so I checked the vmx file and found that it had been modified by ESX and replaced darwin-64 with other.

I replaced the original darwin-64 value and tried to start the machine and am now getting:
CODE
Power On virtual machine
OSXS
The guest operating system 'darwin64Guest' is not supported.
Administrateur
VC-VSPHERE
01/07/2009 10:25:28
01/07/2009 10:25:28
01/07/2009 10:25:28


I'm going to try and rebuild a new VM on the iSCSI datastore and re-use the existing disk to see if that works, but this is an annoying problem since it means that you have to be extra careful and using the standard VMware tools to manage an OSX VM.


Update to add to the documentation here. It would appear that VMware is considerably more stringent about applying compatibility rules when you're using vCenter to manage multiple ESX Servers. If I register the virtual machine to a server via the vCenter server and try to boot it, I get the error message noted above. However, if I use the VI Client to connect directly to the server, I can start the VM. Same server, same VM.

Bottom line, running OS X VMs on ESX requires that you are connected directly to the ESX Server and not via vCenter. This (unfortunately) means that you can't take advantage of the vCenter features like High Availability and Load Balancing (DRS).

The datastore issue I was chasing was a red herring.
Donk
QUOTE (VMErik @ Jul 8 2009, 02:04 PM) *
Update to add to the documentation here. It would appear that VMware is considerably more stringent about applying compatibility rules when you're using vCenter to manage multiple ESX Servers. If I register the virtual machine to a server via the vCenter server and try to boot it, I get the error message noted above. However, if I use the VI Client to connect directly to the server, I can start the VM. Same server, same VM.

Bottom line, running OS X VMs on ESX requires that you are connected directly to the ESX Server and not via vCenter. This (unfortunately) means that you can't take advantage of the vCenter features like High Availability and Load Balancing (DRS).

The datastore issue I was chasing was a red herring.


Thanks for this. It could be unfixable, in which case I will alter the documentation. At least users of free ESXi should be OK, and anyone else not running within a vCenter system.
geiman
Quick question, ESX server 3 is not in the list of supported vmware products, but I was wondering if it has just never been tried or if it does not support something necessary for this? We're running an OS X server install on a dual G5 that we would love to move to our ESX 3 server.
danno
Will this procedure work for installing Leopard Server as well ??
Donk
QUOTE (geiman @ Jul 8 2009, 08:02 PM) *
Quick question, ESX server 3 is not in the list of supported vmware products, but I was wondering if it has just never been tried or if it does not support something necessary for this? We're running an OS X server install on a dual G5 that we would love to move to our ESX 3 server.


Sorry this method won't work for ESX3, it does not have the virtual hardware 7 support. I have tried!

QUOTE (danno @ Jul 8 2009, 09:16 PM) *
Will this procedure work for installing Leopard Server as well ??


Yes
mharris45
Great write up and thanks for the work that went into this.

Does anyone know if VMWare has any plans to allow this to properly install on vSphere 4, or is this always going to be an "unsupported" implementation?
Donk
QUOTE (mharris45 @ Jul 9 2009, 09:30 PM) *
Great write up and thanks for the work that went into this.

Does anyone know if VMWare has any plans to allow this to properly install on vSphere 4, or is this always going to be an "unsupported" implementation?


Unless they get Apple to agree to use ESX on Apple servers then it will remain unsupported due to the EULA for Mac OS X.
buhrmi
Hello Donk. Thank you very much for this. I sooooo love it!

It worked like a charm, but I cannot access internet from within MacOS.

I'm running windows 7 x64 rc. VM seems to be able to resolve hostnames though.
QUOTE
traceroute to osx86project.com (216.8.179.24), 64 hops max, 40 byte packets
1 192.168.117.2 (192.168.117.2) 2.507 ms 0.397 ms 0.374 ms
2 * * *
3 * * *
[...]


Any ideas?

Some random infos that might be helpfull:
Firewalls are deactivated. I'm behind a DSL router using Intel WLAN 5300. VMWare is using NAT and configured as E1000.

Cheers smile.gif
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.