- #INSTALL MAC OS ON VMWARE ESXI 6.5 FOR MAC#
- #INSTALL MAC OS ON VMWARE ESXI 6.5 INSTALL#
- #INSTALL MAC OS ON VMWARE ESXI 6.5 UPDATE#
- #INSTALL MAC OS ON VMWARE ESXI 6.5 UPGRADE#
#INSTALL MAC OS ON VMWARE ESXI 6.5 UPGRADE#
Also,despite stating it is supported it is still not listed on the host as an available guest OS.Īs a work around, upgrade to macOS 10.Have a technical question? Just make a self post!ĭiscussion of piracy methods will not be permitted. Performance with snapshots still sucks under 6.5 on that hardware.
#INSTALL MAC OS ON VMWARE ESXI 6.5 INSTALL#
If using VSphere, VMs can be moved to different storage devices without worrying about APFS Good information, thanks! The KB attached to the support page you linked shows the following as another way to allow upgrade without APFS conversion, although that doesn't sound like it helps one install 10.13 from scratch. The APFS conversion is no longer an issue since it is not performing the installation and seeing an SSD to perform the conversion during a clean install. Once done either VM can be configured and made to be used as templates for quick deployment.
Format internal disk to Mac OS Extended (Journaled) (I preferred using this method to preserve a typical Mac hardware deployment)ģ. The issue states that the virtual SATA controller will see the ESXi hosts internal SSD and creates a virtual SSD drive which causes the installer to perform the APFS conversion on installation. The issue with the APFS conversion happens only on storage devices running VMFS5+ and virtual SSD drives. Second workaround is to have an NFS storage device assigned to your ESXi host for the creation of the new VM. Create a VM and customize during creationĦ. This is not the typical Mac configuration but works to deploy VMs for testing.ġ. The fix doesn't seem to work from the test deployments I made but did happen to find to ways to get around the APFS conversion.įirst workaround is to remove the virtual SATA HDD then add a virtual iSCSI controller and SCSI HDD when creating a new VM. Found that High Sierra is supported now from the guest compatibility chart on VMware site but only explains that the APFS issue is a known problem, they have a documented work around. Once I started to do the same same on 10.13 I was able to see first hand the issues reported.
#INSTALL MAC OS ON VMWARE ESXI 6.5 FOR MAC#
I have recently deployed a LAB for Mac VMs and was running ESXi 6.5 on MacPro (Late 2013) with a VSphere Appliance 6.5 to manage and seemed to work without issue performing a clean install on 10.12. I'm probably going to end up going to fusion soon w/ me logged into the console 100% of the time to keep the vms running if I cannot figure something out. Might be something going on there with APFS. The 10.12 ISO sees the internal disk, but with 0 partitions, and lists it as "unformatted". At this point I boot from a 10.12 installation iso to open disk-utility and see what the status is of the disk. When I run an upgrade of the OS from 10.12.6 to 10.13 the system eventually gets to a reboot where it cannot find any boot disks and gives me the standard vmware blue ansi boot menu. Booting from 10.13 installation iso I still cannot see the virtual disks.
#INSTALL MAC OS ON VMWARE ESXI 6.5 UPDATE#
I'm not sure what the difference is between 6.0 and 6.5, but something is very wrong here.Īnyway, worse luck with 10.13 after the bios update and ESXi upgrade. Even a copy of a 5gb file from an SMB share brings it to its knees with the guest responding to key-presses intermittently and the host web interface taking 5-10 seconds to fill in information when navigating around. Once I take a snap it keeps giving me the pin-wheel ever few seconds. 1vm running on the host with macos 10.12.6 with a thick provisioned disk runs fine without a snapshot. On a host with a 1tb SSD, 32gb of ram, 12core processor, it should be fine. Performance is TERRIBLE now when a VM has a snapshot. Yay apple! Prior to the wipe I had 1 vm that I was able to upgrade to 10.13 without issue.Īfter updating the bios I wiped the internal SSD and installed ESXi 6.5 u1 w/ the October update. I found that I had to wipe ESXi completely off the system to install OSX 10.9 on the internal disk of the system because that is the only place and OS that the bios update for this system would run from.
Per suggestion of someone on the vmware communities ESXi forums I updated the bios of the MacPro I use, which has just made things worse.
0 kommentar(er)
