Description of problem:
Fedora CoreOS operates in a different manner than traditional Red Hat based distros, this is most prevalent when ignition is involved.
Presently virt-install has a lot of direct support for other Red Hat-isms like the stage2 image. While we shouldn't need this with Fedora CoreOS there are other optimizations which may be possible like presenting the firmware mechanisms needed to provide configuration of the host:
From the Fedora CoreOS side this is also being tracked in https://github.com/coreos/fedora-coreos-tracker/issues/221
I think the main thing here is some kind of ignition config support, like have with virt-install --cloud-init upstream. That could eventually make its way to the UI.
If coreos provides a .treeinfo file then URL and OS detection can work nicely.
But yes there's probably a variety of things to consider here like described in the github issue
We are closing down this tracker for upstream virt-manager bugs. I've moved this issue to the upstream github tracker here: https://github.com/virt-manager/virt-manager/issues/152