Hello, I am trying to provision Fedora CoreOS on MacOS (version 13.5.1) and VMware Fusion Pro (version 13.0.2) with an ignition file. The Fedora guideline for provisioning FCOS on VMware instructs to use an OVA image, but this is only available for x86_64 architecture, not for aarch64 in the download site.
The FCOS aarch64 ISO image runs fine in Fusion Pro, but I see no way to use an ignition file here.
Is there a way to provision FCOS on MacOS with VMware Fusion Pro using an ignition file?
Any help would be greaty appreciated.
Best wishes,
Martin
Hi, I stumbled upon the same issue and I’m a bit confused. Is it even possible to boot FCOS via VMware Fusion on macOS? Obviously there is no OVA for aarch64, so following VMware provisioning guideline does not really make sense.
I decided to make a bold (or dumb) move and mix up two provisioning approaches. I downloaded Bare Metal FCOS Live DVD ISO and tried to provision it on a VMware Fusion. I can boot it but unless I’m doing something wrong, I can’t proceed with configuration with Ignition. I have prepared basic ignition file and I launched local HTTP server to store it there. Once I tried to install it with this command: sudo coreos-installer install /dev/sda --ignition-url http://localhost:8000/my-file.ign (according to guideline for bare metal installation), I got en error that path /dev/sde does not exists.
This is where I get stuck.
I saw it’s mentioned that this path might be different depending on hardware, but I can’t find path /dev/nvme neither.
What’s even worse, I can’t play around with ovftool to try to set it up, because for whatever reason I can’t download it from official web page Open Virtualization Format (OVF) Tool.
I’d like to find out if FCOS provisioning is possible on VMware Fusion on macOS, or should I seek a different way of using this OS?
The virtual hardware on Fusion VMs on Apple Silicon presents its hard drives as NVMe drives. The path for the primary hard disk for Linux VMs is /dev/nvme0n1, not /dev/sda or /dev/nvme.
I just booted the FCOS ISO in a Fusion VM and it was able to install FCOS to the hard drive using /dev/nvme0n1 as the hard drive path. Give that a try with your custom ignition file.
If you’re booted into the Live ISO then you can look at the system and see what disks are available (i.e. run lsblk). Then you can use that info to determine what disk to pass to coreos-installer.
Thank you, I’ll make a note of that. Would it be possible to provide aarch64 OVA for VMware? No sure if the issue was created as per Timothée’s request to OP.