Hi all,
My first post and my first day attempting to use ESXi. Some background: I don't work as a sysadmin, but as QA (we don't have any sysadmins) at work, and I'm trying to set up a virtualized environment for macOS on a 2014 Mac Mini running VMWare ESXi 7.0, but I'm having some trouble with a few things:
Tried to attach the log file as well.
I would be really glad for some input to my thoughts and pointers to other resources that helps me get up and running.
Hey, hope you are doing fine
Let me reply between lines:
ESXi is an enterprise-class product and it's not intended to run on consumer class-hardware.
Nevertheless, it is supported on some models of mac.
Have you set up your ESXi server properly?
Are you able to power on virtual machines?
How are you starting the install process?
It looks like the 2014 Mac mini is in the VMware HCL for ESXi 7.0
This is the error found in the log
2020-09-28T11:13:28.623Z| vcpu-0| I125: Msg_Post: Warning
2020-09-28T11:13:28.623Z| vcpu-0| I125: [msg.Backdoor.OsNotFound] No operating system was found. If you have an operating system installation disc, you can insert the disc into the system's CD-ROM drive and restart the virtual machine.
It appears the virtual optical drive that is mapped to the ISO file is not connected.
2020-09-28T11:13:17.831Z| vmx| I125: DICT sata0:1.startConnected = "FALSE"
2020-09-28T11:13:17.831Z| vmx| I125: DICT sata0:1.deviceType = "cdrom-image"
2020-09-28T11:13:17.831Z| vmx| I125: DICT sata0:1.fileName = "/vmfs/volumes/5f7191a3-e989d3b6-a02e-787b8ac3bfb0/ISOs/Sierra.iso"
2020-09-28T11:13:17.831Z| vmx| I125: DICT sata0:1.present = "TRUE"
So first thing is to make sure it is connected to the VM.
There is also a strange entry.
2020-09-28T11:13:17.831Z| vmx| I125: DICT bios.bootRetry.delay = "10"
Do you really meant for that to be
bios.bootDelay = "10000"
since the value is in milliseconds. Note it is bios.bootDelay. I am assuming the delay introduced is to be able to press a key.
Alternatively to boot to the VM firmware directly you can also use
bios.forceSetupOnce = "TRUE"
which you can then choose EFI CDROM to boot (assuming it is connected to the VM). It just boots up to firmware only once and the same entry have to added again if you want to power up to the VM firmware.
If you have Fusion Pro running on another Mac you can connect to the ESXi running on the Mac mini.
Thanks for the quick reply.
At the moment, I have the ESXi web interface running and I seem to be able to upload files to the Data storage. When trying to create the VM, I click on "Virtual Machines" --> "Create / register VM". The help/guide window for creating a new VM appears. But for the sake of screenshots, I just went through the process again, but only this time I added the image during this process and now I have installed macOS without a hiccup - woohoo!
So I guess I just answered myself, with your help that my image did indeed work as expected, and it seems that there is a bug with ESXi that I can't edit and save the configuration to use the CD/DVD Drive when the VM is already created but powered off).
Many thanks for your reply, nachogonzalez
Glad to hear it worked, It seems like OS wasn't installed.
I'm not understanding this:
So I guess I just answered myself, with your help that my image did indeed work as expected, and it seems that there is a bug with ESXi that I can't edit and save the configuration to use the CD/DVD Drive when the VM is already created but powered off).
Are you able to right-click the VM and edit settings? Is CD-DVD drive connected?
Hi Bluefirestorm,
You are absolutely correct that the virtual optical drive was disconnected, thus why I couldn't start the .iso from it.
When it comes to the other parameter, bios.bootDelay = "", I have not done anything other than default values when creating the VM, so either something is off in the ESXi or my setup. But given that it works, I don't think it's an issue.
But cheers and thanks for highlighting the error and I appreciate the heads-up.
While I am able to right-click and select "Edit", the menu won't save the setting if I check the "Connected"-box for connecting the virtual optical drive (unexpected behaviour). However, if I create a new VM and connect the virtual optical drive from the create menu, it saves as expected.
Hope that enlightens the issue.