2013-10-08 Virtualization

Fedora Test Days

Virtualization Test Day

Date	2013-10-08
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?

Today's installment of Fedora Test Day will focus on Virtualization in Fedora 20. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 20.

Who's available

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

Cole Robinson (crobinso)
Eric Blake (eblake on IRC)
Kashyap Chamarthy (kashyap on IRC)
Alexander Todorov (atodorov on IRC)

Known issues

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

libvirt managed save occasionally fails with 'unexpected migration status in setup': https://bugzilla.redhat.com/show_bug.cgi?id=1015636
virt-manager doesn't correctly report 'current' VM CPUs: https://bugzilla.redhat.com/show_bug.cgi?id=1016318
Selinux denial on the host when enabling multiqueue nic in the guest: https://bugzilla.redhat.com/show_bug.cgi?id=1016326
'groupinstall virtualization' needs additional 'yum install libvirt-daemon-config-network': https://bugzilla.redhat.com/show_bug.cgi?id=1016606
virt-manager fails creating /root/.cache/virt-manager, if you hit issues create that director manually: https://bugzilla.redhat.com/show_bug.cgi?id=1016435
libvirt generates conflicting pci address when adding qxl device: https://bugzilla.redhat.com/show_bug.cgi?id=1016775

What's needed to test

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: yum groupinstall virtualization

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

Virt Test Day Live CD

There's a Fedora 20 live CD image that already has all the required virtualization packages installed (though you should still yum update after booting). You will probably want a good amount of RAM if using this option (greater than 4G) since you'll be using RAM for both a VM and running the live OS.

Get the image: wget -c http://fedorapeople.org/groups/virt/virt-testday-2013-10-08.iso
For Live CD or USB setup instructions, see: FedoraLiveCD#Download_and_Create_Live_image_or_Live_USB
If you have a really beefy machine, you can probably run the Live CD in a VM using nested virtualization! (see instructions below)
After booting the livecd, make sure to do a yum update to get all the latest packages

Fedora 20 on a physical machine

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

Install with CD/DVD

You can download the Fedora 20 Alpha in various formats here.

Upgrade from Fedora 19

The supported way is using 'fedup': FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F You may also find the instructions in the fedup test case useful for using fedup to upgrade to a pre-release.
Upgrade using 'yum': This method is not officially supported, but is very commonly used by developers. If you're a power user this is a possible option!

Run Fedora 20 in a VM with nested virtualization

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

Use the virt-preview instructions below, install a guest using one of the install test cases, and follow the nested virt test case to finish the setup and verify things are working correctly.

Fedora 20 virt packages on Fedora 19

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

http://fedoraproject.org/wiki/Virtualization_Preview_Repository

Areas to test

All these tests have an entry in the Test Results table, please record them there.

VM Install

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!

Standard features

These are recurring tests of standard virt features, they ensure nothing obvious is broken.

New features

New or improved features in Fedora 20:

Extra tests

These tests aren't listed in the 'test results' table, but consider giving them a spin and reporting any issues on IRC or bugzilla.

OpenVZ

libguestfs and tools

You will need Fedora 20 (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

Previous test cases

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

Fedora 19 features:

Fedora 18 features:

Misc tests:

All tests:

Complete list of previous tests

Debugging

https://fedoraproject.org/wiki/How_to_debug_Libvirt_problems

Test Results

VM Install

User	Hardware	Guest Install via CDROM	Guest Install via url	PXE Install	Import VM	References
mrezanin	HP Z400		pass
Skip_Wyatt	Dell PowerEdge 2950	pass ^[1]				↑ Using Fedora20 Alpha, guest install passes. No Errors.
Jorge_Fabregas	Dell_Optiplex_790 (F19 with Preview Repo)	pass	fail ^[1] ^{[long 1]}		pass	↑ RHBZ #873468
atodorov	IBM LS22 Blade		fail ^[1] ^[2] fail ^[3] ^[4]			↑ RHBZ #1016449 ↑ worked around the previous bug to find another one ↑ RHBZ #1016435 ↑ virt-manager fails to start so I can't do pretty much anything. This is with a latest snapshot, will try downgrading to a TC release.
atodorov	IBM LS22 Blade qemu-kvm-1.6.0-9.fc20.x86_64 libvirt-daemon-kvm-1.1.3-2.fc20.x86_64	pass ^[1]	pass ^[2]			↑ Using 20-Beta-TC1 ISO with virt-manager wizard ↑ Tested with 20-Beta-TC1 anbd virt-manager wizard. worked fine this time.
hhuang	Lenovo T500		pass ^[1]			↑ F20 Alpha guest install via URL via virt-manager worked as expected.
dustymabe	Nested Virt - F19(L0) F20(L1) F20(L2)	pass ^{[long 2]}		pass ^[1] ^{[long 3]}		↑ RHBZ #1016715
bsd	Dell Poweredge M620			pass ^[1]	pass ^[2]	↑ Setup a bridge and installed FC 19 as guest with no problems ↑ Imported a FC20 guest image with no problems in virt-manager
zbyszek	ASUSTeK COMPUTER INC. Z9PE-D16 Series		fail ^[1] fail ^[2] ^[3] ^[4] fail ^[2] ^[5] ^[6]			↑ (I though I can replace, not append. The first three lines should be discarded.) ↑ ^2.0 ^2.1 RHBZ #1017419 ↑ RHBZ #1017428 ↑ Hangs in dracut, #1017428. ↑ RHBZ #1016449 ↑ Hangs in dracut, either #1016449 or something similar.
Tadej	HP EliteBook 8530p	pass ^[1] ^[2]	fail ^[3] ^{[long 4]}			↑ RHBZ #1016657 ↑ The install via virt-manager's 'New VM' wizard was smooth, apart from the issue described in the bug report. ↑ RHBZ #1016606
rhn-support-jrodrigu	Lenovo T430s	pass

Standard Features

User	Hardware	VM Lifecycle	VM Serial console login	Host USB device hotplug	Nested Virt	Host PCI device assignment	Change CDROM media for running VM	Spice features	References
mrezanin	HP Z400	pass	pass ^[1] ^[2]	fail ^[3]	pass		pass ^[4]		↑ RHBZ #1016445 ↑ Problems with combining virt-manager and virsh access to console. ↑ RHBZ #1016511 ↑ BZ 967914 not reproduced
Jorge_Fabregas	Dell_Optiplex_790 (F19 with Preview Repo)	warn ^{[long 5]} pass	pass ^{[long 6]} warn ^{[long 7]} warn ^{[long 8]}				pass
atodorov	IBM LS22 Blade qemu-kvm-1.6.0-9.fc20.x86_64 libvirt-daemon-kvm-1.1.3-2.fc20.x86_64	pass ^[1]	fail ^[2] ^[3]						↑ RHBZ #1015636 ↑ RHBZ #1016488 ↑ Installed 20-Beta-TC1 from DVD ISO, GUI works fine, serial not.
dustymabe	Nested Virt - F19(L0) F20(L1) F20(L2)		pass ^{[long 9]}
bsd	Dell Poweredge M620		warn ^[1]		pass ^[2] fail ^{[long 10]}	warn ^[3] pass ^[4]		pass ^[5]	↑ Exact behavior as Jorge_Fabregas mentioned in his comments ↑ Failed the first time - testcase didn't mentione "nested=1" to kvm_intel ↑ For VFIO, after adding <driver name='vfio' /> to the config, I couldn't run the guest at all. I am guessing it's a syntax issue. ↑ I tested with a Intel 82599 controller. Normal Device Assignment works as expected. ↑ Satisfies everything mentioned in the test case
zbyszek	ASUSTeK COMPUTER INC. Z9PE-D16 Series	fail ^[1]	fail ^[2] ^[3]						↑ Hangs at shutdown. ↑ RHBZ #1016613 ↑ Works through the graphical interface, but not through 'virsh console'.
Tadej	HP EliteBook 8530p	pass	warn ^[1] ^{[long 11]}	fail ^[2] ^[3]					↑ RHBZ #1016488 ↑ RHBZ #1016511 ↑ Similar to what mrezanina observed.
rhn-support-jrodrigu	Lenovo T430s	pass ^[1] fail ^{[long 12]}	warn ^{[long 13]} fail ^{[long 14]}	warn ^{[long 15]}	pass ^[2]				↑ In save VM after doing three times it has been successful. ↑ I have had some issue as losing root password and I have had to recover the system. No more issues.

New Features

User	Hardware	Virt ACLs	ARM on x86	Snapshot UI	CPU Hotplug	Mulitiqueue NIC	References
mrezanin	HP Z400		pass	pass	pass	pass
Jorge_Fabregas	Dell_Optiplex_790 (F19 with Preview Repo)			pass	pass	fail ^[1]	↑ Got the SElINUX AVC on the host plus the VM crashed. Did it again and same thing happened.
atodorov	IBM LS22 Blade qemu-kvm-1.6.0-9.fc20.x86_64 libvirt-daemon-kvm-1.1.3-2.fc20.x86_64	pass ^[1] pass	fail ^[2] ^[3]	pass ^[4] pass ^[5]	pass ^[6]	pass ^[7] pass	↑ Fedora 20 Beta TC2 ↑ RHBZ #1016648 ↑ Fedora-Minimal-armhfp-20-Beta-TC2-sda.raw ↑ RHBZ #1016604 ↑ No issues for me. ↑ RHBZ #1016613 ↑ Fedora 20 Beta TC2
bsd	Dell Poweredge M620				pass ^[1]		↑ Followed Testcase - Works as expected
Tadej	HP EliteBook 8530p			pass	fail ^[1]		↑ RHBZ #1017179

Long comments

↑ Encountered the issue described in this bug ("Nothing Selected" in Software Selection). The workaround mentioned solved the issue. After that, I was able to start installation but while I was creating a user the installation aborted (error populatint transaction: failure: ntfsprogs...). Could be network issue.
↑
# F20 iso image was attached to cdrom of L1 guest
1. Following command was run to create and install L2 guest
virt-install --name nest1 --ram 2048 --disk /guests/nest1.img,size=10,bus=scsi --controller=scsi,model=virtio-scsi --accelerate --location /dev/sr0
↑ PXE and network components worked fine (used virt-install --pxe...). Only issue came at the end of install when I had to force reboot the guest. This may be a result of my odd nested virt setup.
↑ After working around the first bug, I didn't manage to install via URL due to mirror problems (a needed several retries to get the initial image, later anaconda failed in the middle of install due to a missing rpm package).
↑ After installing Fedora-20-Beta-TC2-x86_64-DVD.iso, I can't see the mouse pointer on the Desktop (this VM was installed with virt-install ...--os-variant fedora20)
↑ Found out that once you open the console thru virt-manager...no matter if you close the viewer window you can't use the virsh line. You have to close virt-manager completely in order to use virsh console...
↑ It worked thru virt-manager. With "virsh console test-day-vm" I received: Connected to domain test-day-vm Escape character is ^] error: operation failed: Active console session exists for this domain This was using Fedora-20-Beta-TC2-x86_64-DVD.iso
↑ It worked thru virt-manager. With "virsh console test-day-vm" I received: Connected to domain test-day-vm Escape character is ^] error: operation failed: Active console session exists for this domain
↑ Install guest with --os-variant fedora20 and verified guest xml has serial console device and can login using virsh console and virt-manager.
↑ Launched L1 using virt-manager (CPU copy host). Verified that qemu on host has -cpu SandyBridge,+pdpe1gb,+osxsave,+dca,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme. Inside guest, cpuinfo shows SandyBridge but no vmx flags found.
↑ Same thing as observed by atodorov. However, if I manually add the Console Device via "Add Hardware" option, I get a working console in virt-manager. 'virsh console vm-name' still doesn't work though.
↑ Error saving domain: internal error: unexpected migration status in setup Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/engine.py", line 918, in cb vm.save(path, meter=asyncjob.get_meter()) File "/usr/share/virt-manager/virtManager/domain.py", line 1309, in save self._backend.managedSave(0) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 911, in managedSave if ret == -1: raise libvirtError ('virDomainManagedSave() failed', dom=self) libvirtError: internal error: unexpected migration status in setup
↑ Finally I have been able to add a virtio console and it works fine from virt-manager. From command line I have been able to connect but login didn't appear and I haven't been able to login.
↑ My Guest didn't have a virtio console. After add it guest doesn't start and in /var/log/libvirt/qemu/fedora20.log I have: ... Warning: option deprecated, use lost_tick_policy property of kvm-pit instead. char device redirected to /dev/pts/2 (label charserial0) char device redirected to /dev/pts/3 (label charconsole1) Failed to allocate 1073741824 B: Cannot allocate memory 2013-10-09 13:33:50.918+0000: shutting down
↑ I have been able to attach USB pen-drive from my Lenovo to my first Fedora 20 VM. When I try to attach this pen-drive to my nested Fedora 20 nested VM I receive this error: Path '/dev/bus/usb/000/000' is not accessible: No such file or directory Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/addhardware.py", line 1261, in add_device self.vm.attach_device(self._dev) File "/usr/share/virt-manager/virtManager/domain.py", line 851, in attach_device self._backend.attachDevice(devxml) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 429, in attachDevice if ret == -1: raise libvirtError ('virDomainAttachDevice() failed', dom=self) libvirtError: Path '/dev/bus/usb/000/000' is not accessible: No such file or directory It says that it's possible to see the attached pen-drive in next reboot but after rebooting it's no possible to see it.

[1] Using Fedora20 Alpha, guest install passes. No Errors.

[bz873468-2] RHBZ #873468

[bz1016449-4] RHBZ #1016449

[5] worked around the previous bug to find another one

[bz1016435-6] RHBZ #1016435

[7] virt-manager fails to start so I can't do pretty much anything. This is with a latest snapshot, will try downgrading to a TC release.

[8] Using 20-Beta-TC1 ISO with virt-manager wizard

[9] Tested with 20-Beta-TC1 anbd virt-manager wizard. worked fine this time.

[10] F20 Alpha guest install via URL via virt-manager worked as expected.

[bz1016715-12] RHBZ #1016715

[14] Setup a bridge and installed FC 19 as guest with no problems

[15] Imported a FC20 guest image with no problems in virt-manager

[16] (I though I can replace, not append. The first three lines should be discarded.)

[bz1017419-17] 2.0 ^2.1 RHBZ #1017419

[bz1017428-18] RHBZ #1017428

[19] Hangs in dracut, #1017428.

[bz1016449-20] RHBZ #1016449

[21] Hangs in dracut, either #1016449 or something similar.

[bz1016657-22] RHBZ #1016657

[23] The install via virt-manager's 'New VM' wizard was smooth, apart from the issue described in the bug report.

[bz1016606-24] RHBZ #1016606

[bz1016445-26] RHBZ #1016445

[27] Problems with combining virt-manager and virsh access to console.

[bz1016511-28] RHBZ #1016511

[29] BZ 967914 not reproduced

[1]

[1]

[long 1]

[1]

[2]

[3]

[4]

[1]

[2]

[1]

[long 2]

[1]

[long 3]

[1]

[2]

[1]

[2]

[3]

[4]

[5]

[6]

[1]

[2]

[3]

[long 4]

[1]

[2]

[3]

[4]

[long 5]

[long 6]

[long 7]

[long 8]

[1]

[2]

[3]

[long 9]

[1]

[2]

[long 10]

[3]

[4]

[5]

[1]

[2]

[3]

[1]

[long 11]

[2]

[3]

[1]

[long 12]

[long 13]

[long 14]

[long 15]

[2]

[1]

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[1]

[1]

Search

Test Day:2013-10-08 Virtualization

Contents

What to test?

Who's available

Known issues

What's needed to test

Virt Test Day Live CD

Fedora 20 on a physical machine

Install with CD/DVD

Upgrade from Fedora 19

Run Fedora 20 in a VM with nested virtualization

Fedora 20 virt packages on Fedora 19

Areas to test

VM Install

Standard features

New features

Extra tests

OpenVZ

libguestfs and tools

Previous test cases

Debugging

Test Results

VM Install

Standard Features

New Features

Long comments