Replies: 27 comments 20 replies
|
As far as I know, this project isn't abandoned. It's just very quiet at the moment. Can you provide more details on how you achieved it? I would imagine that doing so would increase the chances of this project being able to make it work! |
|
Really? The main page says project abandoned, figured that was the end. I used the AMD opencore , added the cpuid flags for AMD to the vmx, installed from sequoia iso and updated oc and kexts to latest version. No issues other than the one I mentioned above. |
|
I may change my mind and bring it back but just for VMware. QEMU on anything other than macOS is extremely flakey. I have tried VMware Workstation recently and it does seem OK. |
|
I should add I had some VMware issues on Intel macOS but it was entirely my fault. I now only have a 2014 Mac mini and 2017 MacBook Air for any form of Intel testing as I have moved to Apple Silicon machines. Mac mini has OCLP installed to allow it to run a later version of macOS, specifically Sonoma. That works great except for messing up VMware Fusion. |
|
If you decide to have another go just for vmware, I am willing to test and support where possible. |
|
OK I've re-opened and committed a bunch of changes I made on my private repo. I will create a V1 release but need to make the readme a bit more coherent first. |
|
@DrDonk thanks for adding the vmhide.kext. Do you know if it is possible to launch the OC picker and boot into macos using an esxi vm profile other than a version of Mac OS as listed in vsphere? For example, choosing Other Linux 64bit, EFI boot and adding some vmx parameters? I have this really weird issue that I need to restart the OSX VM about 4-6 times before it actually boots to the OC menu. There seems to be no consistency to the number of attempts. It might work on the 2nd or 3rd attempt for example. When it does boot to the menu, the VM seems to work fine. |
|
FYI VMHide is disabled by default, so you will need to edit the config.plist on the OC image and change the boot-args vmhState=Enabled or Force. I've written a little script to change boot-args and that will be in V1 when I release it. It is coming the last thing to do is write some docs. I didn't want it to be enabled by default as it does affect other things like size of macOS updates from 2GB to full installer size. Are you using the VMX template I provide or have you just added the OC VMDK to an exiting VM? I can create an ESXi 8 VM and run nested to test. I no longer have access to vSphere/vCenter after Broadcom. |
|
It's all generated when run make.sh. However I just tried running a macOS vm with FreeBSD 64-bit as guest setting and works on Fusion so try that. vCenter checks the ESXi host that it is running on Apple kit before allowing macOS guests to start. ESXi does not care. You can have a look at my now archived ESXi Unlocker on how to patch that, but don't think it will work on latest ESXi as much more locked down. https://github.com/DrDonk/esxi-unlocker |
|
Update: it crashes the VM after awhile and no mouse and keyboard. I'll try something else for guests setting. |
|
I'll share my vmx for you to look at if that's ok? Apart from that odd power cycle issue it runs seq perfectly fine (when the VM finally boots). My system is am5 7900 and esxi 8.0u3c. |
|
Sure no problem. Just attach it rather than copy it inline to the post. |
|
MACOS01.vmx.txt |
|
I see quite a few lines which come from older days of running macOS on VMware, but mostly not needed for the OC4VM disk image. For example the cpuid lines, smc.version plus a few more. One question have you actually built the OC4VM images and templates yourself using the make.sh script on a macOS system. The vodkas in the repo are base images that have to be modified during the build phase to add settings and patches. I've never heard anyone successfully basing thru GPU on ESXi to a macOS guest. (I've been doing this stuff for 18 years now. |
|
i used an OC from a KVM repo updated it to 1.03, grabbed a 15.1.1 installer ISO and installed the OS that way. I had to add the AMD and other bits to the vmx manually. Might explain why i'm running in to a few issues. As for GPU, i defo got it working some time ago, think it was a GT710 using OCLP or might have been the radeon 4100. Whichever it was, i had to disable the svga in the vmx otherwise OC would throw a wobbly at the point of initialising vmtools on boot. |
|
Hang on found an issue with the make process for AMD. |
|
If you want t try mine you can build again from latest commit. Otherwise looks like you may be OK. Not sure about updating the VM. Maybe disable VMHide so that Apple knows it is updating a VM, otherwise it may try firmware updates as you have spoofed a real machine in your VMX file. |
|
@DrDonk David, can we expect a release soon? I have trouble building from the source on a M3 Mac. |
|
@DrDonk I'm really struggling getting passthrough to work for either my WX4100 or W6600 GPU. |
|
I am not in a position to test ESXi anymore and I can only test on macOS, Linux and Windows. Basically I have one Intel Mac mini left everything else is Apple Silicon. Also I have no experience in using passthru in ESXi, well not since I was an alpha tester of the very first version of ESXi! Perhaps the OpenCore config needs to be made more like a real hackintosh as real hardware being passed into guest, rather than the VMware Virtual SVGA adapter. Maybe someone else can help out. In the meantime perhaps need to look at this https://dortania.github.io/GPU-Buyers-Guide/modern-gpus/amd-gpu.html and may be need https://github.com/acidanthera/WhateverGreen. Can you send me your latest VMX file and I will tell you how to use the debug level version of the OC4VM image. |
|
Attached is a test OC4VM with all the OpenCore and macOS kernel debugging switched on and sent to serial port. The VMX file has been altered to add a serial port which outputs to serial.log in the VM folder. This means once you start the VM and select macOS screen output will stop as it's going to the serial port. I also edited the CPUS back to 2x2 as I tested that this boots in QEMU and cannot run 8X8. Please leave that just for the moment. I sorted the lines in the VMX so I could check it and added my changes to the top of the file. The OC vmdk has debug WhateverGreen.kext added and should load from Catalina onwards. Also debug parameters for this kext are enabled and the agdpmod=pikera boot arg added. Look for "WhateverGreen" in the serial logs to help debug any issues. That's as much as I can do for you as no ability of knowledge to test AMD Radeon GPUs. So in the zip is VMX and opencore.vmdk. Of course you will need to copy them to ESXi. I'm sure you know to copy originals somewhere else so you can rollback. |
|
Attached 2 zips one with raw DMG in it, second with ESXi flat vmdk. Used:
|
|
I have made a mistake and sent you an AMD image as I thought you were on AMD. I'm not around kit to build a new one but maybe you can attach the vmdk to another VM Windows or Linux and edit the config.plist file. You will need to remove all the Kernel Patches section. |
|
Hi ! |
|
@DrDonk I'm curious if you can help me out with just previous knowledge. I am running ESXi 6.7(I know you can't test on it anymore), and I was trying to run one of the unlockers you've built in the past. I believe it was for ESXi 7.0. I'm running that one because I can't find one that will work with 6.7. That being said, your unlocker keeps trying to run python 3.6 using f strings, but 6.7 only has python 3.5. I'm having a hard time finding out if the unlock works, as running the check says that smcPresent is true, but when I try to load MacOS Sonoma or Sequoia onto it, I get stuck in a boot loop. I suppose my question is, do you have an older version that may work with this, or is there a way that I can run that newer python on something like that that you know of? I'm running on older hardware and I believe 6.7 is the newest ESXi version that I can use. Thank you! |



Uh oh!
There was an error while loading. Please reload this page.
It's a shame this project is abandoned. Today I had another go at running sequoia on esxi 8 with AMD 7900 CPU and managed to get it installed, added vmhide kext to get around the apple account issue, installed VMtools and it seems to be working ok. Next step is for me to try w6600 pro GPU passthrough for gfx acceleration.
One really odd issue that I never saw before is that it can sometimes take a few attempts to boot from the oc picker. It's completely random. Sometimes it just goes into a boot loop until the 3rd or 4th attempt at which point it boots ok. Strange.
All reactions