Username | Profile | AppleHV | AWS | GCP | Virtual install | Bare Metal install | Raspberry Pi 4 | Comments |
---|---|---|---|---|---|---|---|---|
Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | |||
aaradhak | FCOS next on APPLE HV | [1] |
1.
I was able to successfully install Fedora CoreOS on AppleHV using the next image apple hv
|
|||||
adriend | Raspberry Pi 4 - 2Gb | [1] |
1.
All is okay
|
|||||
marmijo | Raspberry Pi 4 - 8GB | [1] |
1.
fedora-coreos-42.20250316.1.0-metal.aarch64.raw
U-Boot method via SD card
|
|||||
tvannahl | MacBook M3 Pro / vfkit 0.6.1 | [1] |
1.
Ignition failed https://github.com/coreos/fedora-coreos-tracker/issues/1909
|
Username | Profile | Virtual install | Bare Metal install | IBM Cloud | Comments |
---|---|---|---|---|---|
Enter result | Enter result | Enter result | |||
mtarsel | [1] |
1.
A qcow2 fcos image on Power10 with KVM/QEMU booted successfully.
|
|||
tle | RaptorCS Blackbird with IBM POWER9 8core running Fedora 42 with Virtual Machine Manager / QEMU | [1] |
1.
The qcow2 image could not boot up inside Virtual Machine Manager app (qemu-ppc64)
It hangs right after the `Booting Linux via __start() @ 0x0000000000440000 ...` prompt
|
Username | Profile | Virtual install | Bare Metal install | IBM Cloud | Comments |
---|---|---|---|---|---|
Enter result | Enter result | Enter result |
Username | Profile | AppleHV | Virtual install | Bare Metal install | Comments |
---|---|---|---|---|---|
Enter result | Enter result | Enter result | |||
argentum-ipsum | fedora-coreos-42.20250410.1.1-qemu.x86_64.qcow2 | [1] |
1.
tested from kinoite with a production configuration
|
||
bittin | gnome-boxes 20250316 | ||||
dtunma | QEMU, fedora-coreos-42.20250316.1.0-qemu.x86_64.qcow2 image | ||||
ersen | fedora-coreos-42.20250316.1.0-qemu.x86_64.qcow2 | ||||
hricky | fedora-coreos-42.20250316.1.0-qemu.x86_64.qcow2 | ||||
pnemade | fedora-coreos-42.20250316.1.0 qemu image | ||||
ravanelli | Mac Pro, Intel Core i5 | [1] |
1.
Intel Core i5, vfkit starts the boot, but it never ends, not logs are provided.
|
||
tvannahl | Bare metal | ||||
whelanh | QEMU virtual install following the instructions (my host system is Fedora Rawhide) | [1] |
1.
I followed the instructions and was able to successfully log into the QEMU virtual machine using ssh -p 2222 core@localhost. I did not provision disk space, so there was only a limited amount of
exploration I could do on the virtual system except explore the file system. cat /etc/os-release gave a full description of the CoreOS system.
|
Username | Profile | Alibaba | AWS | Azure | DigitalOcean | Exoscale | GCP | Hyper-v | IBM Cloud | Kubevirt | Nutanix | OpenStack | VirtualBox | VMWare | Vultr | Comments |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | |||
c4rt0 | fedora-coreos-42.20250316.1.0-digitalocean.x86_64.qcow2.gz | [1] |
1.
2 GB Memory / 60 GB Disk / SFO2 - Unknown OS my-fcos-image
|
|||||||||||||
dustymabe | fedora-coreos-42.20250316.1.0-ibmcloud.x86_64.qcow2 on IBMCloud bx2-2x8 | [1] |
1.
Needed docs update: https://github.com/coreos/fedora-coreos-docs/pull/716
|
|||||||||||||
fifofonix | [1] | [2] |
1.
We deploy a number of AWS `next` nodes automatically daily in our dev environment: singleton canary nodes, kubernetes auto-scaling group nodes. All are succeeding.
2. We deploy a number of VMWareCloud (VMC) (on AWS) and on-premises vSphere `next` nodes automatically daily in our dev environment: singleton canary nodes and kubernetes auto-scaling group nodes. All are succeeding. |
|||||||||||||
jtognazzi | [1] |
1.
Worked as expected also with Secure Boot enabled !
|
||||||||||||||
marmijo | fedora-coreos-42.20250316.1.0-azure.x86_64.vhd | [1] |
1.
Standard DS1 v2 (1 vcpu, 3.5 GiB memory), us-east region
|
|||||||||||||
ryencoke | fedora-coreos-42.20250316.1.0-openstack.x86_64.qcow2 | [1] |
1.
successful using custom ignition file
|
Username | Profile | Static networking | Complex partitioning | Building containers | Containerized service | Kernel Tuning (sysctl) | Modifying Kernel Arguments | OS extensions | Comments |
---|---|---|---|---|---|---|---|---|---|
Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | |||
Nemric | Live Fedora CoreOS 42.20250316.1.0 | [1] |
1.
Build from a containerized jenkins-agent that drives host's podman via its socket
|
||||||
hricky | fedora-coreos-42.20250316.1.0-qemu.x86_64.qcow2 | ||||||||
jtognazzi | Hyper-V fedora-coreos-42.20250316.1.0-hyperv.x86_64.vhdx | ||||||||
marmijo | fedora-coreos-42.20250316.1.0-qemu.x86_64.qcow2 | ||||||||
tvannahl | quay.io/coreos/coreos-installer to Bare metal | [1] |
1.
1. Left pulling of the image to the coreos-installer
2. created two additional partitions (one after `root` and one on a second disk)
|
Username | Profile | Configuring SwapOnZRAM | Configuring Time Zone | Debugging with Toolbox | Customizing NIC name | Setting alternatives | Node counting | KDump via Ignition | Nmstate | Comments |
---|---|---|---|---|---|---|---|---|---|---|
Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | Enter result | |||
Nemric | Live Fedora CoreOS 42.20250316.1.0 | [1] |
1.
Did not try to disable it
|
|||||||
dustymabe | fedora-coreos-42.20250316.1.0-ibmcloud.x86_64.qcow2 on IBMCloud bx2-2x8 | [1] |
1.
Passed kdump test case.
|
|||||||
hricky | fedora-coreos-42.20250316.1.0-qemu.x86_64.qcow2 |
Username | Profile | Switch stream | Bootloader updates | Comments |
---|---|---|---|---|
Enter result | Enter result | |||
alciregi | KVM | |||
tvannahl | Bare metal | [1] |
1.
#1904,
Failed due to git
|
Username | Profile | All Tests - Add the ones you did | Comments |
---|---|---|---|
Enter result |
Username | Profile | Documentation | Exploratory testing | Comments |
---|---|---|---|---|
Enter result | Enter result | |||
Nemric | Live Fedora CoreOS 42.20250316.1.0 | [1] |
1.
Run live k8s node with cri-o installed "on the fly" and configs pushed via ignition with a containerized kubelet
|