Mac OS install on AMD Ryzen/INTEL (VMWare) Opencore - Improved Performance - Works with Sequoia / Sonoma / etc

[tucano2000]

Hey all! I have a Ryzen 7950X3D, VMWW 17.x and Sequoia working very well. Thank you for this forum!!! My only apparent issue is this delay. I searched before asking this but could not find anything for 'mouse delay'. When I click a menu, nothing happens. When I click a menu and move my mouse a little, then the menu shows. It does this everywhere. And the highlight does not match where my mouse actually is in the VM. But I hover the mouse where I want to click, and that does still work. Is that a resolution issue possibly? I set my VM to exactly 1/2 of my 4k total resolution of my monitor in full screen. Maybe related to this, in terminal, typing commands is one character off. This is a clean windows 11 pro 24H2 host and fresh vmware with all the patches and fixes from the top of this thread. If nobody is saying anything about this, or calling it something else, what could it be that is behind this issue? To explain the one character off, imagine I went to this line: test 01 and went to delete the space between 'test' and '01'. If I allow myself to move to the space, and hit delete, it deletes the 't' in 'test' rather than the space between which was highlighted. I can 'deal' with that since I know where I need to go to sort this out, it's very odd behavior. Hopefully there is an easy fix to this. Thanks again for all this!!

The problems reported can indeed be considered strange, but it's not common because from what I've researched few people use 4k resolution on virtualized macOS.

The cursor and mouse is usually a problem of poorly activated graphics acceleration (QE/CI) caused by VMWare Tools.

If you uninstall it, the problem should disappear, but there's no way you'll be able to configure a higher resolution without it.

One solution would be to try smaller resolutions such as 1920x1080, 2560x1440 or 1440x900. The advantage is that you can choose any resolution value close to 4k.

Avoid exactly “half of 4K”, as this can cause pixel mapping problems in the VM.

As for the problem with the mouse, you could also try disabling the mouse's graphics acceleration in 4k resolution by running the command in the terminal:

defaults write .GlobalPreferences com.apple.mouse.scaling -1

Make these changes and let us know the result, but in principle VMWare Tools no longer receives updates and this must be the exact cause of the problem, which must be solved in some other way.

 

[6StringDemon]

One solution would be to try smaller resolutions such as 1920x1080, 2560x1440 or 1440x900. The advantage is that you can choose any resolution value close to 4k.

Avoid exactly “half of 4K”, as this can cause pixel mapping problems in the VM.

As for the problem with the mouse, you could also try disabling the mouse's graphics acceleration in 4k resolution by running the command in the terminal:

Yes. This was it. I have a 65inch screen for my main desktop and having full 4k+ (4096x2160) is amazing. I need that real estate on my screen for my DAW and am testing that in the OSX VM with Logic Pro. And adjusting to 60% of 4k+ really made the issue nearly go away. And I made your suggested change to mouse acceleration and recalled an issue with gaming in VNC that caused problems unless you set it to gaming mode which effectively (in VNC) forced exact movement of the mouse per-pixel-exact once the screen had focus. So it got me thinking to take this information you provided and try switching to gaming only mode in VMware workstation preferences>input>optimize mouse for games = Always. And THAT fully fixed the issue. I immediately noticed that I needed to go into OSX and accelerate my mouse again of course. But after that re-adjustment, I was able to move around the mouse in OSX just like before, but I gained a hyper-responsive mouse for all menus. The drawback is that to exit the OSX-VM, I do have to hit (CTL+ALT) to release the mouse to Windows. But for me I think, the added benefit of further suspending disbelief that my OSX VM is a bare-metal mac, it's really worth it. So long story short is that testing different resolutions showed that half res was not so great but that 60% was a bit of a sweet-spot for compromise between mouse capture in the VM and responsive menus. And setting Gaming mode for input mouse to Always makes the OSX VM perform flawlessly with the only drawback of manual capture and release of the mouse. Thank you for your guidance on this as it took me right to a fix that worked, and that path led me to here. So I have some options, and my problem is fixed!

 

[tucano2000]

Yes. This was it. I have a 65inch screen for my main desktop and having full 4k+ (4096x2160) is amazing. I need that real estate on my screen for my DAW and am testing that in the OSX VM with Logic Pro. And adjusting to 60% of 4k+ really made the issue nearly go away. And I made your suggested change to mouse acceleration and recalled an issue with gaming in VNC that caused problems unless you set it to gaming mode which effectively (in VNC) forced exact movement of the mouse per-pixel-exact once the screen had focus. So it got me thinking to take this information you provided and try switching to gaming only mode in VMware workstation preferences>input>optimize mouse for games = Always. And THAT fully fixed the issue. I immediately noticed that I needed to go into OSX and accelerate my mouse again of course. But after that re-adjustment, I was able to move around the mouse in OSX just like before, but I gained a hyper-responsive mouse for all menus. The drawback is that to exit the OSX-VM, I do have to hit (CTL+ALT) to release the mouse to Windows. But for me I think, the added benefit of further suspending disbelief that my OSX VM is a bare-metal mac, it's really worth it. So long story short is that testing different resolutions showed that half res was not so great but that 60% was a bit of a sweet-spot for compromise between mouse capture in the VM and responsive menus. And setting Gaming mode for input mouse to Always makes the OSX VM perform flawlessly with the only drawback of manual capture and release of the mouse. Thank you for your guidance on this as it took me right to a fix that worked, and that path led me to here. So I have some options, and my problem is fixed!

Nice... Excellent Work !!!

 

[6StringDemon]

Nice... Excellent Work !!!

First off, a big thank you—I did this because you knew exactly what to check. So, for anyone else facing this issue, here's an unexpected resolution:


After switching to gaming-only mode in settings for mouse input, I decided to switch back to 'auto'—and to my surprise, it kept working as if it were still set to gaming! Whaaat?! It seems to be one of those classic Windows quirks where disabling and re-enabling a setting somehow fixes the issue. But hey, I’ll take it! Now my mouse moves in and out of the VM seamlessly, menus are snappy, and everything is running smoothly.


On top of that, I’m thrilled that I got this working with iCloud too! While I do have an older Mac upgraded using Legacy Open Core, what’s been really helpful is running macOS in my VM on my big screen—having that extra space makes a big difference.


Now, here are three key issues I’d love to improve:


FaceTime mic audio – Right now, the microphone input is static-filled and glitchy for the recipient on FaceTime. I really need to find a way to get cleaner, more reliable mic input.


DAW audio input (Logic Pro) – I’d love for audio input to work smoothly and reliably in Logic Pro. I may be able to route things through my Helix Rack mount via USB, but if anyone has experience improving USB audio passthrough in VMs, I’d love some insights!


FaceTime responsiveness – The video and audio lag, and sometimes the VM struggles to stay responsive on FaceTime. If there’s a way to prioritize FaceTime performance so the VM updates in real-time without delays or break-ups, that would be a game-changer.


I haven’t fully scanned the forum yet for audio fixes, FaceTime tweaks, or ways to get a USB Wi-Fi adapter to act like built-in Wi-Fi, but if anyone has ideas or links, I’d love to hear about it!

 

[Sebastian's Epic Videos]

Can someone make a macOS Tahoe version? It just kernel panics when I try to update to macOS 26

 

[severian]

There are some reports that macOS doesn't work internet in Bridge mode and depends on NAT.

It seems that depending on the configuration of the VMWare machine, it can't detect the correct network adapter in automatic mode.

To fix this, do the following:

In VMWare click on Edit and then choose Virtual Network Editor

View attachment 17101

In the window that opens, select VMNet1 and click Change Settigns.



Now select VMNet0 and then choose the local network adapter used on your host computer in the “Bridged to:' option. The name of the adapter will depend on which type exists on your machine.



Press OK and start your hackintosh.

Hi @tucano2000
I can't' make this work, it shows 4 "Qualcomm FastConnect 6900 Wi-Fi.... ", where do you see the "bridged to..." device? Right now I'm using NAT and it works fine, but the Mac shows the WiFi inactive and I need it to sync my phone.
Thank you!

 

[tucano2000]

Can someone make a macOS Tahoe version? It just kernel panics when I try to update to macOS 26

Not yet. I have a loop reboot in the Tahoe installation that happens right after this screen on an AMD PC with VMWare:



I changed the MaxKernel of the patch to 25.99 and with or without -lilobetaall the result doesn't change even when updating kexts.

I'll test it on Intel later.

 

[tucano2000]

Hi @tucano2000
I can't' make this work, it shows 4 "Qualcomm FastConnect 6900 Wi-Fi.... ", where do you see the "bridged to..." device? Right now I'm using NAT and it works fine, but the Mac shows the WiFi inactive and I need it to sync my phone.
Thank you!

Do you have 4 adapters with the same name? If so, then for some reason you have installed more than once and not removed the previous ones. That's not normal.

Did you try all four and it didn't work?

For ethernet it works but I haven't tested it on Wifi yet.

 

[Edhawk]

Is -lilobetaall a spelling mistake you made here or is this what you used in the config.plist? As it should be -lilubetaall.

MaxKernel should be 25.99.99 for Tahoe.

 

[severian]

Do you have 4 adapters with the same name? If so, then for some reason you have installed more than once and not removed the previous ones. That's not normal.

Did you try all four and it didn't work?

For ethernet it works but I haven't tested it on Wifi yet.

yes, they end in a different number, and I tried the 4 of them, but I'll try to remove them and start fresh.
Yes, it's working as "ethernet" (even if it's a physical wifi adapter) but if I try to activate the WiFi in Mac OS it doesn't work, and I wanted to try to sync my iphone, not sure if it's possible.

Thank you!

 

[tucano2000]

Is -lilobetaall a spelling mistake you made here or is this what you used in the config.plist? As it should be -lilubetaall.

MaxKernel should be 25.99.99 for Tahoe.

yes. you're correct... I misspelled only here on the forum in both cases.

 

[tucano2000]

Here's the Tahoe Beta iso.

Tahoe.zip

If anyone wants to help try to create the opencore boot file containing the .vmdk
I tried the installation, it shows a black screen and then restarts after the installer shows the Data and Privacy screen.

 

[Edhawk]

You may need to use the latest release of OC 1.0.5, as it contains a fix for Tahoe.

Builds

You should also have a look at this thread containing links to latest AMD Kernel Patches and revised kexts for Tahoe.

Thread 'macOS Tahoe'

Jun 11, 2025

​

Patches didn't need updated to run the latest beta, only change to MaxKernel. Use at your own risk. It's beta software and may break.

Note: We don't support beta versions of macOS. Forum sections for Tahoe are open but support is extrememly limited.

GitHub - AMD-OSX/AMD_Vanilla at beta

Native AMD macOS via OpenCore. Contribute to AMD-OSX/AMD_Vanilla development by creating an account on GitHub.

github.com

• Shaneee
• Replies: 14
• Forum: Chit Chat

• 

 

[tucano2000]

You may need to use the latest release of OC 1.0.5, as it contains a fix for Tahoe.

Builds

You should also have a look at this thread containing links to latest AMD Kernel Patches and revised kexts for Tahoe.

Thread 'macOS Tahoe'

Jun 11, 2025

​

Patches didn't need updated to run the latest beta, only change to MaxKernel. Use at your own risk. It's beta software and may break.

Note: We don't support beta versions of macOS. Forum sections for Tahoe are open but support is extrememly limited.

GitHub - AMD-OSX/AMD_Vanilla at beta

Native AMD macOS via OpenCore. Contribute to AMD-OSX/AMD_Vanilla development by creating an account on GitHub.

github.com

• Shaneee
• Replies: 14
• Forum: Chit Chat

• 

The same problem remains. I updated the Opencore and Kernel Patch to 25.99.99.

I'm not sure, but I think that right after the Data & Privacy Screen, macOS Tahoe is trying to activate a 3D video acceleration mode that VMWare doesn't have and then macOS starts a controlled reboot process. In other words, there is no crash. I'll try it later with Opencore Debug but I saw macOS itself listing commands to reboot the mac.

 

[Edhawk]

To be honest anyone trying to run Tahoe at this damage in its development n a VM is taking the Micky (I am being polite).

It is my believe that as Tahoe is still at the first Developer Beta stage, that getting a VM to work on Tahoe won't really be sensible till we are near the first public release. Testing is fine between now and then. But anyone thinking they are going to have a stable VM it dreaming. Too many things can change and will change between now and the first official release.

Everyone should be told to hold their horses and wait until Tahoe is at least at the Public release stage before trying to run a Tahoe VM.

 

[tucano2000]

To be honest anyone trying to run Tahoe at this damage in its development n a VM is taking the Micky (I am being polite).

It is my believe that as Tahoe is still at the first Developer Beta stage, that getting a VM to work on Tahoe won't really be sensible till we are near the first public release. Testing is fine between now and then. But anyone thinking they are going to have a stable VM it dreaming. Too many things can change and will change between now and the first official release.

Everyone should be told to hold their horses and wait until Tahoe is at least at the Public release stage before trying to run a Tahoe VM.

I agree with you that Tahoe is incomplete and unfinished. I'm sure they'll still make a lot of changes and I hope that with these tests we'll be able to analyze if there's any evolution in the new versions of macOS Beta.

I'll be reporting on the progress and if anyone knows anything new in this regard for virtual machines, please post it here.

I know of a project with QEMU on Linux, which is a virtual machine running Tahoe. But each virtual machine has its own characteristics, so there's no way to compare. The way is to wait for new versions of Tahoe.

Thank you.

 

[mragab85]

Hi, I want to add more power the VM currently running at 8 core, can I download the 16 core and mount it to get the 16 core running, or does it need a full installation? Thanks!

 

[tucano2000]

You can add more cpu core even if your processor is inferior, but the performance won't increase much.

This percentage I tested on my cpu which has 8 physical core so I used the 16 core vmk file with vmware in 16 core and got an improvement of 5 to 10%.

 

[Edhawk]

Adding more cores to the VM doesn’t mean that the system will use them all. As it will depend on whether the application you are using in the VM can make use of the multiple cores that are available.

 

[rasworth]

Hi all, brand new member. Per this thread, installed Ventura and Sequoia on my Yoga, Ryzen 7 8840HS. The Ventura install worked fine, loaded up VMware tools and able to "pull" it to any resolution. However, the Sequoia version is stuck at 1024 x 768. When pulled the VMware window expands, but not the mac image. Same for full screen. VMware tools install went fine on Sequoia. No luck adding new resolution, terminal line goes thru the process apparently successful, and then ends up with update not accepted.

I have searched for similar situation, no luck, any suggestions? I've tried a number of reinstalls, resets, etc., no progress. Again, the Ventura version is fully functional.

Richard Southworth