- Joined
- Aug 15, 2024
- Messages
- 1
You have 2 options: either leave it in automatic mode and macOS will have a predetermined ip depending on the ip of the modem router.Hello! I was wondering what information I have to put for the Bridged connection. It wants me to set this up manually and there are no predetermined values to throw in there. Any tips?
View attachment 14780
you don't need Kext because Opencore's Kext directory already has the kext for the macOS network.I was able to update macos 14 to sequoia and was able to login / use imessage etc so that's great. my bigger goal is to be able to use screen mirroring, i bought a usb wifi dongle which i can present directly to the guest vm but the guest isnt seeing the hardware. do I need to add the wifi kext in opencore?
I am passing the usb wifi adapter directly to the vm (connected) so it wont be a matter of configuration on the host. the vm isnt seeing the adapter, the option to enable wifi is grayed outyou don't need Kext because Opencore's Kext directory already has the kext for the macOS network.
Probably some incorrect network configuration could be the problem.
Have you set it to Bridge mode? Check the previous post for a configuration example.
vmware can use your windows network configuration and that includes wifi. I don't know why you want to directly use the wifi connected to the virtual machine's shared usb. That's not necessary.I am passing the usb wifi adapter directly to the vm (connected) so it wont be a matter of configuration on the host. the vm isnt seeing the adapter, the option to enable wifi is grayed out
yea, I am only doing it because sequoia needs to see wifi for screen sharing. using the host adapter, even it is wifi still maps it to an ethernet adapter in the guest unless im missing somethingvmware can use your windows network configuration and that includes wifi. I don't know why you want to directly use the wifi connected to the virtual machine's shared usb. That's not necessary.
If you're referring to screen sharing from your iPhone to your macOS, I don't know if it's possible.yea, I am only doing it because sequoia needs to see wifi for screen sharing. using the host adapter, even it is wifi still maps it to an ethernet adapter in the guest unless im missing something
Activating Bluetooth for the guest OS on vmware I've never done and I don't know if it's possible with macOS.Your iPhone and Mac need to be signed into the same Apple ID, and two-factor authentication must be enabled for the iPhone Mirroring feature to work. You will also need to turn on Bluetooth and Wi-Fi, and the two devices will need to be near each other.
Reread the tutorial and go through the whole sequence again and recreate a new virtual machine:Hey folks mine just says guest host disabled CPU. any ideas ? I am using 8 core and unlocker 3.0.x
AMD Rizen 3700X
vmkfstools -i macOS_Opencore_1.0_4_cores.vmdk -d thin macOS_Opencore_1.0_4_cores-esx.vmdk
I recommend that you uninstall and reinstall vmware from scratch, patch it and create a new default virtual machine without changing anything and following only what is suggested in the tutorial.Hi again ! 4 and 8 cores working very stable. tested in a lot of build hours. 16 cores sometimes hangs the VM with next after reboot error any suggestions welcome!
I'm not familiar with ESXi, but VMWare emulates the appropriate hardware for installing macOS, which is hidden. You need to apply the patch to release the choice of this type of machine called macOS 14.thanks a bunch for this @tucano2000
My home server is running ESXi 8 update 3 AMD is a 128GB RAM with AMD5950x CPU.
I've started off with the 1 socket by 4 cores configuration with 8GB RAM.
Because type 1 vmdk's aren't supported on ESXi, I run this from the SSH console of ESXi host
vmkfstools -i macOS_Opencore_1.0_4_cores.vmdk -d thin macOS_Opencore_1.0_4_cores-esx.vmdk
I then create the VM as per you instructions but set it to use ESXI 7 update2 compatibility - as that was the last ESXi 7 update 2 to support MacOS X.
I set the OS type to be OSX12.
I use the DrDonk Unlocker for ESXi.
I'm able to install the 14.6.1 inside a VM, and was able to boot it afterwards - which is great.
but I've found the OS will hang randomly and randomly reboot.
My ESXi host is running an AMD 5950X and running ESXi8 update 3 (the latest).
It feels like this is really close to working.
Any ideas here?
thanks, I've been using; https://github.com/DrDonk/esxi-unlocker for years and that worked well prior to Ventura on ESXi (provided that the CPU masks were set as you say). On this I haven't set up any of the CPU masks as I understand OpenCore is working its magic at that layer. I'll try with the 8 core version to see if the behavior is any different. thanks again.I'm not familiar with ESXi, but VMWare emulates the appropriate hardware for installing macOS, which is hidden. You need to apply the patch to release the choice of this type of machine called macOS 14.
The patch in the tutorial is specific to VMWare Workstation Player and VWWare Worstation Pro.
I don't know if you've tried patching ESXi. There is a project about it on GiHub and you could try it.
GitHub - netgc/esxi-unlocker-4: macOS Unlocker v4 for VMware ESXi
macOS Unlocker v4 for VMware ESXi . Contribute to netgc/esxi-unlocker-4 development by creating an account on GitHub.github.com
I haven't tested it and I don't know if it works and if that's the case.
Do not use the cpuid codes in the vmx file if you are using the opencore vmdk.
How come in Workstantion Pro, ESXi doesn't have OSX14 ?thanks, I've been using; https://github.com/DrDonk/esxi-unlocker for years and that worked well prior to Ventura on ESXi (provided that the CPU masks were set as you say). On this I haven't set up any of the CPU masks as I understand OpenCore is working its magic at that layer. I'll try with the 8 core version to see if the behavior is any different. thanks again.
So I'm using ESXi and not workstation so Mac OS is no longer supported on ESXi on a virtual hardware level after 7update2 - hence the reason why under 8update3 I need to set the hardware compatibility level downwards. VMware stopped supporting Mac OS on ESXi shortly after Mac announced the switch to M1.How come in Workstantion Pro, ESXi doesn't have OSX14 ?
In test here Workstantion if not use vmxnet3 driver in vmx file the system reboot.
There are some upload problems with the vmxnet3 drive but they can be solved using the commands in the macos terminal as described in the tutorial.So I'm using ESXi and not workstation so Mac OS is no longer supported on ESXi on a virtual hardware level after 7update2 - hence the reason why under 8update3 I need to set the hardware compatibility level downwards. VMware stopped supporting Mac OS on ESXi shortly after Mac announced the switch to M1.
But you were spot on with the NIC type. On ESXi for Mac OS was set to e1000e so I've switched that now to vmxnet3 and Im getting bridged netwrok connectivity and stable OS on ESXi8, the thing feels quite snappy - I'll run further tests.
Wahoo! thanks again! Brilliant work by you on this - you sir deserve a medal!
It makes me so mad that Apple doesn't allow for development builds for IOS to be compiled on anything other than Apple tin, its incredibly restrictive, and this is my only motivation for wanting to do this.
I have about 12TB of RAM on our VMware cluster (but that is Intel based so Im not sure what I'll need to do yet on that) - if we were legally able to provision OSX VDIs for our teams we could use things like USB Over IP via things like;
https://www.virtualhere.com/ to help the developers with remote USB attached debugging.
View attachment 14830