Test Day:2012-11-01 Virtualization: Difference between revisions

Latest revision as of 19:42, 26 June 2015

Fedora Test Days

Virtualization Test Day

Date	2012-11-01
Time	all day

Website	Virtualization
IRC	#fedora-test-day (webirc IRC logs)
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 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 18. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 18.

Who's available[edit]

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

Daniel Berrange (danpb)
Richard W.M. Jones (rwmjones)
Cole Robinson (crobinso)
Stefan Hajnoczi (stefanha)
Miroslav Rezanina (mrezanin)
Eric Blake (eblake)
Laine Stump (laine)

Known issues[edit]

Before you begin testing, there are a few known bugs that should be taken into account:

Pausing a KVM guest can crash that guest. Might be specific to guests using a QXL video device (the default created by virt-manager): bug 870811
running libvirtd inside a guest can break that guests networking. you can work around this by using 'sudo virsh net-edit default' inside the VM, and change all instances of 192.168.122 to 192.168.123 and restarting the VM: bug 811967
qemu + libvirt + seccomp doesn't work, the qemu guests fail to even start: bug 855162
some graphical corruption if using cirrus virtual card for guests: bug 871247
virt-manager will backtrace trying to show guests in the 'suspended' state bug 871237
Closing a graphical window triggers a guest resume bug 871240
ctrl-alt-f2,3,4 don't have effect in guests (unless xserver is restarted): bug 871241

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?). If unavailable, you can still help with testing QEMU support.
Up to 10-20Gb free disk space. Guest images take up a lot of space.
Get the packages with
```
yum groupinstall virtualization
```

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

Fedora 18 on a physical machine[edit]

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

Install with CD/DVD.
- Latest live CD builds ('desktop' is the default): http://alt.fedoraproject.org/pub/alt/nightly-composes/
- Latest 64 Bit DVD: http://dl.fedoraproject.org/pub/alt/stage/18-Beta-TC6/Fedora/x86_64/iso/

Upgrade from Fedora 17
- The supported way is using CD/DVD upgrade. See media links above
- Update using 'yum': https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum
  This method is not supported, but is very commonly used by developers. If you're a power user this is a possible option!

Fedora 18 virt packages on Fedora 17[edit]

If you aren't ready to make the jump to Fedora 18, this is the next best thing! Run latest virt packages on Fedora 17 from the virt-preview repo:

http://fedoraproject.org/wiki/Virtualization_Preview_Repository

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

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

Install the latest virt packages from virt-preview using the instructions above.
Install a Fedora 18 guest using one of the test cases below.
Use virt-manager to 'copy host CPU' for your VM. Boot the VM, install virtualization packages, and verify that nested virt is working by running the following command as root:
```
virt-host-validate
```

Some notes on nested virt with AMD and Intel:

Areas to test[edit]

VM Install[edit]

Record your results for these test cases in the Test Results section.

If you don't already have a VM available, run through one of these test cases. A fully functioning VM is required for every other test case!

Next give this a run through, which should ensure things aren't broken in some obvious manner:

VM Lifecycle (start, stop, save, delete, ...)

New tests and features[edit]

Record your results for these test cases in the Test Results section.

libguestfs and tools[edit]

You will need Fedora 18 (host) and at least one guest (but the more the merrier).

Install libguestfs:

# yum install '*guestf*'

and run through the tests here: http://libguestfs.org/guestfs-testing.1.html

In Fedora 18, we are using libvirt to launch the appliance, and sVirt + SELinux to make everything much more secure. Therefore it's better (though not required) if you can run these tests with SELinux set to enforcing.

Previous test cases[edit]

Some test cases used in previous test days. Still useful to test for regressions!

Migration:

Hotplug:

virtio-scsi:

Test Results[edit]

Each tester should add a row for their results.

If you have problems with any of the tests, report a bug to Bugzilla. If you have any questions about what component to file against, just shout in the IRC channel and we can help you out. Same goes for any selinux alerts you might see!

User	VM Install	VM Lifecycle	Live Backup	Suspend	Seccomp	IO Throttling	PV EOI	USB3	USB Redir	References
crobinso	pass	pass	pass	pass	fail ^[1]	pass	pass	warn ^[2]	done	↑ Guest fails to start RHBZ #855162 ↑ USB Device didn't appear in lsusb -t in guest
Kashyap Chamarthy	pass	pass	pass	none	none	none	none	none	none
mkrizek	pass	pass	pass	pass	none	pass	pass ^[1]	none	pass	↑ Reduced only from approx. 15.000 to 12.000
mrezanin	pass	pass	pass	pass	none	pass	none	none	pass
pschindl	warn ^[1]	fail ^[2]		pass ^[3]						↑ RHBZ #872162 ↑ RHBZ #869607 ↑ I tested only guest functionality, when I try agent I got 'Error starting domain: Unable to read from monitor: Connection reset by peer'
Stefan Hajnoczi	pass	none	none	none	none	pass ^{[long 1]}	none	none	none
Eric Blake	inprogress	inprogress	inprogress ^[1]	inprogress	inprogress	inprogress	inprogress	inprogress	inprogress	↑ RHBZ #872292 found by inspection based on an IRC question, latent bug which affects snapshots, among other operations
Arun S A G	pass	pass	none	pass ^[1]	none	none	none	none	none	↑ RHBZ #872343 Cannot resume RHEL6 vm running at runlevel 3
kparal	pass	pass	pass	fail ^[1]	none	fail ^[2]	none	none	none	↑ RHBZ #872573 ↑ RHBZ #872582
Karen Noel	pass ^[1]	inprogress	none	none	none	none	none	none	none	↑ Installed RHEL6.3 and F18 guests

Long comments[edit]

↑ Throttling works but virsh blkdeviotune reports incorrect results. I have sent patches here: https://www.redhat.com/archives/libvir-list/2012-November/msg00095.html RHBZ #872582

[1] Guest fails to start RHBZ #855162

[2] USB Device didn't appear in lsusb -t in guest

[3] Reduced only from approx. 15.000 to 12.000

[bz872162-4] RHBZ #872162

[bz869607-5] RHBZ #869607

[6] I tested only guest functionality, when I try agent I got 'Error starting domain: Unable to read from monitor: Connection reset by peer'

[8] RHBZ #872292 found by inspection based on an IRC question, latent bug which affects snapshots, among other operations

[9] RHBZ #872343 Cannot resume RHEL6 vm running at runlevel 3

[bz872573-10] RHBZ #872573

[bz872582-11] RHBZ #872582

[12] Installed RHEL6.3 and F18 guests

[7] Throttling works but virsh blkdeviotune reports incorrect results. I have sent patches here: https://www.redhat.com/archives/libvir-list/2012-November/msg00095.html RHBZ #872582

[1]

[2]

[1]

[1]

[2]

[3]

[long 1]

[1]

[1]

[1]

[2]

[1]

Search