From Fedora Project Wiki

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 25: Line 25:
* [[User:huzhan|Hu Zhang]] (huzhan)
* [[User:huzhan|Hu Zhang]] (huzhan)
* [[User:ericb|Eric Blake]] (eblake)
* [[User:ericb|Eric Blake]] (eblake)
* [[User:laine|Laine Stump]] (laine)


== Known issues ==
== Known issues ==
Line 170: Line 169:


== Test Results ==
== Test Results ==
This section will have more info when we are closer to the test day.
<!-- metadata: https://fedoraproject.org/wiki/User:Crobinso/Sandbox:F22VirtTestAppMetadata
<!-- metadata: https://fedoraproject.org/wiki/User:Crobinso/Sandbox:F22VirtTestAppMetadata
     To update the results tool, put the metadata in the following form and submit: http://209.132.184.193/testdays/admin  
     To update the results tool, put the metadata in the following form and submit: http://209.132.184.193/testdays/admin -->
 
This section will have more info when we are closer to the test day.
 
'''We are tracking test results in a web application [http://209.132.184.193/testdays/show_event?event_id=25 over here]'''
'''We are tracking test results in a web application [http://209.132.184.193/testdays/show_event?event_id=25 over here]'''


Results from this web application will be automatically transferred to the Wiki a week after the test day, and the reporting system will be shutdown. Feel free to continue testing and filling the wiki even after this date.
Results from this web application will be automatically transferred to the Wiki a week after the test day, and the reporting system will be shutdown. Feel free to continue testing and filling the wiki even after this date.
-->
=== VM Install ===
{|
! User
! Hardware
! [[QA:Testcase_Virtualization_CDROM_Guest_Install|Guest Install via CDROM]]
! [[QA:Testcase_Virtualization_URL_Guest_Install|Guest Install via URL]]
! [[QA:Testcase_Virtualization_Import_Guest_Install|Import VM]]
! References
|-
| [[User:knoel|knoel]]
| Intel Haswell laptop nested
| {{result|pass}}  <ref>Installed Fedora 22 guest 1 on Fedora 21 host. Installed Fedora 22 nested guest.</ref>
|
|
| <references/>
|-
| [[User:jardafas|jardafas]]
| lenovo 440s nested
| {{result|pass}}  <ref>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.</ref>
|
|
| <references/>
|-
| [[User:crobinso|crobinso]]
| None
| {{result|pass}}  <ref>{{bz|1211797}}</ref><ref>{{bz|1211796}}</ref><ref>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.</ref>{{result|pass}}  <ref>Tested virt-manager and virt-install.</ref>
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| [[User:jsnow|jsnow]]
| lenovo yoga 1 x86_64
| {{result|warn}}  <ref>{{bz|1212599}}</ref><ref>{{bz|1212616}}</ref><ref>{{bz|1212617}}</ref>
| {{result|fail}}  <ref>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.</ref>{{result|pass}}  <ref>via virt-install: hard guest freeze, cannot reproduce. second run passed.</ref>
| {{result|pass}}  <ref>virt-install --import (win7 ultimate sp1 x64)</ref>{{result|pass}}  <ref>virt-manager import: OS version drop down is difficult to read: bad UX.</ref>
| <references/>
|-
| [[User:jenelson|jenelson]]
| IBM System x3655
|
| {{result|pass}}  <ref>aarm64 installation</ref>{{result|fail}}  <ref>{{bz|1212575}}</ref><ref>VM appears to be running, but virt-viewer fails to connect.</ref>
|
| <references/>
|-
| [[User:pschindl|pschindl]]
| Lenovo ThinkPad T540p
| {{result|pass}}  <ref>{{bz|1211797}}</ref><ref>{{bz|1211796}}</ref><ref>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).</ref>
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| abologna
| Lenovo ThinkPad T440s
| {{result|pass}}  <ref>Installation of Debian 8.0 with virt-manager was successful.</ref>
|
| {{result|pass}}  <ref>Deleting the VM without deleting the disk image and then importing the disk image worked correctly as well.</ref>
| <references/>
|-
|}
=== Standard Features ===
{|
! User
! Hardware
! [[QA:Testcase_Virtualization_Virt_Manager_Lifecycle|VM Lifecycle]]
! [[QA:Testcase_Virt_Snapshot_UI|VM snapshots]]
! [[QA:Testcase_Virtualization_Spice_Features|Spice features]]
! [[QA:Testcase_Virt_Change_CDROM_Media|Change VM CDROM]]
! [[QA:Testcase_Virtualization_Hotplug_USB_device_to_guest|Host USB hotplug]]
! [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment|Host PCI assignment]]
! [[QA:Testcase_KVM_nested_virt|Nested virt]]
! [[QA:Testcase_Live_Migration_using_libvirt/virsh|Live migration]]
! [[QA:Testcase_Virt_ARM_on_x86|ARM on x86]]
! References
|-
| [[User:knoel|knoel]]
| Intel Haswell laptop nested
| {{result|warn}}  <ref>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.
</ref>
|
|
|
|
|
| {{result|pass}}  <ref>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. </ref>
|
|
| <references/>
|-
| [[User:crobinso|crobinso]]
| None
| {{result|warn}}  <ref>{{bz|1211795}}</ref><ref>{{bz|1211760}}</ref><ref>Mostly worked. Hit libvirt crash on VM delete a couple times. Delete wizard didn't notice new clone storage.</ref>
| {{result|pass}} 
| {{result|warn}}  <ref>{{bz|1211761}}</ref><ref>Mostly passed. Some weirdness with the auto resize feature.</ref>
| {{result|warn}}  <ref>{{bz|1211761}}</ref><ref>Worked. But 'eject' needs to be run twice. See the bug</ref>
| {{result|pass}}  <ref>Used a usb2.0 thumbdrive for testing, and F22 Workstation VM</ref>
| {{result|pass}}  <ref>Used intel NIC for passthrough. Only verified it appeared in lspci in the VM, didn't test it was working.</ref>
| {{result|pass}}  <ref>Worked if using host-passthrough</ref>
|
| {{result|pass}}  <ref>Used virt-install</ref>
| <references/>
|-
| [[User:jsuchane|jsuchane]]
| lenovo 440s nested
| {{result|pass}}  <ref>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</ref>
| {{result|fail}}  <ref>{{bz|1212471}}</ref><ref>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
</ref>
|
|
|
|
|
|
|
| <references/>
|-
| [[User:jsuchane|jsuchane]]
| lenovo 440s
|
|
|
|
|
|
| {{result|pass}}  <ref>No problems spotted. For the nested guest I used dir storage located on a secondary disk.</ref>
|
|
| <references/>
|-
| [[User:ericb|ericb]]
| Lenovo T500
| {{result|fail}}  <ref>{{bz|1212620}}</ref><ref>Regression in event reporting makes it impossible to filter life-cycle events of just one domain</ref>
|
|
|
|
|
|
|
|
| <references/>
|-
| [[User:jsnow|jsnow]]
| lenovo yoga 1 x86_64
| {{result|pass}}  <ref>win7 ultimate sp1 x64</ref>
| {{result|pass}}  <ref>w7 sp1 x64: minor visual artifacting when restoring snapshot 2</ref>
| {{result|warn}}  <ref>No confirmation/visual feedback for drag/drop, but copy worked. USB redirection works for w7 guest. Resize does not work to downscale.</ref>
|
|
|
|
|
|
| <references/>
|-
| [[User:shajyan|shajyan]]
| lenovo 440s nested
| {{result|warn}}  <ref>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</ref>
|
| {{result|fail}}  <ref>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</ref>
|
|
|
|
|
|
| <references/>
|-
| abologna
| Lenovo ThinkPad T440s
| {{result|warn}}  <ref>{{bz|1217491}}</ref>
| {{result|pass}}
|
|
|
|
|
|
|
| <references/>
|-
|}
=== New Features ===
{|
! User
! Hardware
! [[QA:Testcase_Virt_AArch64_on_x86|AArch64 on x86]]
! [[QA:Testcase_Virtualization_UEFI|x86 UEFI VM]]
! References
|-
| [[User:crobinso|crobinso]]
| None
| {{result|warn}}  <ref>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.</ref>
| {{result|pass}}  <ref>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.</ref>
| <references/>
|-
| [[User:kparal|kparal]]
| None
|
| {{result|pass}} 
| <references/>
|-
|}




[[Category:Virtualization]]
[[Category:Virtualization]]
[[Category:Fedora 22 Test Days]]
[[Category:Fedora 22 Test Days]]
Please note that all contributions to Fedora Project Wiki are considered to be released under the Attribution-Share Alike 4.0 International (see Fedora Project Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please solve the following task below and enter the answer in the box (more info):

Cancel Editing help (opens in new window)