From Fedora Project Wiki

(Copied QA testcase from KVM. Did sed s/KVM/Xen/. Modified the install instructions to refer to PV case (so NFS/HTTP) only)
(add the 'associated criterion' block)
Line 1: Line 1:
{{Template:Associated_release_criterion|releasecriterion=Fedora_{{FedoraVersionNumber|next}}_Final_Release_Criteria#Xen_DomU}}
{{QA/Test_Case
{{QA/Test_Case
|description=A complete installation started from booting in Xen. Get started with Xen virtualization,please see [[Features/XenPvopsDom0]]
|description=A complete installation started from booting in Xen. Get started with Xen virtualization,please see [[Features/XenPvopsDom0]]

Revision as of 23:20, 25 July 2013

Note.png
Associated release criterion
This test case is associated with the Fedora_40_MILESTONE_Release_Criteria#CRITERION_NAME release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.


Description

A complete installation started from booting in Xen. Get started with Xen virtualization,please see Features/XenPvopsDom0

Setup

  1. Prepare a machine with the current development release (Fedora 40) installed
  2. Install Package-x-generic-16.pngvirt-manager (or Package-x-generic-16.pnglibvirt) and Package-x-generic-16.pngxen to control Xen virtual machines)

How to test

  1. Create a virtual machine and boot the current development release in it using the HTTP/NFS install. This can be accomplished using the virt-install command or by using the graphical utility virt-manager. For example:

virt-install -l http://download.fedoraproject.org/pub/fedora/linux/releases/16/Fedora/x86_64 --ram 1024 --disk /dev/vg_guest/guest --name guest

  1. Hit run to boot the guest from the provided HTTP/NFS link
  2. Proceed with normal installation

Expected Results

  1. The installer successfully boots from the HTTP/NFS link
  2. The installer is able to activate and use the virtual network device(s)
  3. The installer is able to activate and use the virtual storage device(s)
  4. The install completes successfully
  5. The system reboots successfully, recognizing filesystems created on the virt device(s)