3 ms·
> We can’t just buy hideous Xeon workstations from Dell and install macOS on them. Sure you can. Or rather, you can install the [free] VMWare ESXi hypervisor o
by derefr 10y ago
> We can’t just buy hideous Xeon workstations from Dell and install macOS on them.
Sure you can. Or rather, you can install the [free] VMWare ESXi hypervisor on said hideous box, and then install macOS on that. The ESXi hypervisor is an officially-supported macOS hardware configuration. Apple want you to only run macOS guests through ESXi if you're on macOS hardware, but there's literally nothing stopping you from doing otherwise.
Default new USB device attachments to the macOS VM; add a USB Bluetooth dongle; use SR/IOV to feed the VM a dedicated video card, and plug your monitor into that. You'll never even know ESXi is running.
Side benefit: cheap sibling Linux VMs!
- UnoriginalGuy 10y ago> The ESXi hypervisor is an officially-supported macOS hardware configuration. ON APPLE HARDWARE. If you run MacOS on non-Apple hardware it isn't officially supported at all, effectively piracy, and you need to hack ESXi to make it work at all (ESXi Unlocker, etc). > but there's literally nothing stopping you from doing otherwise. Except the license agreements (both Apple and VMWare), and the fact that ESXi won't do it unless modified.
- derefr 10y ago> If you run MacOS on non-Apple hardware it isn't officially supported at all By "officially supported", what I mean is that Apple supports VMWare in developing drivers for ESXi, so neither new versions of ESXi, nor macOS updates, will suddenly break macOS ESXi guests. You can put the same expectations on the stability of the ESXi hypervisor in running Apple software as you can on Apple hardware in running Apple software. (This contrasts with the Hackintosh driver ecosystem, where every time macOS updates you have to figure your compatibility out all over again.) Now, the other half of that—the stability of your hardware in running ESXi, etc.—is up to you. Obviously, you can't take your Dell into an Apple Store and expect support. VMWare sort of does support you, though, insofar as it's the free-tier support (you can get better if you pay for VSphere), and insofar as whatever problem you're facing is a problem with ESXi—or a problem in your hardware's ESXi compatibility—instead of a problem in how ESXi handles macOS guests. But, as I said above, the latter is Apple's problem to worry about; such bugs get fixed, to support the people who are virtualizing macOS on Apple hardware. > the fact that ESXi won't do it unless modified Not actually true! ESXi won't create a macOS guest without hacks. It's perfectly happy, however, to import a macOS VM created using VMWare Fusion. There's even a quick menu-action to upload VMs directly from Fusion into ESXi. > Except the license agreements (both Apple and VMWare) A license agreement doesn't stop you from doing anything. It doesn't have hands to restrain you from typing the commands that will install macOS. You stop yourself, because of a license agreement. Or you don't. Up to you, really. It's not like either Apple or VMWare is going to stop selling you their products, let alone sue you, for what you do with their software on your own computer. (Now, if you're an employee of a company, then the licence agreement might indeed have "hands" to stop you with: the hands of the lawyers of the company, enforcing the company's agreement with VMware/Apple. This is why https://macminicolo.net/ https://macminicolo.net/ exists, instead of just being an ESXi farm.)
- saosebastiao 10y agoI'd love to run macOS on my NUC with 32 gigs of ram for iOS development instead of buying a shitty Mac mini. This sounds pretty awesome but I only understand a fraction of what you're talking about. Is there some kind of tutorial for setting this up?
- derefr 10y agoNot that I know of. I mostly pieced the process together from disparate sources. Let me try to give you a brain-dump: First, a point of note: one funny thing is that the VSphere ecosystem assumes, is that the ops people deploying VSphere use Windows. So the tooling around VSphere—even the unofficial community tooling—are Windows programs. Besides the server computer I was setting up, I only have a MBP (with no Boot Camp partition), so, "step zero": I installed VMWare Fusion, and downloaded a Windows evaluation guest image from Microsoft. The rest of this assumes you have Windows: 1. Install http://www.v-front.de/p/esxi-customizer-ps.html http://www.v-front.de/p/esxi-customizer-ps.html, and use it to generate an ESXi ISO customized for your machine. (Add network-card and storage drivers, essentially.) The generated ISO doesn't "burn" onto a USB correctly using regular tools for some reason. The recommended Windows tool is called Rufus. I couldn't use that from a VM without a lot of hassle, but it turns out the ISO is essentially an ISO9660 export of what was a FAT filesystem, including UEFI boot files. So: 2. Extract the ISO onto a FAT-formatted USB stick. Plug it into the new machine, and pick the UEFI file in your BIOS boot manager. The installation proceeds a lot like an ncurses Linux install (e.g. Ubuntu Server.) 3. Once the machine is running, it shows a URL you can reach its web client interface at. For managing the hypervisor, this is mostly fine. (You can also enable SSH from this web console, and then SSH into the hypervisor.) For setting up new VMs, however, I found the [free] VSphere Client (https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2089791 https://kb.vmware.com/selfservice/microsites/search.do?langu...) a lot more powerful. Install that if you like. Again, though, it's Windows-only. 4. Create a macOS VM in VMWare Fusion. (It assists you in doing this; it just requires that you have a recovery partition on your Mac.) 5. Find the menu option in VMWare Fusion to "Connect to an ESXi server"; specify the IP the server console provides, and the admin user/password you provided during installation. 6. Go to the VM library window, right-click the macOS VM, and one of the options should be "Upload to an ESXi server". You can then pick one of your connected servers. --- One thing VMWare wants you to do, that you shouldn't do (for a home lab, at least), is to install their Platform Management Controller, "VSphere VCenter." (You might be tempted, because that's the only way to get their modern [horribly-janky] web-app interface that exposes all the VM configuration options like the Windows client does.) The VCenter VM appliance is ridiculously bulky: it takes ~16GB of RAM and two dedicated vCPUs just to run it. It's designed to consume one whole ESXi host node of a VSphere cluster, not to assist in the maintenance of a single-node ESXi setup.