From Fedora Project Wiki

Description

This test case verifies the successful provisioning of Fedora CoreOS (FCOS) on a Hyper-V virtualization environment. The process includes downloading the FCOS image, creating a new VM on Hyper-V, and configuring it to run FCOS. This is taken from the doc[1]. Feel free to raise issue if something doesn't work.

Setup

  1. Ensure Hyper-V is enabled on a Windows machine. Refer to Windows documentation for instructions on enabling Hyper-V.
  2. Download the latest Fedora CoreOS ISO suitable for Hyper-V from the Fedora downloads page.

How to test

  1. Open Hyper-V Manager and select "New" -> "Virtual Machine" to launch the New Virtual Machine Wizard. Click "Next" to proceed.
  2. Specify a name for the virtual machine and choose a location for storing the VM files. Click "Next".
  3. Select "Generation 1" for the VM generation option. This is important because Fedora CoreOS images are currently optimized for Generation 1 VMs. Click "Next".
  4. Assign at least 2048 MB of memory to the VM and check the option to use Dynamic Memory. Click "Next".
  5. Configure networking by connecting the VM to an existing virtual switch on Hyper-V. Click "Next".
  6. On the "Connect Virtual Hard Disk" step, choose to create a new virtual hard disk, specify its name, location, and size (a minimum of 10 GB is recommended). Click "Next".
  7. On the "Installation Options" step, choose to install an operating system from a bootable CD/DVD-ROM. Select "Image file (.iso)" and browse to the Fedora CoreOS ISO downloaded earlier. Click "Next" and then "Finish" to create the VM.
  8. Start the VM and proceed with the Fedora CoreOS installation process. Use the default settings or customize as required by your testing environment.
  9. After installation, configure Fedora CoreOS by logging in and setting up any required services or applications for your test case.

Expected Results

  1. The VM should be successfully created and listed in Hyper-V Manager.
  2. Fedora CoreOS should boot from the ISO without errors, displaying the login prompt post-installation.
  3. The VM should meet Fedora CoreOS's minimum performance and operational requirements, such as network connectivity and the ability to install and run services.

Optional

Optionally, test specific Fedora CoreOS functionalities or applications to further validate the provisioning process on Hyper-V. This can include deploying containerized applications, testing network configurations, or applying updates.