Menu
Not able to access internet on guest OS VMware Fusion 11 with mac OS 12 Monterey. The network adapter used is "share with my mac" same works for mac OS 11 but not working on 12. Is shows self-assigned IP.
Any work around?
352
Select a virtual machine in the Virtual Machine Library window and click Settings. Under Removable Devices in the Settings window, click Network Adapter. Select the Connect Network Adapter check box. Fusion retains and reapplies the setting you select when you start up the virtual machine.
Shut down the virtual machine, then restart your Host Machine. After your Host machine reboots, reopen Workstation. Download and reinstall VMware Workstation. This ensures that you have the most recent version, and that any missing or corrupted virtual network settings are replaced/repaired.
The Desktop Hypervisor team at VMware is happy to announce the release of the latest update to Fusion 12, with changes to support macOS Monterey hosts, fixes for some persistent bugs, as well as improvements to the security and management of Fusion at scale.
The reason seems to be explained here: Thread "Big Sur hosts with Fusion". Main point: Fusion is no longer able to provide its own DHCP server and the Apple server has only few configuration possibilities (and there may be some more bugs). Possible workaround: Configure IP manually inside the guest instead of using DHCP.
But, if your ESXi server is not a Mac, there's a patch you need to apply to allow it to run macOS VMs. (The symptom you described is exactly what happens without that patch.) You'll have to search for it. 06-27-2022 05:41 PM Hi, thanks for quick reply. My ESXi server is actually a Mac so no patches needed (I know what you're talking about).
To run Ventura in a VM you will need a newer Intel Mac. For safety (as I noted) you should use a Mac model which has an Intel processor and is officially supported by Ventura, as listed in the article linked by @dlhotka , or in brief any 2017 or later Intel Mac model apart from the 2017 MacBook Air.
In this release, if we don’t use the NIC type ‘vmxnet3’, we will have issues getting an IP Address in the VM. Locate the below (search “virtualDev” or “e1000e”) in your VM's VMX file (option+right click on your VM, select "Open config file in editor".
ethernet0.virtualDev = "e1000e"
Replace “e1000e” with “vmxnet3”.
ethernet0.virtualDev = "vmxnet3"
Once that's done, restart the VM. If this doesn't work, rebuild your VM with this option set from the start.
I have a blog on this topic which should get you going. https://blog.eucse.com/how-to-run-macos-monterey-12-beta-in-vmware-fusion/
137
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
