Running a Fedora CoreOS physical computer as VM host. Possible? Good/bad idea?

I thought it would be interesting to try out to create a few VM:s of Fedora CoreOS with
virt-install. As VM host I could use a computer (i.e. physical machine)
that currently has an empty HDD so I would first need to install an operating system on that computer.

As VM host operating system, I guess Fedora 32 would be a good choice.
But I was wondering if it would be possible to instead use Fedora CoreOS as the VM host operating system?

Maybe it would be possible to create an Ignition file that automates the installation of the VM host and the virt-install of the FCOS VM:s?

What do you think?
Are there any tricky things that you foresee?

Thanks,
Erik Sjölund

I don’t think you will run into any particular issue with running VMs on Fedora CoreOS. You will probably have to overlay the libvirt and qemu packages as I don’t know how well libvirt work inside of a container.

If you choose to keep auto-updates enabled by default, you should be aware that the VMs will be stopped for the system to reboot. You might want to take a look at setting up maintenance windows with zincati to make this happen only when appropriate for your users.

1 Like

We currently deploy VMs of CoreOS. The way we do it is to use packer to create a VMX from the ISO and then convert that to an OVA using VMware’s ovftool.

@dans Why not use the official Fedora CoreOS VMware OVA image?

Looking back at the code, I was incorrect. We don’t use the ISO. We start with the OVA, but we use packer because we customize the image.

1 Like