From Fedora Project Wiki

(Note that some mirrors aren't complete)
 
(13 intermediate revisions by one other user not shown)
Line 8: Line 8:
 
|actions=
 
|actions=
  
=== virt-manager ===
+
=== Test OS detection on the URL ===
 +
 
 +
{{admon/note | Fedora 29 URLs are detected as Fedora 28 }}
 +
 
 +
This will determine if the virt-install/virt-manager can detect an OS from the URL. Feel free to try this with as many different OS install trees that you want, and file a bug against virt-manager if the output doesn't match the expected results.
 +
 
 +
For F29, this looks like
  
{{admon/warning | Mirrors may be incomplete | If you have issues with the links below, use a non-mirrormanager link like http://mirror.pnl.gov/fedora/linux/development/20/x86_64/os/ ||
+
* <code>sudo virt-install --test-media-detection https://kojipkgs.fedoraproject.org/compose/branched/Fedora-29-20180910.n.0/compose/Workstation/x86_64/os/</code>
  
 +
=== virt-manager ===
 
# Run virt-manager (should autoconnect to qemu)
 
# Run virt-manager (should autoconnect to qemu)
 
# Launch the 'New VM' wizard
 
# Launch the 'New VM' wizard
 
# Choose the 'Network install' option
 
# Choose the 'Network install' option
# Enter the following URL for the latest fedora development bits: http://download.fedoraproject.org/pub/fedora/linux/development/20/x86_64/os/
+
# Enter the following URL for the latest fedora development bits: https://kojipkgs.fedoraproject.org/compose/branched/Fedora-29-20180910.n.0/compose/Workstation/x86_64/os/
 
# Press enter when the URL field is active: virt-manager should auto detect the URL as a recent fedora distro
 
# Press enter when the URL field is active: virt-manager should auto detect the URL as a recent fedora distro
 
# Proceed with through the wizard, using the default suggested values. On the final page, use the VM name: test-day-vm
 
# Proceed with through the wizard, using the default suggested values. On the final page, use the VM name: test-day-vm
Line 24: Line 31:
 
An example virt-install invocation looks like
 
An example virt-install invocation looks like
  
  $> virt-install --name test-day-vm --ram 2048 \
+
sudo virt-install --name test-day-vm --ram 2048 --disk size=20 \
        --disk path=/var/lib/libvirt/images/test-day-vm.img,size=10 \
+
          --location https://kojipkgs.fedoraproject.org/compose/branched/Fedora-29-20180910.n.0/compose/Workstation/x86_64/os/
        --location http://download.fedoraproject.org/pub/fedora/linux/development/20/x86_64/os/
 
  
 
|results=
 
|results=

Latest revision as of 17:46, 10 September 2018

Description

Install a Fedora guest from an install tree URL using virt-install or virt-manager.

Setup

Nothing beyond initial test day setup.

How to test

Test OS detection on the URL

Error creating thumbnail: File missing
Fedora 29 URLs are detected as Fedora 28

This will determine if the virt-install/virt-manager can detect an OS from the URL. Feel free to try this with as many different OS install trees that you want, and file a bug against virt-manager if the output doesn't match the expected results.

For F29, this looks like

virt-manager

  1. Run virt-manager (should autoconnect to qemu)
  2. Launch the 'New VM' wizard
  3. Choose the 'Network install' option
  4. Enter the following URL for the latest fedora development bits: https://kojipkgs.fedoraproject.org/compose/branched/Fedora-29-20180910.n.0/compose/Workstation/x86_64/os/
  5. Press enter when the URL field is active: virt-manager should auto detect the URL as a recent fedora distro
  6. Proceed with through the wizard, using the default suggested values. On the final page, use the VM name: test-day-vm
  7. Start the install, and perform the install as you would on a normal machine.

virt-install

An example virt-install invocation looks like

sudo virt-install --name test-day-vm --ram 2048 --disk size=20 \
         --location https://kojipkgs.fedoraproject.org/compose/branched/Fedora-29-20180910.n.0/compose/Workstation/x86_64/os/

Expected Results

Guest installations start and perform without any issues. Guest is bootable after install completes.