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

[Donk]

I tried darwin301b4 but after software update to 10.6.4 it contines to reboot!

 

None of what I have done so far will work (including a private beta 5 build with kernel patching). Am talking to Zenith432 and will have to move to a different kernel.

[yanis]

I don´t understand how you disabled HT? My config is the same but HT is already active. In BIOS of the VM I also do´t find a way to disable HT and in the BIOS of the host I can disable but I won´t do this because there are other machines running on the ESXi.

 

Within the VM configuration are a set of options to control the CPU (you should be able to see where the option is based on the screen shot). That config is within the individual VM settings, not in the main configuration of the ESXi server.

 

In my case, I don't have HT at all, however VMware ESXi 4 has per-VM control of hyper-threading. It can be disabled or enabled accordingly. I simply suggested it as a potential way to test if HT is part of the issue.

[DFox]

Within the VM configuration are a set of options to control the CPU (you should be able to see where the option is based on the screen shot). That config is within the individual VM settings, not in the main configuration of the ESXi server.

 

In my case, I don't have HT at all, however VMware ESXi 4 has per-VM control of hyper-threading. It can be disabled or enabled accordingly. I simply suggested it as a potential way to test if HT is part of the issue.

 

I tried to disable HT but the problem persists!

[Donk]

I tried to disable HT but the problem persists!

 

Your problem has nothing to do with HT. I have now built a new darwin,iso with a legacy kernel to try and fix the problem. I am finishing the testing and will make it available when I am happy with it. Note it is not a simple to setup and use as previous versions.

[hippoth]

Within the VM configuration are a set of options to control the CPU (you should be able to see where the option is based on the screen shot). That config is within the individual VM settings, not in the main configuration of the ESXi server.

 

In my case, I don't have HT at all, however VMware ESXi 4 has per-VM control of hyper-threading. It can be disabled or enabled accordingly. I simply suggested it as a potential way to test if HT is part of the issue.

Maybe I´am blind or something else but do you mean this configuration dialog?

If yes, I can set what ever I want - it does not disable HT.

 

Your problem has nothing to do with HT. I have now built a new darwin,iso with a legacy kernel to try and fix the problem. I am finishing the testing and will make it available when I am happy with it. Note it is not a simple to setup and use as previous versions.

I think DFox and me will try everything

[Donk]

Maybe I´am blind or something else but do you mean this configuration dialog?

If yes, I can set what ever I want - it does not disable HT.

 

 

I think DFox and me will try everything

 

OK here goes last attempt after that I have to stop as have other work and personal projects that need some attention. Firstly the image is here http://www.filedropper.com/darwin310b6. Secondly, thanks to Meklort (Chameleon team), Zenith432 plus Nawcom for the bits and pieces I have used to try this last attempt. I assume you are happy with the previous instructions e.g. no SCSI etc.

 

To install SL you will need to do the following from the boot prompt:

 

Step 1: With the DVD attached to the session, press F8 for boot prompt, then F5 to re-scan optical media. You should now see the DVD listed. At the prompt type the following and then press enter:

 

rd(0,1)/legacy_kernel -v -f -x rd=disk1s3

The install Mac OS X.

 

Step 2: at the first reboot F8 and then this command again at the prompt.

 

rd(0,1)/legacy_kernel -v -f -x rd=disk0s2

Go through the initial setup program until you are at the desktop.

 

Step 3: Immediately get 10.6.4 installed either via download or mounting another ISO, then reboot.

 

Step 4: Carry out step 2 at the boot prompt once again.

 

Step 5: Reboot and one final test, at the boot prompt just use:

 

rd(0,1)/legacy_kernel rd=disk0s2

Check everything works especially mouse and keyboard

 

Step 6: To make this permanent (if all the other stuff works) you will need to:

a. Make a directory under the root of the hard drive called /Extra

b. Copy /Library/Preferences/SystemConfiguration/com.apple.Boot.plist to /Extra

c. Edit /Extra/com.apple.Boot.plist and replace the mach_kernel string with rd(0,1)/legacy_kernel, and the kernel flags should read rd=disk0s2.

 

I will properly write this up if it works!

[DFox]

OK here goes last attempt after that I have to stop as have other work and personal projects that need some attention. Firstly the image is here http://www.filedropper.com/darwin310b6. Secondly, thanks to Meklort (Chameleon team), Zenith432 plus Nawcom for the bits and pieces I have used to try this last attempt. I assume you are happy with the previous instructions e.g. no SCSI etc.

 

To install SL you will need to do the following from the boot prompt:

 

Step 1: With the DVD attached to the session, press F8 for boot prompt, then F5 to re-scan optical media. You should now see the DVD listed. At the prompt type the following and then press enter:

 

rd(0,1)/legacy_kernel -v -f -x rd=disk1s3

The install Mac OS X.

 

Step 2: at the first reboot F8 and then this command again at the prompt.

 

rd(0,1)/legacy_kernel -v -f -x rd=disk0s2

Go through the initial setup program until you are at the desktop.

 

Step 3: Immediately get 10.6.4 installed either via download or mounting another ISO, then reboot.

 

Step 4: Carry out step 2 at the boot prompt once again.

 

Step 5: Reboot and one final test, at the boot prompt just use:

 

rd(0,1)/legacy_kernel rd=disk0s2

Check everything works especially mouse and keyboard

 

Step 6: To make this permanent (if all the other stuff works) you will need to:

a. Make a directory under the root of the hard drive called /Extra

b. Copy /Library/Preferences/SystemConfiguration/com.apple.Boot.plist to /Extra

c. Edit /Extra/com.apple.Boot.plist and replace the mach_kernel string with rd(0,1)/legacy_kernel, and the kernel flags should read rd=disk0s2.

 

I will properly write this up if it works!

 

Tomorrow I'll try if this works on my ESXi.

Today a make a different test: I assembled a new machine using an ASUS P5K motherboard and an Intel Q6600 processor, 4GB ram, 500GB SATA disk, etc.

Then I installed Ubuntu Server 8.10 and Vmware Server 2.0.2 64bit (latest build), patched with darwin310b2 package. Finally I created a Virtual Machine using settings for Snow Leo but with darwin-64 as guest, ide0:0 for disk and ide1:0 for cd-rom and I have been able to install a working Snow Leo Server 10.6.0. Final step, Combo Update 10.6.4 and... IT WORKS!!!

 

So, I can confirm that problem causing on my ESXi are the same of hippoth, and they are concerning with processor type, like previously mentioned by Donk!

 

Soon I'll post all procedure for VMware Server 2.0.2 with vmx, etc.

 

Tomorrow I'll try if this works on my ESXi.

Today a make a different test: I assembled a new machine using an ASUS P5K motherboard and an Intel Q6600 processor, 4GB ram, 500GB SATA disk, etc.

Then I installed Ubuntu Server 8.10 and Vmware Server 2.0.2 64bit (latest build), patched with darwin310b2 package. Finally I created a Virtual Machine using settings for Snow Leo but with darwin-64 as guest, ide0:0 for disk and ide1:0 for cd-rom and I have been able to install a working Snow Leo Server 10.6.0. Final step, Combo Update 10.6.4 and... IT WORKS!!!

 

So, I can confirm that problem causing on my ESXi are the same of hippoth, and they are concerning with processor type, like previously mentioned by Donk!

 

Soon I'll post all procedure for VMware Server 2.0.2 with vmx, etc.

 

I want to share this post that I've just find on vmware forum: osx universal builds

In this post ther's an explanation about 10.6.2, 10.6.3 and so on incompatibility with some processors like Intel i7.

[Donk]

Tomorrow I'll try if this works on my ESXi.

Today a make a different test: I assembled a new machine using an ASUS P5K motherboard and an Intel Q6600 processor, 4GB ram, 500GB SATA disk, etc.

Then I installed Ubuntu Server 8.10 and Vmware Server 2.0.2 64bit (latest build), patched with darwin310b2 package. Finally I created a Virtual Machine using settings for Snow Leo but with darwin-64 as guest, ide0:0 for disk and ide1:0 for cd-rom and I have been able to install a working Snow Leo Server 10.6.0. Final step, Combo Update 10.6.4 and... IT WORKS!!!

 

So, I can confirm that problem causing on my ESXi are the same of hippoth, and they are concerning with processor type, like previously mentioned by Donk!

 

Soon I'll post all procedure for VMware Server 2.0.2 with vmx, etc.

 

 

 

I want to share this post that I've just find on vmware forum: osx universal builds

In this post ther's an explanation about 10.6.2, 10.6.3 and so on incompatibility with some processors like Intel i7.

 

Thanks for pointing out the post by HPReg, which I had missed. If you don't know he is one of the engineers at VMware and has been working on the products for some time, and was responsible for Fusion being developed. It does maybe mean there is another possibility to try and use a CPUID mask for ESX if the new kernel fails.

 

Do you need a server based VMware product as Server 2.0.2 is pretty old now and rumour has it won't be updated? Player 3.1 has everything needed built-in for Snow Leopard.

[hippoth]

OK here goes last attempt after that I have to stop as have other work and personal projects that need some attention. Firstly the image is here http://www.filedropper.com/darwin310b6. Secondly, thanks to Meklort (Chameleon team), Zenith432 plus Nawcom for the bits and pieces I have used to try this last attempt. I assume you are happy with the previous instructions e.g. no SCSI etc.

 

To install SL you will need to do the following from the boot prompt:

 

Step 1: With the DVD attached to the session, press F8 for boot prompt, then F5 to re-scan optical media. You should now see the DVD listed. At the prompt type the following and then press enter:

 

rd(0,1)/legacy_kernel -v -f -x rd=disk1s3

The install Mac OS X.

 

Step 2: at the first reboot F8 and then this command again at the prompt.

 

rd(0,1)/legacy_kernel -v -f -x rd=disk0s2

Go through the initial setup program until you are at the desktop.

 

Step 3: Immediately get 10.6.4 installed either via download or mounting another ISO, then reboot.

 

Step 4: Carry out step 2 at the boot prompt once again.

 

Step 5: Reboot and one final test, at the boot prompt just use:

 

rd(0,1)/legacy_kernel rd=disk0s2

Check everything works especially mouse and keyboard

 

Step 6: To make this permanent (if all the other stuff works) you will need to:

a. Make a directory under the root of the hard drive called /Extra

b. Copy /Library/Preferences/SystemConfiguration/com.apple.Boot.plist to /Extra

c. Edit /Extra/com.apple.Boot.plist and replace the mach_kernel string with rd(0,1)/legacy_kernel, and the kernel flags should read rd=disk0s2.

 

I will properly write this up if it works!

Thank you Donk, the new ISO is a big step forward. I can start the installation, can choose a disk where to install, set install options and start the install. But after 10 Minutes, where the installation processed the install finished with an error. After this I try to set an startvolume (boot-partition) but Mac OS X tells me that the "bless-Tool" could not set the startvolume.

I will try to google for this error, maybe I will find a way to pass this error

 

EDIT: I also tried to set the DVD as startvolume and rebootet with this paramters

<span class="postcolor">rd(0,1)/legacy_kernel -v -f -x rd=disk0s2

... but I get an kernel panic.

[Donk]

Thank you Donk, the new ISO is a big step forward. I can start the installation, can choose a disk where to install, set install options and start the install. But after 10 Minutes, where the installation processed the install finished with an error. After this I try to set an startvolume (boot-partition) but Mac OS X tells me that the "bless-Tool" could not set the startvolume.

I will try to google for this error, maybe I will find a way to pass this error.

 

I had that error and just rebooted using the rd=disk0s2 version of the command and it worked. You can't use start-disk on VMware unles using newer version as there is no EFI NVRAM storage.

[hippoth]

I had that error and just rebooted using the rd=disk0s2 version of the command and it worked. You can't use start-disk on VMware unles using newer version as there is no EFI NVRAM storage.

How you can read in my edited post. I tried this too with the DVD as startvolume (other does not work) but I get an kernel panic.

 

EDIT: I will try this --> http://www.insanelymac.com/forum/index.php?showtopic=184060#

[Donk]

How you can read in my edited post. I tried this too with the DVD as startvolume (other does not work) but I get an kernel panic.

 

EDIT: I will try this --> http://www.insanelymac.com/forum/index.php?showtopic=184060#

 

Hmm. Strange, but hopefully you can move forward on this by trying the suggestions in the other post.

[hippoth]

Hmm. Strange, but hopefully you can move forward on this by trying the suggestions in the other post.

Ok, I passed this step. Mac OS tries to identify my keyboard but does not going on. Any idea?

[hippoth]

I have to stop my test for this week. I´am back on monday. Maybe someone has an idea how to bypass the keyboard config.

 

What I tried ... keyboard.vusb.enable = "true"/"false" - but no luck.

 

On monday I will try this --> http://www.macosxhints.com/article.php?sto...050430055638150

 

Donk thanks for your great investigations for the ESXi-problems. Today we have made a really big step forward. Maybe we can bring it to a good end.

 

Today I got a vmware-newsletter regarding vSphere 4.1 ... maybe we can hope for a bigger ESXi update with the improvements of VM Workstation 7.1 or Player 3.1.

 

I say goodby for this week - I´am back on monday!

[Donk]

Ok, I passed this step. Mac OS tries to identify my keyboard but does not going on. Any idea?

 

That's a standard problem with PC keyboards and not VMware itself. I am guessing you have a German keyboard if so press the key 2 from the the left shift key. On a UK keyboard (mine) it is Z but Y on German keyboards.

 

I have also another trick which may work using a CPUID mask which may remove the need for the legacy_kernel. I am testing it out now, and would be great of you could test it for me, as my machines don't show the problem.

 

See you on Monday.

[Donk]

For DFox and Hippoth:

 

One other test to try for me as well.

 

1. Use beta 2 or 6

2. In the VMX file add this line which masks the CPU details to mine (Core2 Duo)

 

cpuid.1.eax = "--------------------011111111011"

 

Try booting without any other switches apart from -v for verbose mode.

[Robert3000]

Hello Donk! Really appreciate the work you've done, was able to quickly get 10.6.3 Server (10D572) running in Workstation 7.0.1 on a Core 2 Duo box without a hitch.

 

Now, I've imported this running VM into an ESXi 4.0U2 box running a Core i3 processor and the VM constantly reboots. Booting in verbose mode shows no kernel panics or errors, it just goes straight from completion of loading kexts to rebooting. Booting the DVD does the exact same thing. I used the same darwin.iso that worked under Workstation 7.0.1 on the ESXi box.

 

Does anyone know if this symptom is indicative of an unsupported CPU family/model?

[Donk]

Hello Donk! Really appreciate the work you've done, was able to quickly get 10.6.3 Server (10D572) running in Workstation 7.0.1 on a Core 2 Duo box without a hitch.

 

Now, I've imported this running VM into an ESXi 4.0U2 box running a Core i3 processor and the VM constantly reboots. Booting in verbose mode shows no kernel panics or errors, it just goes straight from completion of loading kexts to rebooting. Booting the DVD does the exact same thing. I used the same darwin.iso that worked under Workstation 7.0.1 on the ESXi box.

 

Does anyone know if this symptom is indicative of an unsupported CPU family/model?

 

You can't do that you need to use specific darwin.iso for ESXi, and we are currently still debugging it it on ESXi.

[Robert3000]

You can't do that you need to use specific darwin.iso for ESXi, and we are currently still debugging it it on ESXi.

 

Ah, sorry. That darwin.iso (3.1.0B6) actually worked for me. Booting with...

rd(0,1)/legacy_kernel rd=disk0s2

...as suggested ended up with an RTC/TSC related kernel panic, however booting with...

rd(0,1)/legacy_kernel rd=disk0s2 busratio=20 -notscverify

...worked perfectly.

 

 

I can now boot the imported VM in ESXi. It prompted to reconfigure the keyboard, but had no issues there either. I assume because I'm using a US keyboard.

[Donk]

Ah, sorry. That darwin.iso (3.1.0B6) actually worked for me. Booting with...

rd(0,1)/legacy_kernel rd=disk0s2

...as suggested ended up with an RTC/TSC related kernel panic, however booting with...

rd(0,1)/legacy_kernel rd=disk0s2 busratio=20 -notscverify

...worked perfectly.

 

 

I can now boot the imported VM in ESXi. It prompted to reconfigure the keyboard, but had no issues there either. I assume because I'm using a US keyboard.

 

Great thanks for the update!

[Robert3000]

Another quick update, it seems as if you can set busratio=x closer to the actual host ratio. In my case though, setting it to 32 to match the host's 2.93GHz CPU resulted in the VM going into "turbo mode" with each keypress translating into 10+ in the VM. Not sure if that's truly RTC related or a VMware tools issue. Setting it lower to 30 for 2.84GHz seems to have resolved the issue.

 

Booting without the busratio=x, you can see the bus speed reported in the KP as 0MHz.

 

Booting without the -notscverify gives you an RTC error.

[DFox]

For DFox and Hippoth:

 

One other test to try for me as well.

 

1. Use beta 2 or 6

2. In the VMX file add this line which masks the CPU details to mine (Core2 Duo)

 

cpuid.1.eax = "--------------------011111111011"

 

Try booting without any other switches apart from -v for verbose mode.

 

I've just tried your suggestion in conjuction with beta2 but nothing... now I give a chance to beta6, too

 

I want to share a link to a document of vmware about masking CPUID, but at the moment I am not able to understand the procedure for a perfect masking! vmotion and cpuid masking

 

I've just tried your suggestion in conjuction with beta2 but nothing... now I give a chance to beta6, too

 

I want to share a link to a document of vmware about masking CPUID, but at the moment I am not able to understand the procedure for a perfect masking! vmotion and cpuid masking

 

I also found this document provided by Intel about CPUID and other information for building EAX, EDX, etc... This values can be inputed in the advande CPUID mask of ESXi VM Configuration; I think that with the correct strings it could be work!

[Donk]

I've just tried your suggestion in conjuction with beta2 but nothing... now I give a chance to beta6, too

 

I want to share a link to a document of vmware about masking CPUID, but at the moment I am not able to understand the procedure for a perfect masking! vmotion and cpuid masking

 

 

 

I also found this document provided by Intel about CPUID and other information for building EAX, EDX, etc... This values can be inputed in the advande CPUID mask of ESXi VM Configuration; I think that with the correct strings it could be work!

I have had experience of using the masks before. I do know what is usable here. I am also looking at the source code for xnu kernel, and can see what values are OK for booting. I need to re-check one your log files to work out a new mask.

[Robert3000]

Another update regarding the running 10.6.3 VM on an ESXi 4.0U2 box running a Core i3. This would also probably work on the i5 & i7 mobile, and possibly the Xeon 3400 series.

 

Upgraded to 10.6.4 (10F569) successfully.

 

On first boot, use...

rd(0,1)/legacy_kernel rd=disk0s2 -f -x -v

 

On subsequent boots, no longer need to specify busratio=x or use -notscverify. It seems 10F569 recognizes this processor properly. Recognized host CPU clock speed correctly. Boots in about half the time as 10D572, and much more responsive in general. Just using the same boot options recommended by Donk now...

rd(0,1)/legacy_kernel rd=disk0s2

 

Those of us with newer CPU's may do well to use a later build, builds compatible with Nehalem/Clarkdale/Arrandale seem to only be available via update or bundled with newer systems right now. My retail DVD from March was too old.

[hippoth]

YYYYYYEEEEEESSSSSS!!!

 

Donk, I found some more minutes to compete the installation. IT WORKS!

 

The machine is up to date on 10.6.4. It reebots without parameters (with the /Extra folder). GREAT!

I can´t tell you something about the performance, because I have completed the installation via an SSL VPN Connection (this is not as fast as being in the local office ).

 

I´am really glad about this.

 

On monday I will try your last idea with masquarading the CPU in a second Mac OS X virtual machine.

 

Thanks for all!