Test Day:2015-04-16 Virtualization: Difference between revisions

Latest revision as of 21:43, 19 September 2016

Fedora Test Days

Virtualization Test Day

Date	Thursday 2015-04-16
Time	all day

Website	Virtualization
IRC	#fedora-test-day
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 [on Fedocal] 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 22. Test cases will basic virtualization workflow, some cool functionality, as well as new features introduced in Fedora 22.

Who's available[edit]

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

Cole Robinson (crobinso)
Jeff E. Nelson (jenelson)
Lingfei Kong (lkong)
Hu Zhang (huzhan)
Eric Blake (eblake)
Laine Stump (laine)

Known issues[edit]

ejecting CDROM media from a VM hits 'tray locked' error, but succeeds on the second attempt: http://bugzilla.redhat.com/show_bug.cgi?id=1211761
libvirt has crashed on me a couple times while deleting a running VM: https://bugzilla.redhat.com/show_bug.cgi?id=1211760
libosinfo doesn't have a Fedora 22 option: https://bugzilla.redhat.com/show_bug.cgi?id=1211797
libosinfo's fallback fedora detection doesn't catch fedora server: https://bugzilla.redhat.com/show_bug.cgi?id=1211796
After cloning a VM with virt-manager, the delete VM wizard thinks the new storage doesn't exist: https://bugzilla.redhat.com/show_bug.cgi?id=1211795

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?).
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 22 on a physical machine[edit]

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

Install with CD/DVD[edit]

You can download the latest Fedora 22 Beta composes here:

Upgrade from Fedora 21[edit]

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 22 in a VM with nested virtualization[edit]

Do you have a new machine with a ton of ram and storage space, running Fedora 22? Nested virt might be an option! This allows you to create KVM guests inside a Fedora 22 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 22 virt packages on Fedora 21[edit]

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

http://fedoraproject.org/wiki/Virtualization_Preview_Repository

Areas to test[edit]

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

Ensure you are using the latest virt packages![edit]

Several updated packages were pushed to Fedora 22 only recently. The recommended versions are:

qemu-system-x86-2.3.0-0.3.rc2.fc22.x86_64 (same version for all qemu* packages)
libvirt-daemon-1.2.13-2.fc22.x86_64
virt-manager-1.1.0-7.git6dbe19bd8.fc22

If a 'yum update' isn't pulling these packages in, try 'sudo yum clean all', then 'sudo yum update'.

VM Install[edit]

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[edit]

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

New features[edit]

These are 'newish'. We had them here last year but things have been improved quite a bit.

Extra tests[edit]

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

libguestfs and tools[edit]

You will need Fedora 22 (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[edit]

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

Fedora 21 features:

Fedora 20 features:

Fedora 19 features:

Fedora 18 features:

Misc tests:

All tests:

Complete list of previous tests

Debugging[edit]

https://fedoraproject.org/wiki/How_to_debug_Libvirt_problems

Test Results[edit]

VM Install[edit]

User	Hardware	Guest Install via CDROM	Guest Install via URL	Import VM	References
knoel	Intel Haswell laptop nested	pass ^[1]			↑ Installed Fedora 22 guest 1 on Fedora 21 host. Installed Fedora 22 nested guest.
jardafas	lenovo 440s nested	pass ^[1]			↑ Installation passed on nested kvm. Dir storage pool was used as a target. Creation and management of the storage was done via virt-manager. The guest booted normally, network was working as well.
crobinso	None	pass ^[1]^[2]^[3] pass ^[4]	pass	pass	↑ RHBZ #1211797 ↑ RHBZ #1211796 ↑ Test virt-manager and virt-install for all install methods. Tested with beta RC1 media, not RC2 on the wiki but hopefully it doesn't matter. There's a couple minor issues with the os listings, see the bugs. ↑ Tested virt-manager and virt-install.
jsnow	lenovo yoga 1 x86_64	warn ^[1]^[2]^[3]	fail ^[4] pass ^[5]	pass ^[6] pass ^[7]	↑ RHBZ #1212599 ↑ RHBZ #1212616 ↑ RHBZ #1212617 ↑ f22rc2 via virt-manager: Failed to download packages during first run, did not reproduce. Second attempt had the guest freeze hang with 0% cpu usage during post-installation setup-tasks. ↑ via virt-install: hard guest freeze, cannot reproduce. second run passed. ↑ virt-install --import (win7 ultimate sp1 x64) ↑ virt-manager import: OS version drop down is difficult to read: bad UX.
jenelson	IBM System x3655		pass ^[1] fail ^[2]^[3]		↑ aarm64 installation ↑ RHBZ #1212575 ↑ VM appears to be running, but virt-viewer fails to connect.
pschindl	Lenovo ThinkPad T540p	pass ^[1]^[2]^[3]	pass	pass	↑ RHBZ #1211797 ↑ RHBZ #1211796 ↑ Installation works fine with both virt-manager and virt-install. libosinfo doesn't recognize any of f22 images (it says f21 for all lives and None for anything else e. g. workstation netinst).
abologna	Lenovo ThinkPad T440s	pass ^[1]		pass ^[2]	↑ Installation of Debian 8.0 with virt-manager was successful. ↑ Deleting the VM without deleting the disk image and then importing the disk image worked correctly as well.

Standard Features[edit]

User	Hardware	VM Lifecycle	VM snapshots	Spice features	Change VM CDROM	Host USB hotplug	Host PCI assignment	Nested virt	ARM on x86	References
knoel	Intel Haswell laptop nested	warn ^[1]						pass ^[2]		↑ I had mixed success. I was using virt-manager (except to set host-passthrough at level 0). Creating a nested guest, I got "No virtual networks available". But, the network in the L1 host was working. I used it to download the iso. Creating a nested guest, I got a strange error, "Unable to complete install: 'list.remove(x): x not in list'. I was trying to create the VM with a virtio-scsi disk. When I switched to virtio-blk, it worked. I'm not sure if I can reproduce this. ↑ Nested virt worked well. I used host-passthrough at L0 on Fedora 21 and SandyBridge at L1 using Fedora 22. I did everything with virt-manager using the Fedora 22 beta workstation iso. Except I used virsh edit to set host-passthrough for the L0 host. In the L1 host, I ran yum update to make sure I had qemu 2.3 rc3. I didn't get a default network for the L2 guest. And, I had trouble using virtio-scsi for the L2 guest.
crobinso	None	warn ^[1]^[2]^[3]	pass	warn ^[4]^[5]	warn ^[6]^[7]	pass ^[8]	pass ^[9]	pass ^[10]	pass ^[11]	↑ RHBZ #1211795 ↑ RHBZ #1211760 ↑ Mostly worked. Hit libvirt crash on VM delete a couple times. Delete wizard didn't notice new clone storage. ↑ RHBZ #1211761 ↑ Mostly passed. Some weirdness with the auto resize feature. ↑ RHBZ #1211761 ↑ Worked. But 'eject' needs to be run twice. See the bug ↑ Used a usb2.0 thumbdrive for testing, and F22 Workstation VM ↑ Used intel NIC for passthrough. Only verified it appeared in lspci in the VM, didn't test it was working. ↑ Worked if using host-passthrough ↑ Used virt-install
jsuchane	lenovo 440s nested	pass ^[1]	fail ^[2]^[3]							↑ Operations via virsh: 1. start -- PASSED 2. suspend -- PASSED - state reflected in virt-manager as well 3. resume -- PASSED 4a. managedsave -- PASSED 4b. save/restore -- PASSED 5. destroy -- PASSED Clone/Delete 1. clone -- PASSED 2. clone -- PASSED 3. start -- PASSED 4. shutdown -- PASSED 5. delete -- PASSED ↑ RHBZ #1212471 ↑ 1. create snapshot1 with stopped vm -- PASSED 2. create snapshot2 with running vm -- PASSED 3. create snapshot3 with running vm and launched application -- PASSED 4. run snapshot2 -- PASSED 5. run snapshot1 -- PASSED 6. shutdown -- FAILED, bz 1212471 created
jsuchane	lenovo 440s							pass ^[1]		↑ No problems spotted. For the nested guest I used dir storage located on a secondary disk.
ericb	Lenovo T500	fail ^[1]^[2]								↑ RHBZ #1212620 ↑ Regression in event reporting makes it impossible to filter life-cycle events of just one domain
jsnow	lenovo yoga 1 x86_64	pass ^[1]	pass ^[2]	warn ^[3]						↑ win7 ultimate sp1 x64 ↑ w7 sp1 x64: minor visual artifacting when restoring snapshot 2 ↑ No confirmation/visual feedback for drag/drop, but copy worked. USB redirection works for w7 guest. Resize does not work to downscale.
shajyan	lenovo 440s nested	warn ^[1]		fail ^[2]						↑ Save / Restore problem (could not reproduce) saved - OK restored - Not OK -> VM does not get mouse input, but domain was running immediately after it I cloned the VM, with cloned one both save/restore worked properly Next multiple save/restore actions were without problems ↑ Resize problem ( GNOME classic desktop ) Symptoms: The login freezes, showing the grey desktop only (reproducable multiple times), maybe it will react after some timeout, didn't wait for hours 1) Start VM with the settings View -> Scale Display -> Always with "Auto resize with VM window" unchecked! 2) Check the "Auto resize with VM window" option 3) Reboot the VM from menu: Virtual Machine -> Reboot 4) Try to login -> The login freezes, showing the grey desktop only How to revert back to normal: Uncheck the "Auto resize with VM window" and reboot
abologna	Lenovo ThinkPad T440s	warn ^[1]	pass							↑ RHBZ #1217491

New Features[edit]

User	Hardware	AArch64 on x86	x86 UEFI VM	References
crobinso	None	warn ^[1]	pass ^[2]	↑ Test virt-manager. URL install took a long time just to start, but it did reach the installer, but I stopped there. CDROM install made it past package install but appeared to hang at 'post install' handling. ↑ Installed with virt-manager, using URL install. Seemed to hang when I clicked 'reboot' at end of the installer but other than that it all worked fine.
kparal	None		pass

[1] Installed Fedora 22 guest 1 on Fedora 21 host. Installed Fedora 22 nested guest.

[2] Installation passed on nested kvm. Dir storage pool was used as a target. Creation and management of the storage was done via virt-manager. The guest booted normally, network was working as well.

[3] RHBZ #1211797

[4] RHBZ #1211796

[5] Test virt-manager and virt-install for all install methods. Tested with beta RC1 media, not RC2 on the wiki but hopefully it doesn't matter. There's a couple minor issues with the os listings, see the bugs.

[6] Tested virt-manager and virt-install.

[7] RHBZ #1212599

[8] RHBZ #1212616

[9] RHBZ #1212617

[10] 22rc2 via virt-manager: Failed to download packages during first run, did not reproduce. Second attempt had the guest freeze hang with 0% cpu usage during post-installation setup-tasks.

[11] via virt-install: hard guest freeze, cannot reproduce. second run passed.

[12] virt-install --import (win7 ultimate sp1 x64)

[13] virt-manager import: OS version drop down is difficult to read: bad UX.

[14] rm64 installation

[15] RHBZ #1212575

[16] VM appears to be running, but virt-viewer fails to connect.

[17] RHBZ #1211797

[18] RHBZ #1211796

[19] Installation works fine with both virt-manager and virt-install. libosinfo doesn't recognize any of f22 images (it says f21 for all lives and None for anything else e. g. workstation netinst).

[20] Installation of Debian 8.0 with virt-manager was successful.

[21] Deleting the VM without deleting the disk image and then importing the disk image worked correctly as well.

[22] I had mixed success. I was using virt-manager (except to set host-passthrough at level 0). Creating a nested guest, I got "No virtual networks available". But, the network in the L1 host was working. I used it to download the iso. Creating a nested guest, I got a strange error, "Unable to complete install: 'list.remove(x): x not in list'. I was trying to create the VM with a virtio-scsi disk. When I switched to virtio-blk, it worked. I'm not sure if I can reproduce this.

[23] Nested virt worked well. I used host-passthrough at L0 on Fedora 21 and SandyBridge at L1 using Fedora 22. I did everything with virt-manager using the Fedora 22 beta workstation iso. Except I used virsh edit to set host-passthrough for the L0 host. In the L1 host, I ran yum update to make sure I had qemu 2.3 rc3. I didn't get a default network for the L2 guest. And, I had trouble using virtio-scsi for the L2 guest.

[24] RHBZ #1211795

[25] RHBZ #1211760

[26] Mostly worked. Hit libvirt crash on VM delete a couple times. Delete wizard didn't notice new clone storage.

[27] RHBZ #1211761

[28] Mostly passed. Some weirdness with the auto resize feature.

[29] RHBZ #1211761

[30] Worked. But 'eject' needs to be run twice. See the bug

[31] Used a usb2.0 thumbdrive for testing, and F22 Workstation VM

[32] Used intel NIC for passthrough. Only verified it appeared in lspci in the VM, didn't test it was working.

[33] Worked if using host-passthrough

[34] Used virt-install

[35] Operations via virsh: 1. start -- PASSED 2. suspend -- PASSED - state reflected in virt-manager as well 3. resume -- PASSED 4a. managedsave -- PASSED 4b. save/restore -- PASSED 5. destroy -- PASSED Clone/Delete 1. clone -- PASSED 2. clone -- PASSED 3. start -- PASSED 4. shutdown -- PASSED 5. delete -- PASSED

[36] RHBZ #1212471

[37] 1. create snapshot1 with stopped vm -- PASSED 2. create snapshot2 with running vm -- PASSED 3. create snapshot3 with running vm and launched application -- PASSED 4. run snapshot2 -- PASSED 5. run snapshot1 -- PASSED 6. shutdown -- FAILED, bz 1212471 created

[1]

[1]

[1]

[2]

[3]

[4]

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[1]

[2]

[3]

[1]

[2]

[3]

[1]

[2]

[1]

[2]

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[11]

[1]

[2]

[3]

[1]

[1]

[2]

[1]

[2]

[3]

[1]

[2]

[1]

[1]

[2]

@@ Line 186: / Line 186: @@
 ! User
 ! Hardware
-! [http://fedoraproject.org/wiki/QA:Testcase_Virtualization_CDROM_Guest_Install Guest Install via CDROM]
+! [[QA:Testcase_Virtualization_CDROM_Guest_Install|Guest Install via CDROM]]
-! [http://fedoraproject.org/wiki/QA:Testcase_Virtualization_URL_Guest_Install Guest Install via URL]
+! [[QA:Testcase_Virtualization_URL_Guest_Install|Guest Install via URL]]
-! [http://fedoraproject.org/wiki/QA:Testcase_Virtualization_Import_Guest_Install Import VM]
+! [[QA:Testcase_Virtualization_Import_Guest_Install|Import VM]]
 ! References
 |-
@@ Line 247: / Line 247: @@
 ! User
 ! Hardware
-! [http://fedoraproject.org/wiki/QA:Testcase_Virtualization_Virt_Manager_Lifecycle VM Lifecycle]
+! [[QA:Testcase_Virtualization_Virt_Manager_Lifecycle|VM Lifecycle]]
-! [http://fedoraproject.org/wiki/QA:Testcase_Virt_Snapshot_UI VM snapshots]
+! [[QA:Testcase_Virt_Snapshot_UI|VM snapshots]]
-! [http://fedoraproject.org/wiki/QA:Testcase_Virtualization_Spice_Features Spice features]
+! [[QA:Testcase_Virtualization_Spice_Features|Spice features]]
-! [http://fedoraproject.org/wiki/QA:Testcase_Virt_Change_CDROM_Media Change VM CDROM]
+! [[QA:Testcase_Virt_Change_CDROM_Media|Change VM CDROM]]
-! [http://fedoraproject.org/wiki/QA:Testcase_Virtualization_Hotplug_USB_device_to_guest Host USB hotplug]
+! [[QA:Testcase_Virtualization_Hotplug_USB_device_to_guest|Host USB hotplug]]
-! [http://fedoraproject.org/wiki/QA:Testcase_Virtualization_KVM_PCI_Device_Assignment Host PCI assignment]
+! [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment|Host PCI assignment]]
-! [http://fedoraproject.org/wiki/QA:Testcase_KVM_nested_virt Nested virt]
+! [[QA:Testcase_KVM_nested_virt|Nested virt]]
-! [http://fedoraproject.org/wiki/QA:Testcase_Live_Migration_using_libvirt/virsh Live migration]
+! [[QA:Testcase_Live_Migration_using_libvirt/virsh|Live migration]]
-! [http://fedoraproject.org/wiki/QA:Testcase_Virt_ARM_on_x86 ARM on x86]
+! [[QA:Testcase_Virt_ARM_on_x86|ARM on x86]]
 ! References
 |-
@@ Line 389: / Line 389: @@
    How to revert back to normal: Uncheck the "Auto resize with VM window" and reboot</ref>
+|
+|
+|
+|
+|
+|
+| <references/>
+|-
+| abologna
+| Lenovo ThinkPad T440s
+| {{result|warn}}  <ref>{{bz|1217491}}</ref>
+| {{result|pass}}
+|
 |
 |
@@ Line 398: / Line 411: @@
 |-
 |}
 === New Features ===
@@ Line 405: / Line 417: @@
 ! User
 ! Hardware
-! [http://fedoraproject.org/wiki/QA:Testcase_Virt_AArch64_on_x86 AArch64 on x86]
+! [[QA:Testcase_Virt_AArch64_on_x86|AArch64 on x86]]
-! [http://fedoraproject.org/wiki/QA:Testcase_Virtualization_UEFI x86 UEFI VM]
+! [[QA:Testcase_Virtualization_UEFI|x86 UEFI VM]]
 ! References
 |-
@@ Line 425: / Line 437: @@
 [[Category:Virtualization]]
 [[Category:Fedora 22 Test Days]]

Search

Test Day:2015-04-16 Virtualization: Difference between revisions

Latest revision as of 21:43, 19 September 2016

Contents

What to test?[edit]

Who's available[edit]

Known issues[edit]

What's needed to test[edit]

Fedora 22 on a physical machine[edit]

Install with CD/DVD[edit]

Upgrade from Fedora 21[edit]

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

Fedora 22 virt packages on Fedora 21[edit]

Areas to test[edit]

Ensure you are using the latest virt packages![edit]

VM Install[edit]

Standard features[edit]

New features[edit]

Extra tests[edit]

libguestfs and tools[edit]

Previous test cases[edit]

Debugging[edit]

Test Results[edit]

VM Install[edit]

Standard Features[edit]

New Features[edit]