From Fedora Project Wiki

Fedora Test Days
Virtualization Test Day

Date 2024-10-11 to 2024-10-13
Time all day

Website Virtualization
IRC #fedora-test-day
Mailing list virt
Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule [on Fedocal] and see if a similar but more recent Test Day is planned or has already happened.

What to test?[edit]

Today's installment of Fedora Test Day will focus on Virtualization in Fedora 41. We will be interested covering the regular virt-install, KVM, Boxes, Vbox.

Who's available[edit]

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion.

What's needed to test[edit]

For starters, your physical machine should have:

  • Hardware virtualization support (e.g. Intel VT or AMD-V) (see Is My Guest Using KVM?).
  • Up to 10-20Gb free disk space. Guest images take up a lot of space.
  • Get the packages with: dnf groupinstall virtualization

As for getting the latest virt packages, you have a few options:

Fedora 41 on a physical machine[edit]

The preferred testing platform is a fully updated Fedora 41 machine. You have a few options for getting the Fedora 41 bits:

Install with CD/DVD[edit]

You can download the latest Fedora 41 composes here:

Run Fedora 40 in a VM with nested virtualization[edit]

Do you have a new machine with a ton of ram and storage space, running Fedora 39/40? Nested virt might be an option! This allows you to create KVM guests inside a Fedora 40 VM.

Run the tests[edit]

Visit the result page and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for the test.

Reporting bugs[edit]

If you have problems with any of the tests, have a look in the results page.

If you don't see it, please file a new bug to Bugzilla. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC #fedora-test-day or #fedora-qa and we will help you.

Test Results[edit]

KVM Install[edit]

User Profile Current KVM install Previous KVM install Guest Install Via URL Import VM References
apologia QEMU/KVM (VMM 4.1.0)
Pass pass
[1]
  1. Success on Expected Results.
apologia QEMU/KVM (VMM 4.1.0) Fedora-KDE-Live-x86_64-41_Beta-1.2.iso
Pass pass
[1]
  1. 1. Success on Expected Results.
apologia QEMU/KVM (VMM 4.1.0) Fedora-Workstation-Live-x86_64-41_Beta-1.2.iso
Pass pass
[1]
  1. 1. Success on Expected Results.
geraldosimiao F41 KDE gest at F41 host Acer Aspire V3-571 / i7-3632QM
Pass pass

Boxes Install[edit]

User Profile Current Boxes Install References
markr217 boxes install
Pass pass
[1]
  1. Install successful, updated after, functionality stable, no problems encountered.

Virtual Box[edit]

User Profile Install Shared Clipboard References

Standard Features[edit]

User Profile VM Lifecycle VM Sanpshots Change VM CDROM Host USB Hotplug Nested virt References
geraldosimiao F41 KDE gest at F41 host Acer Aspire V3-571 / i7-3632QM
Pass pass
Pass pass
joka63 Silverblue with boxes and virt-manager as layered packages. Guest: Debian-12, Fedora Silverblue 40
Fail fail
[1]
  1. RHBZ #2318414 Cloned VM may not start because hard disc device configuration is not copied properly.
joka63 Silverblue with boxes and virt-manager as layered packages. Guests: Debian-12, CentOS 6, Devices: USB Stick, Prolific PL2303 USB to serial adaptor
Warning warn
[1]
  1. RHBZ #2318409 USB hotplug for USB(-2) sticks works fine Connecting Prolific PL2303 USB to serial adaptor to CentOS6 guest requires: - Add Silverblue host user to group dialout - Set SELinux to Permissive to make it working. I have not found any SELinux logs related to the serial adator problem in the audit.log (auditd is running)