Jump to content

Mac OS X on ESXI Server


27 posts in this topic

Recommended Posts

I am new to virtualization so my questions may seem basic but I still need to ask.

 

I want to to run a Mac Os on my EsSXI 5.5 server. It does have support for Mac OS but it is not a Mac Server.

 

So my questions are:

Do i still need to use the unlocker?

Can I use my OSX 10.6 Install DVD with the internal DVD or do I need to create an install DVD?

If I need to create an install DVD how do I do that and should it be an ISO?

Do I need to make any changes in the bios

 

What would the steps be that I would need to follow to set up the Mac OSX on my non Mac environment?

 

This will be used as a test environment only.

 

Thank you very much for you help as I enter the world of virtualization.

Link to comment
Share on other sites

I am new to virtualization so my questions may seem basic but I still need to ask.

 

I want to to run a Mac Os on my EsSXI 5.5 server. It does have support for Mac OS but it is not a Mac Server.

 

So my questions are:

Do i still need to use the unlocker?

Can I use my OSX 10.6 Install DVD with the internal DVD or do I need to create an install DVD?

If I need to create an install DVD how do I do that and should it be an ISO?

Do I need to make any changes in the bios

 

What would the steps be that I would need to follow to set up the Mac OSX on my non Mac environment?

 

This will be used as a test environment only.

 

Thank you very much for you help as I enter the world of virtualization.

Zimboy,

 

Welcome to InsanelyMac, definately the right place to be for help running OS X under ESXi. OS X 10.6 to 10.9 all run well on ESXi 5.5, so to answer your questions:

 

1. Yes, you still need the unlocker if you are not running ESXi on Apple hardware, ESXi checks for Apple hardware (SMC) and disables OS X if it is not Apple hardware, the unlocker removes this check.

2. Yes, but only if your OS X 10.6 Install DVD is a retail copy, not one supplied with Apple Mac hardware. Alternatively if you have a running Mac download Mavericks (10.9) "free" from the App Store, you can create a DMG file from the download which can be used to install Mavericks under ESXi 5.5, see link at the bottom of this post.

3. ESXi supports installing OS X from Retail DVD, ISO or DMG.

4. In terms of the ESXi host it must have an Intel processor, and have VT-x enabled in BIOS.

 

Below find a couple of links which will help you getting OS X up and running in ESXi:

 

Link to Donk's Unlocker thread:

http://www.insanelymac.com/forum/topic/267296-esxi-5-mac-os-x-unlocker/

 

Link to MSoK's How to thread, not written specifically for ESXi but still plenty of helpful information, including creating a bootable OS X 10.9 DMG image:

http://www.insanelymac.com/forum/topic/290949-how-to-install-os-x-108-mountain-lion-and-os-x-109-mavericks-in-vmware-workstation-910-or-player-56/

 

Link to MSoK's Nested OS X under ESXi thread, if you ignore the bit about installing ESXi under Workstation, the rest should be helpful:

http://www.insanelymac.com/forum/topic/292125-how-to-install-and-run-os-x-in-a-nested-instance-of-vmware-esxi-55-within-workstation-10/

 

Link to Zenith432's Enhanced Graphics thread:

http://www.insanelymac.com/forum/topic/188962-vmware-svga-ii-display-driver-for-os-x-v125/?p=1971067

 

Link to Zenith432's Graphics files:

http://sourceforge.net/projects/vmsvga2/files/Display/

 

Special thanks to Donk and Zenith432 for all the effort in getting OS X running in VMware.

Link to comment
Share on other sites

MSoK

 

This is what I have tried so far and here is where I am at.

 

  • I installed the unlocker by using SSH and going to the directory where the files where located and using ./install.sh
  • The install appears to have completed
  • Now when I try to install the MAC OS I get the gray VMWare screen then I get a gray screen with the apple logo then it flashes back to the VMWare screen again and it just keeps looping.
  • Before attempting to do the install from the ISO I created a new virtual machine with a new  virtual disk
  • I then set the virtual machine to boot from the ISO and set the virtual CD ROM to connect when the VM was powered up
  • When it startes the boot process is when it loops between VMware and the apple logo screens
  • Should I not have created the virtual disk or did I miss something else?

Also my connection to the ESXI server seems to be much slower now as I am getting time out errors now but I am not sure if this has anything to do with the MAC OS or if it is a different issue all together.

 

I will go back and read through the threads that you link to but could sure use some help.

 

Thanks.

Link to comment
Share on other sites

  • 2 months later...

Zimboy,

 

Welcome to InsanelyMac, definately the right place to be for help running OS X under ESXi. OS X 10.6 to 10.9 all run well on ESXi 5.5, so to answer your questions:

 

1. Yes, you still need the unlocker if you are not running ESXi on Apple hardware, ESXi checks for Apple hardware (SMC) and disables OS X if it is not Apple hardware, the unlocker removes this check.

2. Yes, but only if your OS X 10.6 Install DVD is a retail copy, not one supplied with Apple Mac hardware. Alternatively if you have a running Mac download Mavericks (10.9) "free" from the App Store, you can create a DMG file from the download which can be used to install Mavericks under ESXi 5.5, see link at the bottom of this post.

3. ESXi supports installing OS X from Retail DVD, ISO or DMG.

4. In terms of the ESXi host it must have an Intel processor, and have VT-x enabled in BIOS.

 

Below find a couple of links which will help you getting OS X up and running in ESXi:

 

Link to Donk's Unlocker thread:

http://www.insanelymac.com/forum/topic/267296-esxi-5-mac-os-x-unlocker/

 

Link to MSoK's How to thread, not written specifically for ESXi but still plenty of helpful information, including creating a bootable OS X 10.9 DMG image:

http://www.insanelymac.com/forum/topic/290949-how-to-install-os-x-108-mountain-lion-and-os-x-109-mavericks-in-vmware-workstation-910-or-player-56/

 

Link to MSoK's Nested OS X under ESXi thread, if you ignore the bit about installing ESXi under Workstation, the rest should be helpful:

http://www.insanelymac.com/forum/topic/292125-how-to-install-and-run-os-x-in-a-nested-instance-of-vmware-esxi-55-within-workstation-10/

 

Link to Zenith432's Enhanced Graphics thread:

http://www.insanelymac.com/forum/topic/188962-vmware-svga-ii-display-driver-for-os-x-v125/?p=1971067

 

Link to Zenith432's Graphics files:

http://sourceforge.net/projects/vmsvga2/files/Display/

 

Special thanks to Donk and Zenith432 for all the effort in getting OS X running in VMware.

 

Hey MSoK,

 

I have been pulling my hair out trying to install OSX 10.6 on an ESXi 5.5 machine. 

 

I first tested the installation process on my personal desktop with I7 processor using ESXi 5.5 installed in Workstation 10. I had no problems with this. 

 

Now I have been trying on a bare-metal ESXi 5.5 machine and I continue to get a boot loop.

 

I noticed that you said in #4 "ESXi host it must have an Intel processor, and have VT-x enabled in BIOS" 

 

This machine I have been working on has a AMD 8 core processor. Could this be my issue?

 

Thanks for any advice,

SUB

Link to comment
Share on other sites

 

This machine I have been working on has a AMD 8 core processor. Could this be my issue?

 

 

Yes- you will need to find an AMD kernel for OS X. Apple do not support non-Intel CPUs, and so a recomplied mach_kernel is needed to boot on AMD. MSoK and myself do not have any AMD equipment but look in the developers sub-fourm here and you may find some help.

Link to comment
Share on other sites

Yes- you will need to find an AMD kernel for OS X. Apple do not support non-Intel CPUs, and so a recomplied mach_kernel is needed to boot on AMD. MSoK and myself do not have any AMD equipment but look in the developers sub-fourm here and you may find some help.

 

Hey there Donk,

 

Thank you for the quick reply. You pointed me in the right direction.

 

This is a great forum... full of great info.

 

I ended up finding a working solution the installation of OSX 10.6 on a bare-metal ESXi 5.5 AMD machine.

 

This is what I did: (for those pulling their hair out too)

 

For ESXi 5.5:
Create ISO image of OSX 10.6 Installation Disk
- use Linux (windows does not create full ISO image due to inability to read format)
$ sudo dd if=/dev/cdrom of=cd.iso  -- link for info
 
In vSphere 5.5 Client create a new VM 
Do not start VM 
 
Then add VMware Unlocker for OS X 1.2.0 to datastore
- from InsanelyMac... Link
 
SSH into ESXi (with putty or similar) and go to /vmfs/... and find location of datastore where VMware Unlocker was saved.
chmod +x all three files that came with VMware Unlocker download
./install.sh   (to run unlocker script)
Restart ESXi
 
For ESXi 5.5 on AMD Processor
Click "Edit VM settings" and choose "Options" tab, then "General" and then "Configuration Parameters..."
Insert the following "between quotes" on appropriate lines
 
smc.present = "FALSE"
ich7m.present = "TRUE"
firmware = "efi"
usb.present = "TRUE"
hostCPUID.0 = "0000000668747541444d416369746e65"
hostCPUID.1 = "00500f100002080000802209178bfbff"
hostCPUID.80000001 = "00500f1000001242000035ff2fd3fbff"
guestCPUID.0 = "00000006756e65476c65746e49656e69"
guestCPUID.1 = "000006f10000080080802209078bfbff"
guestCPUID.80000001 = "00500f1000001242000003e92bd3fbff"
userCPUID.0 = "0000000668747541444d416369746e65"
userCPUID.1 = "00500f100002080080802209078bfbff"
userCPUID.80000001 = "00500f1000001242000003e92bd3fbff"
 
Then in "CPUID Mask" add the following "between quotes" on appropriate lines to "AMD override" tab. Makes OSX thinks that it is installing on Intel Processor.
 
cpuid.0.ebx="0111:0101:0110:1110:0110:0101:0100:0111"
cpuid.0.edx="0100:1001:0110:0101:0110:1110:0110:1001"
cpuid.0.ecx="0110:1100:0110:0101:0111:0100:0110:1110"
cpuid.1.eax="0000:0000:0000:0000:0000:0110:1111:0001"
 
Now "Power on the VM" and install should work correctly.
 
After installation completed, run updates a few times to get yourself completely up to date
 
Enjoy your new OSX 10.6 operating system!
 
This may work the same for newer OSX variations. Let me know
 
Have a day,
SUB
Link to comment
Share on other sites

Hi SUB

 

That's an interesting approach which I haven't tried. I think you can remove the hostCPUID, guestCPUID and userCPUID values as they are for information only. (Go that from VMware engineer on their forums). To help me look at this would you be prepared to send me the vmx and vmware.log files for you guest please? There should not be any private information in them. If you could attach them to a post or create a GIST it would potentially help the community.

 

Thanks

Link to comment
Share on other sites

  • 2 weeks later...

Subcan, I applied your trick on my machine but it didn't work. the system gives me an error message (something like BSD cannot fine its thread, sorry I did't really memorize it) and rebooted itself.

 

What is the CPU on your system?

 

Thanks,


MSoK,

 

You mentioned "ESXi supports installing OS X from Retail DVD, ISO or DMG", I did not find option for the DMG, could you let me know where that option is? Thanks.

Link to comment
Share on other sites

Subcan, I applied your trick on my machine but it didn't work. the system gives me an error message (something like BSD cannot fine its thread, sorry I did't really memorize it) and rebooted itself.

 

What is the CPU on your system?

 

Thanks,

MSoK,

 

You mentioned "ESXi supports installing OS X from Retail DVD, ISO or DMG", I did not find option for the DMG, could you let me know where that option is? Thanks.

 

What is your AMD CPU? As for DMG, just mount it as an ISO and it should work.

Link to comment
Share on other sites

Mine is FX-8320. Sorry I didn't mention that. My motherboard is the GA-FX990-UD5 Rev1.0.

Can you attach (not post inline) the vmware.log file please? I am gathering information for some tests. It would be great to have had one form an AMD system that worked.

Link to comment
Share on other sites

Can you attach (not post inline) the vmware.log file please? I am gathering information for some tests. It would be great to have had one form an AMD system that worked.

Donk,

I have been away from my computer. I will be home later tonight and will post the log file then.

 

Sorry for the delay.

 

This should work on any AMD system. It did not appear that anything was system specific.

 

I had posted exactly what I did (documented as I did it) in order.

 

SUB

Link to comment
Share on other sites

Donk,

I have been away from my computer. I will be home later tonight and will post the log file then.

 

Sorry for the delay.

 

This should work on any AMD system. It did not appear that anything was system specific.

 

I had posted exactly what I did (documented as I did it) in order.

 

SUB

 

 

That would be great. Also with the same log from wingshigh.g could help us come up with some guidelines for AMD CPUs without needing modified kernels. I personally do not have access to AMD based system, so am reliant on others to help out here.

Link to comment
Share on other sites

That would be great. Also with the same log from wingshigh.g could help us come up with some guidelines for AMD CPUs without needing modified kernels. I personally do not have access to AMD based system, so am reliant on others to help out here.

 

Hey there Donk,

 

The vmware.log file is attached to this post as vmware.log.txt. 

 

I have also edited some of the IP and file paths, just for my own comfort sake. Should not impact what you are looking for though.

 

I had some difficulty installing the vmware tools (which I believe explains all the excess stuff in last half of log) but later figured out how to do it with the darwin_snow.iso file.

 

Hopefully wingshigh.g also posts his log file so that we can compare.

 

I hope that it helps.

 

Please post anything of note. 

 

SUB

vmware.log.txt

Link to comment
Share on other sites

Donk, attached is my vmware.log. I created a new VM, put in all the code suggested by Subcan, took one of my Lion virtual disk attached to the VM which I know it worked on Intel CPU ESXi. Powered on the machine, it could gave kernel panic if I chose Guest system being Mac OS X; it will go into reboot loop if I chose FreeBSD 64bit.

 

Let me know if you need more information.

vmware.log.txt

Link to comment
Share on other sites

Donk, attached is my vmware.log. I created a new VM, put in all the code suggested by Subcan, took one of my Lion virtual disk attached to the VM which I know it worked on Intel CPU ESXi. Powered on the machine, it could gave kernel panic if I chose Guest system being Mac OS X; it will go into reboot loop if I chose FreeBSD 64bit.

 

Let me know if you need more information.

 

Hey there wingshigh.g,

 

I just went through your log file next to mine.

 

There are a few differences.

 

The big one I saw was on line 280 (your log): <2014-03-08T03:09:49.807Z| vmx| I120: DICT               smc.present = TRUE>

 

This is supposed to be set to FALSE.

 

From google search on smc: smc - The System Management Controller (SMC) is an internal subsystem introduced by Apple Inc. with the introduction of their new Intel processor based machines in 2006. It takes over the functions of the SMU. Apple has released updates for this system in order to address power or sleep issues in several recent models.

 

I don't know how I missed that on my directions posting. (must have been tired when I typed it out)

 

Your log shows failure just after line 880. On my log this is line 890. 

 

My log; line 892: <2014-02-17T00:05:29.729Z| vcpu-0| W110: AppleSMC_SetCheckForServer(1) called without an SMC.> shows that the SMC is being ignored.

 

Can you give this a try again but change that the "smc.present" to FALSE?

 

I also assigned 4GB of ram for the install. Some post somewhere suggested that, but I really don't think that that could cause an issue. I just have lots of ram so I didn't care.

 

I hope that this helps.

 

Sorry for the mistake in my direction list.

 

SUB

To All,

 

I edited my original instructions to fix the mistake of smc.present="TRUE" to smc.present="FALSE"

 

Sorry for the typo.

 

SUB

OSX 10.6 Snow Installation Notes - Updated 08MAR14.txt

Link to comment
Share on other sites

Subcan,

 

Please see my log below. I am still getting the kernel panic.


Subcan, when I went back to the configuration, I found that all the code I put in got changed by the system, this is what I have after I powered on and powered off the VM after getting the kernel panic:

 

hostCPUID.0 = "0000000d68747541444d416369746e65"
hostCPUID.1 = "00600f20000808003698320b178bfbff"
hostCPUID.80000001 = "00600f201000000001ebbfff2fd3fbff"
guestCPUID.0 = "0000000d756e65476c65746e49656e69"
guestCPUID.1 = "000006f1000208009698320b178bfbff"
guestCPUID.80000001 = "00600f201000000000010be92bd3fbff"
userCPUID.0 = "0000000d68747541444d416369746e65"
userCPUID.1 = "00600f20000808009698320b178bfbff"
userCPUID.80000001 = "00600f201000000000010be92bd3fbff"
 
I did it twice just to confirm I didn't mis-type. Is there anything I missed?

vmware.log.txt

Link to comment
Share on other sites

This is going to sound stupid but I got this to work installing OS X 10.6 on my AMD host using ESXi 5.5 Build 1474528 by setting smc.present="TRUE".

 

I had tried this last Wednesday (using the original "flawed" instructions) not knowing it shouldn't work on a USB key boot.  Strangely enough it kinda worked - OS X installed fine but for the non-OS X VMs the console in vSphere Client remained blank.

 

I put in a small hard drive today to replace the USB key as the boot device for ESXi so I can run the patch on it.  I also installed another drive to act as the datastore for this VM.  Instead of copying the VM from it's original datastore I figured it was easier to simply create a new VM and possibly avoid any weirdness due to the incomplete nature of the previous patch.  When I tried to install OS X 10.6 it got stuck on the loading screen (grey, coloured wheel spinning).

 

Tried repatching, uninstalling and reinstalling the patch, using an ISO instead of a DMG, recheck the edits very very carefully, nothing.

 

Did some Googling, found nothing other than unlocker should work with this build.

 

Finally I decided to re-read this entire thread in case someone experienced something similar when I came across the smc.present edit - since that was *TODAY* it meant that I had put it to "TRUE" on my semi-successful attempt but "FALSE" today.  Put it to "TRUE" in the VMX file and it works!

 

My ESXi host hardware is an AMD FX8350 @stock clock, GA-990FXA-UD5 Rev. 3 motherboard w/latest BIOS, 32GB RAM.

 

Just a note for anyone trying this.  I did *NOT* get a kernel panic with either setting.

Link to comment
Share on other sites

 

The big one I saw was on line 280 (your log): <2014-03-08T03:09:49.807Z| vmx| I120: DICT               smc.present = TRUE>

 

This is supposed to be set to FALSE.

 

 

Actually you need it on, as my unlocker fixes it up so that there is an SMC present. Thanks for the other details I ill take a look at the CPUID details as that is where the "secret suace" will be.

Link to comment
Share on other sites

  • 4 weeks later...

Actually you need it on, as my unlocker fixes it up so that there is an SMC present. Thanks for the other details I ill take a look at the CPUID details as that is where the "secret suace" will be.

 

wingshigh.g & subcan  - I haven't forgotten you but have been looking at what can be achieved and possibly have something I would like you to try for me. It has taken me time but I have found some new undocumented VMX file settings, plus had to get CPUID dumps from a few older real Macs. (Thanks Binky!)

 

It is possible to mask all the CPUID leaves in VMware with some additional settings. The only one not to touch is 80000008 as probably won't start the VM.

 

Can you remove all CPUID settings from your VMX file and add this into it please and see if it boots? (Make sure you keep a copy of the original VMX first.)

 

cpuid.inhibitDarwinMasks = "TRUE"
monitor_control.enable_fullcpuid = "TRUE"
cpuid.0.eax.amd = "0000:0000:0000:0000:0000:0000:0000:1101"
cpuid.0.ebx.amd = "0111:0101:0110:1110:0110:0101:0100:0111"
cpuid.0.ecx.amd = "0110:1100:0110:0101:0111:0100:0110:1110"
cpuid.0.edx.amd = "0100:1001:0110:0101:0110:1110:0110:1001"
cpuid.1.eax.amd = "0000:0000:0000:0001:0000:0110:1110:0101"
cpuid.1.ebx.amd = "0000:0000:0000:0001:0000:1000:0000:0000"
cpuid.1.ecx.amd = "1111:1110:1011:1010:0010:0010:0010:1011"
cpuid.1.edx.amd = "0000:1111:1010:1011:1111:1011:1111:1111"
cpuid.2.eax.amd = "0111:0110:0000:0011:0101:1010:0000:0001"
cpuid.2.ebx.amd = "0000:0000:1111:0000:1011:0010:1111:1111"
cpuid.2.ecx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.2.edx.amd = "0000:0000:1100:1010:0000:0000:0000:0000"
cpuid.3.eax.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.3.ebx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.3.ecx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.3.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.4.0.eax.amd = "0000:0000:0000:0000:0000:0001:0010:0001"
cpuid.4.0.ebx.amd = "0000:0001:1100:0000:0000:0000:0011:1111"
cpuid.4.0.ecx.amd = "0000:0000:0000:0000:0000:0000:0011:1111"
cpuid.4.0.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.4.1.eax.amd = "0000:0000:0000:0000:0000:0001:0010:0010"
cpuid.4.1.ebx.amd = "0000:0001:1100:0000:0000:0000:0011:1111"
cpuid.4.1.ecx.amd = "0000:0000:0000:0000:0000:0000:0011:1111"
cpuid.4.1.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.4.2.eax.amd = "0000:0000:0000:0000:0000:0001:0100:0011"
cpuid.4.2.ebx.amd = "0000:0001:1100:0000:0000:0000:0011:1111"
cpuid.4.2.ecx.amd = "0000:0000:0000:0000:0000:0001:1111:1111"
cpuid.4.2.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.4.3.eax.amd = "0000:0000:0000:0000:0000:0001:0110:0011"
cpuid.4.3.ebx.amd = "0000:0010:1100:0000:0000:0000:0011:1111"
cpuid.4.3.ecx.amd = "0000:0000:0000:0000:0001:1111:1111:1111"
cpuid.4.3.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0110"
cpuid.4.4.eax.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.4.4.ebx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.4.4.ecx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.4.4.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.5.eax.amd = "0000:0000:0000:0000:0001:0000:0000:0000"
cpuid.5.ebx.amd = "0000:0000:0000:0000:0001:0000:0000:0000"
cpuid.5.ecx.amd = "0000:0000:0000:0000:0000:0000:0000:0011"
cpuid.5.edx.amd = "0000:0000:0000:0010:0001:0001:0010:0000"
cpuid.6.eax.amd = "0000:0000:0000:0000:0000:0000:0111:0111"
cpuid.6.ebx.amd = "0000:0000:0000:0000:0000:0000:0000:0010"
cpuid.6.ecx.amd = "0000:0000:0000:0000:0000:0000:0000:1001"
cpuid.6.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.7.0.eax.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.7.0.ebx.amd = "0000:0000:0000:0000:0000:0010:1000:0001"
cpuid.7.0.ecx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.7.0.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.8.eax.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.8.ebx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.8.ecx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.8.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.9.eax.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.9.ebx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.9.ecx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.9.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.a.eax.amd = "0000:0111:0011:0000:0000:0100:0000:0001"
cpuid.a.ebx.amd = "0000:0000:0000:0000:0000:0000:0111:1111"
cpuid.a.ecx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.a.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.b.0.eax.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.b.0.ebx.amd = "0000:0000:0000:0000:0000:0000:0000:0001"
cpuid.b.0.ecx.amd = "0000:0000:0000:0000:0000:0001:0000:0000"
cpuid.b.0.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.b.1.eax.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.b.1.ebx.amd = "0000:0000:0000:0000:0000:0000:0000:0001"
cpuid.b.1.ecx.amd = "0000:0000:0000:0000:0000:0010:0000:0001"
cpuid.b.1.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.b.2.eax.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.b.2.ebx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.b.2.ecx.amd = "0000:0000:0000:0000:0000:0000:0000:0010"
cpuid.b.2.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.c.eax.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.c.ebx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.c.ecx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.c.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.d.0.eax.amd = "0000:0000:0000:0000:0000:0000:0000:0111"
cpuid.d.0.ebx.amd = "0000:0000:0000:0000:0000:0011:0100:0000"
cpuid.d.0.ecx.amd = "0000:0000:0000:0000:0000:0011:0100:0000"
cpuid.d.0.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.d.1.eax.amd = "0000:0000:0000:0000:0000:0000:0000:0001"
cpuid.d.1.ebx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.d.1.ecx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.d.1.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.d.2.eax.amd = "0000:0000:0000:0000:0000:0001:0000:0000"
cpuid.d.2.ebx.amd = "0000:0000:0000:0000:0000:0010:0100:0000"
cpuid.d.2.ecx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.d.2.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000000.eax.amd = "1000:0000:0000:0000:0000:0000:0000:1000"
cpuid.80000000.ebx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000000.ecx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000000.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000001.eax.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000001.ebx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000001.ecx.amd = "0000:0000:0000:0000:0000:0000:0000:0001"
cpuid.80000001.edx.amd = "0010:1000:0001:0000:0000:1000:0000:0000"
cpuid.80000002.eax.amd = "0010:0000:0010:0000:0010:0000:0010:0000"
cpuid.80000002.ebx.amd = "0110:1110:0100:1001:0010:0000:0010:0000"
cpuid.80000002.ecx.amd = "0010:1000:0110:1100:0110:0101:0111:0100"
cpuid.80000002.edx.amd = "0100:0011:0010:0000:0010:1001:0101:0010"
cpuid.80000003.eax.amd = "0010:1000:0110:0101:0111:0010:0110:1111"
cpuid.80000003.ebx.amd = "0010:0000:0010:1001:0100:1101:0101:0100"
cpuid.80000003.ecx.amd = "0011:0011:0010:1101:0011:0111:0110:1001"
cpuid.80000003.edx.amd = "0101:0001:0011:0000:0011:0010:0011:0111"
cpuid.80000004.eax.amd = "0101:0000:0100:0011:0010:0000:0100:1101"
cpuid.80000004.ebx.amd = "0010:0000:0100:0000:0010:0000:0101:0101"
cpuid.80000004.ecx.amd = "0011:0000:0011:0110:0010:1110:0011:0010"
cpuid.80000004.edx.amd = "0000:0000:0111:1010:0100:1000:0100:0111"
cpuid.80000005.eax.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000005.ebx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000005.ecx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000005.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000006.eax.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000006.ebx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000006.ecx.amd = "0000:0001:0000:0000:0110:0000:0100:0000"
cpuid.80000006.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000007.eax.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000007.ebx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000007.ecx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
cpuid.80000007.edx.amd = "0000:0000:0000:0000:0000:0001:0000:0000"
#cpuid.80000008.eax.amd = "0000:0000:0000:0000:0011:0000:0010:1000"
#cpuid.80000008.ebx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
#cpuid.80000008.ecx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
#cpuid.80000008.edx.amd = "0000:0000:0000:0000:0000:0000:0000:0000"
  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...

Sorry for off topic - Donk, it's not possible to send you PM.  Is this by intention or mailbox full?  Thanks.

Hi it is intentional as was getting full with requests for help which should be in the threads. I can restart PM for now.

  • Like 1
Link to comment
Share on other sites

  • 8 months later...

Donk -

  I've been banging my head against this for two or three days now - no luck.  My brand-new AMD ESXi 5.5 machine refuses to boot OSX.  The patch applies perfectly (or so it seems) and I've tried various options including adding your CPU masks and other settings as above, verbatim.  Before the addition of the CPU masks, I'd get MacOS getting to the first moments of the boot (Apple logo splash) but then MacOS would lock up the CPU.  After the CPU masks added, now I get "Transport (VMDB) error -14: Pipe connection has been broken." on boot attempt.  I'd be happy to give you the full .vmx files, error logs, and even let you access the VMWare host remotely - I wiped a machine just for this test, so it has nothing else on it

 

System: ProLiant SL 165z G7  2 CPUs, 16 cores x 2Ghz  (AMD Opteron 6128)

Link to comment
Share on other sites

Donk -

  I've been banging my head against this for two or three days now - no luck.  My brand-new AMD ESXi 5.5 machine refuses to boot OSX.  The patch applies perfectly (or so it seems) and I've tried various options including adding your CPU masks and other settings as above, verbatim.  Before the addition of the CPU masks, I'd get MacOS getting to the first moments of the boot (Apple logo splash) but then MacOS would lock up the CPU.  After the CPU masks added, now I get "Transport (VMDB) error -14: Pipe connection has been broken." on boot attempt.  I'd be happy to give you the full .vmx files, error logs, and even let you access the VMWare host remotely - I wiped a machine just for this test, so it has nothing else on it

 

System: ProLiant SL 165z G7  2 CPUs, 16 cores x 2Ghz  (AMD Opteron 6128)

 

You cannot boot on AMD unless you use an AMD kernel inside the OS X. This is outside my area of expertise but there are others who may help out.

  • Like 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...