The first test is to try to inspect the ISO media and see if libguestfs can identify the operating system. Use the 'virt-inspector' command todo this

+

The first test is to try to inspect the ISO media and see if libosinfo can identify the operating system. Use the 'osinfo-detect' command todo this

−

# virt-inspector /path/to/iso/image

+

# osinfo-detect /path/to/iso/image

−

'''This test shall be considered successful if the above commands outputs an XML document containing an <operatingsystem> element and the following child elements'''

+

'''This test shall be considered successful if the above commands outputs the name of the operating system on the media'''

−

- <name>

+

If this fails, file a bug report against the libosinfo component, providing the output of the following command as an attachment to the bug

−

- <distro>

−

- <arch>

−

- <major_version> + <minor_version>

−

- <format>installer</installer>

−

−

If any of this data is missing, file a bug report against the libguestfs component, providing details of the ISO image you used

+

# isoinfo -d -i /path/to/iso/image

For example a successful invocation on a Fedora 16 DVD looks like this:

For example a successful invocation on a Fedora 16 DVD looks like this:

# cd /var/lib/libvirt/images

# cd /var/lib/libvirt/images

−

# virt-inspector $OSNAME.iso

+

# osinfo-detect $OSNAME.iso

−

<?xml version="1.0"?>

+

Media is bootable.

−

<operatingsystems>

+

Media is an installer for OS 'Fedora 16'

−

<operatingsystem>

−

<root>/dev/sda</root>

−

<name>linux</name>

−

<arch>i386</arch>

−

<distro>fedora</distro>

−

<major_version>116</major_version>

−

<minor_version>0</minor_version>

−

<package_format>rpm</package_format>

−

<package_management>yum</package_management>

−

<format>installer</format>

−

<multipart/>

−

<mountpoints>

−

<mountpoint dev="/dev/sda">/</mountpoint>

−

</mountpoints>

−

<filesystems>

−

<filesystem dev="/dev/sda">

−

<type>iso9660</type>

−

<label>Fedora 16 i386 DVD</label>

−

</filesystem>

−

</filesystems>

−

<applications/>

−

</operatingsystem>

−

</operatingsystems>

Even if this test fails, you can still proceed with the other three tests.

Even if this test fails, you can still proceed with the other three tests.

Line 127:

Line 99:

# virt-install --hvm --noreboot --ram 800 --vnc --name $OSNAME \

# virt-install --hvm --noreboot --ram 800 --vnc --name $OSNAME \

--network network=default \

--network network=default \

−

--disk path=/var/lib/libvirt/images/$OSNAME.qcow2,size=10 \

+

--disk path=/var/lib/libvirt/images/$OSNAME.raw,size=10 \

--cdrom /var/lib/libvirt/images/$OSNAME.iso

--cdrom /var/lib/libvirt/images/$OSNAME.iso

Latest revision as of 09:18, 12 April 2012

Fedora 17 will ship with KVM as the default hypervisor, based on the QEMU 1.0 release. The test day will focus on determining what guest operating systems can be successfully installed and run post-install. It will also check whether libguestfs can inspect the initial install media and resulting disl image.

To install the guest operating system, we will use the command line virt-install tool. Feel free to use virt-manager instead, but be aware that you'll have less opportunity to tune things for rarer operating systems. For testing the basic configuration that is desired is

10 GB qcow2 disk

1 NIC connected to 'default' network (virbr0)

Serial console

800 MB RAM (feel free to raise if the OS is known to need more)

Assuming the $OSNAME env variable is still set from earlier, the following command can be used:

See the virt-install(1) manual page for the full list of supported OS types.

When virt-install launches the guest, a virt-viewer window should appear allowing interaction with the guest OS. Run through the guest OS installer process.

This test shall be considered successful if the guest installation process completes without error, and the guest OS then shuts down.

Bad behaviour requiring bug reports include

Installer kernel/OS hang

Unsupported disk or NIC interface

Disk / network I/O problems / errors

Essentially anything unusual as compared to installing the guest on bare metal.

Some OS may not support the default NIC or disk hardware. There are options for the --network and/or --disk options to virt-install to change the hardware, for example to switch from IDE to SCSI disks, or from e1000 to rtl8139 NICs.

File bugs against the 'virt-install' component if there was no '--os-variant' and the guest required custom hardware to successfully install. File bugs against 'qemu' in the event of any hangs/crashes/other wierd behaviour

For problems installing or booting guests, use the component 'qemu'. For problems inspecting the installation ISOs or disk images, use the component 'libguestfs'. Don't worry too much about getting the component perfect - the maintainers will re-assign bugs if the component is wrong.