From Fedora Project Wiki

(Fix a link)
(Drop direct Test Days category membership)
 
(18 intermediate revisions by 9 users not shown)
Line 7: Line 7:
| website = [[Virtualization]]
| website = [[Virtualization]]
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day]
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day]
<!-- ([http://webchat.freenode.net/?channels=fedora-test-day webirc] [http://meetbot.fedoraproject.org/fedora-test-day/2013-05-28/fedora-test-day.2013-05-28-11.10.log.txt IRC logs]) -->
([http://webchat.freenode.net/?channels=fedora-test-day webirc] [http://meetbot.fedoraproject.org/fedora-test-day/2013-10-08/fedora-test-day.2013-10-08-10.45.log.txt IRC logs])
| fedora_mailing_list = virt}} <!-- {{admon/warning | Under construction | The Test Day page is under construction. It will be ready in time for the Test Day (and this message will be removed).}} --> {{admon/note | 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 [http://bugzilla.redhat.com 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 [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}
| fedora_mailing_list = virt}} <!-- {{admon/warning | Under construction | The Test Day page is under construction. It will be ready in time for the Test Day (and this message will be removed).}} --> {{admon/note | 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 [http://bugzilla.redhat.com 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 [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}


Line 22: Line 22:
-->
-->
* [[User:crobinso|Cole Robinson]] (crobinso)
* [[User:crobinso|Cole Robinson]] (crobinso)
* [[User:ericb|Eric Blake]] (eblake on IRC)
* [[User:kashyapc|Kashyap Chamarthy]] (kashyap on IRC)
* [[User:atodorov|Alexander Todorov]] (atodorov on IRC)


== Known issues ==
== Known issues ==
Line 28: Line 31:


* libvirt managed save occasionally fails with 'unexpected migration status in setup': https://bugzilla.redhat.com/show_bug.cgi?id=1015636
* 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 ==
== What's needed to test ==
Line 37: Line 45:


As for getting the latest virt packages, you have a few options:
As for getting the latest virt packages, you have a few options:
<!--
 
=== Virt Test Day Live CD ===
=== 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 <code>yum update</code> 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.
There's a Fedora 20 live CD image that already has all the required virtualization packages installed (though you should still <code>yum update</code> 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: <code>wget -c http://fedorapeople.org/groups/qa/testday-20130528-x86_64.iso</code>
* Get the image: <code>wget -c http://fedorapeople.org/groups/virt/virt-testday-2013-10-08.iso</code>
* For Live CD or USB setup instructions, see: [[FedoraLiveCD#Download_and_Create_Live_image_or_Live_USB]]
* 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)
* 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 ===
=== Fedora 20 on a physical machine ===


Line 79: Line 88:
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!
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!


* [[QA:Testcase Virtualization CDROM Guest Install| Guest install via CDROM]]
* [[QA:Testcase Virtualization CDROM Guest Install|Guest install via CDROM/ISO]]
* [[QA:Testcase Virtualization URL Guest Install| Guest install via URL]]
* [[QA:Testcase Virtualization URL Guest Install|Guest install via URL]]
* [[QA:Testcase_Virtualization_PXE_Guest_Install|Guest install via PXE (only if you have a pre-existing PXE setup)]]
* [[QA:Testcase_Virtualization_Import_Guest_Install|Import existing VM image (only if you have a pre-existing VM image)]]


=== '''Standard features'''===
=== '''Standard features'''===
Line 93: Line 104:
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment|Host PCI device assignment]]
* [[QA:Testcase_Virtualization_KVM_PCI_Device_Assignment|Host PCI device assignment]]
* [[QA:Testcase_Virt_Change_CDROM_Media|Change CDROM media for running VM]]
* [[QA:Testcase_Virt_Change_CDROM_Media|Change CDROM media for running VM]]
* [[QA:Testcase_Virtualization_Spice_Features|Spice features: copy/paste, drag/drop, USB redirection]]


=== '''New features''' ===
=== '''New features''' ===
Line 101: Line 113:
* [[QA:Testcase_Virt_x86_on_ARM|Import ARM guest on your x86 machine and manage with virt-manager/libvirt]]
* [[QA:Testcase_Virt_x86_on_ARM|Import ARM guest on your x86 machine and manage with virt-manager/libvirt]]
* [[QA:Testcase_Virt_Snapshot_UI|Snapshot UI in virt-manager]]
* [[QA:Testcase_Virt_Snapshot_UI|Snapshot UI in virt-manager]]
* [[QA:Testcase_Virt_CPU_Hotplug|VM CPU hotplug]]
* [[QA:Testcase_Virt_Multiqueue_Net|Enable multiqueue virtio networking]]


== Extra tests ==
== 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.
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 ===
* [[QA:Testcase_vzctl_base]]
* [[QA:Testcase_vzctl_network]]


=== libguestfs and tools ===
=== libguestfs and tools ===
Line 129: Line 148:
* [[QA:Testcase Virtualization IO Throttling|VM IO throttling]]
* [[QA:Testcase Virtualization IO Throttling|VM IO throttling]]
* [[QA:Testcase Virtualization PV EOI|VM PV EOI performance optimization]]
* [[QA:Testcase Virtualization PV EOI|VM PV EOI performance optimization]]
* [[QA:Testcase Virtualization USB3 Device Passthrough|USB3 device assignment]]
* [[QA:Testcase Virtualization USB3 Device Passthrough|USB3 device passthrough]]
* [[QA:Testcase Virtualization USB Redirection|USB Redirection]]


Misc tests:
Misc tests:
Line 145: Line 163:


== Test Results ==
== Test Results ==
=== VM Install ===
{|
! User
! Hardware
! Guest Install via CDROM
! Guest Install via url
! PXE Install
! Import VM
! References
|-
| [[User:mrezanin|mrezanin]]
| HP Z400
|
| {{result|pass}} 
|
|
| <references/>
|-
| [[User:Skip_Wyatt|Skip_Wyatt]]
| Dell PowerEdge 2950
| {{result|pass}}  <ref>Using Fedora20 Alpha, guest install passes. No Errors.</ref>
|
|
|
| <references/>
|-
| [[User:Jorge_Fabregas|Jorge_Fabregas]]
| Dell_Optiplex_790  (F19 with Preview Repo)
| {{result|pass}} 
| {{result|fail||873468}}<ref group="long">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.</ref>
|
| {{result|pass}} 
| <references/>
|-
| [[User:atodorov|atodorov]]
| IBM LS22 Blade
|
| {{result|fail||1016449}}<ref>worked around the previous bug to find another one</ref>{{result|fail||1016435}}<ref>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.</ref>
|
|
| <references/>
|-
| [[User:atodorov|atodorov]]
| IBM LS22 Blade qemu-kvm-1.6.0-9.fc20.x86_64 libvirt-daemon-kvm-1.1.3-2.fc20.x86_64
| {{result|pass}}  <ref>Using 20-Beta-TC1 ISO with virt-manager wizard</ref>
| {{result|pass}}  <ref>Tested with 20-Beta-TC1 anbd virt-manager wizard. worked fine this time.</ref>
|
|
| <references/>
|-
| [[User:hhuang|hhuang]]
| Lenovo T500
|
| {{result|pass}}  <ref>F20 Alpha guest install via URL via virt-manager worked as expected.
</ref>
|
|
| <references/>
|-
| [[User:dustymabe|dustymabe]]
| Nested Virt - F19(L0) F20(L1) F20(L2)
| {{result|pass}}  <ref group="long"># F20 iso image was attached to cdrom of L1 guest
# 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</ref>
|
| {{result|pass||1016715}}<ref group="long">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. </ref>
|
| <references/>
|-
| [[User:bsd|bsd]]
| Dell Poweredge M620
|
|
| {{result|pass}}  <ref>Setup a bridge and installed FC 19 as guest with no problems</ref>
| {{result|pass}}  <ref>Imported a FC20 guest image with no problems in virt-manager</ref>
| <references/>
|-
| [[User:zbyszek|zbyszek]]
| ASUSTeK COMPUTER INC. Z9PE-D16 Series
|
| {{result|fail}}  <ref>(I though I can replace, not append. The first three lines should be discarded.)</ref>{{result|fail||1017419|1017428}}<ref>Hangs in dracut, #1017428.</ref>{{result|fail||1017419|1016449}}<ref>Hangs in dracut, either #1016449 or something similar.</ref>
|
|
| <references/>
|-
| [[User:Tadej|Tadej]]
| HP EliteBook 8530p
| {{result|pass||1016657}}<ref>The install via virt-manager's 'New VM' wizard was smooth, apart from the issue described in the bug report.</ref>
| {{result|fail||1016606}}<ref group="long">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).</ref>
|
|
| <references/>
|-
| [[User:rhn-support-jrodrigu|rhn-support-jrodrigu]]
| Lenovo T430s
| {{result|pass}} 
|
|
|
| <references/>
|}
=== Standard Features ===
{|
! User
! Hardware
! VM Lifecycle
! VM Serial console login
! Host USB device hotplug
! Nested Virt
! Live Migration
! Host PCI device assignment
! Change CDROM media for running VM
! Spice features
! References
|-
| [[User:mrezanin|mrezanin]]
| HP Z400
| {{result|pass}} 
| {{result|pass||1016445}}<ref>Problems with combining virt-manager and virsh access to console.</ref>
| {{result|fail||1016511}}
| {{result|pass}} 
|
|
| {{result|pass}}  <ref>BZ 967914 not reproduced</ref>
|
| <references/>
|-
| [[User:Jorge_Fabregas|Jorge_Fabregas]]
| Dell_Optiplex_790  (F19 with Preview Repo)
| {{result|warn}}  <ref group="long">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)</ref>{{result|pass}} 
| {{result|pass}}  <ref group="long">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...</ref>{{result|warn}}  <ref group="long">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
</ref>{{result|warn}}  <ref group="long">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
</ref>
|
|
|
|
| {{result|pass}} 
|
| <references/>
|-
| [[User:atodorov|atodorov]]
| IBM LS22 Blade qemu-kvm-1.6.0-9.fc20.x86_64 libvirt-daemon-kvm-1.1.3-2.fc20.x86_64
| {{result|pass||1015636}}
| {{result|fail||1016488}}<ref>Installed 20-Beta-TC1 from DVD ISO, GUI works fine, serial not.</ref>
|
|
|
|
|
|
| <references/>
|-
| [[User:dustymabe|dustymabe]]
| Nested Virt - F19(L0) F20(L1) F20(L2)
|
| {{result|pass}}  <ref group="long">Install guest with --os-variant fedora20 and verified guest xml has serial console device and can login using virsh console and virt-manager. </ref>
|
|
|
|
|
|
| <references/>
|-
| [[User:bsd|bsd]]
| Dell Poweredge M620
|
| {{result|warn}}  <ref>Exact behavior as Jorge_Fabregas mentioned in his comments</ref>
|
| {{result|pass}}  <ref>Failed the first time - testcase didn't mentione "nested=1" to kvm_intel</ref>{{result|fail}}  <ref group="long">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.</ref>
|
| {{result|warn}}  <ref>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.</ref>{{result|pass}}  <ref>I tested with a Intel 82599 controller.
Normal Device Assignment works as expected. </ref>
|
| {{result|pass}}  <ref>Satisfies everything mentioned in the test case</ref>
| <references/>
|-
| [[User:zbyszek|zbyszek]]
| ASUSTeK COMPUTER INC. Z9PE-D16 Series
| {{result|fail}}  <ref>Hangs at shutdown.</ref>
| {{result|fail||1016613}}<ref>Works through the graphical interface, but not through 'virsh console'.</ref>
|
|
|
|
|
|
| <references/>
|-
| [[User:Tadej|Tadej]]
| HP EliteBook 8530p
| {{result|pass}} 
| {{result|warn||1016488}}<ref group="long">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.</ref>
| {{result|fail||1016511}}<ref>Similar to what mrezanina observed.</ref>
|
|
|
|
|
| <references/>
|-
| [[User:rhn-support-jrodrigu|rhn-support-jrodrigu]]
| Lenovo T430s
| {{result|pass}}  <ref>In save  VM after doing three times it has been successful.</ref>{{result|fail}}  <ref group="long">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</ref>
| {{result|warn}}  <ref group="long">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.</ref>{{result|fail}}  <ref group="long">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
</ref>
| {{result|warn}}  <ref group="long">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.</ref>
| {{result|pass}}  <ref>I have had some issue as losing root password and I have had to recover the system. No more issues.</ref>
|
|
|
|
| <references/>
|}
=== New Features ===
{|
! User
! Hardware
! Virt ACLs
! ARM on x86
! Snapshot UI
! CPU Hotplug
! Mulitiqueue NIC
! References
|-
| [[User:mrezanin|mrezanin]]
| HP Z400
|
| {{result|pass}} 
| {{result|pass}} 
| {{result|pass}} 
| {{result|pass}} 
| <references/>
|-
| [[User:Jorge_Fabregas|Jorge_Fabregas]]
| Dell_Optiplex_790  (F19 with Preview Repo)
|
|
| {{result|pass}} 
| {{result|pass}} 
| {{result|fail}}  <ref>Got the SElINUX AVC on the host plus the VM crashed.  Did it again and same thing happened.</ref>
| <references/>
|-
| [[User:atodorov|atodorov]]
| IBM LS22 Blade qemu-kvm-1.6.0-9.fc20.x86_64 libvirt-daemon-kvm-1.1.3-2.fc20.x86_64
| {{result|pass}}  <ref>Fedora 20 Beta TC2</ref>{{result|pass}} 
| {{result|fail||1016648}}<ref>Fedora-Minimal-armhfp-20-Beta-TC2-sda.raw</ref>
| {{result|pass||1016604}}{{result|pass}}  <ref>No issues for me.</ref>
| {{result|pass||1016613}}
| {{result|pass}}  <ref>Fedora 20 Beta TC2</ref>{{result|pass}} 
| <references/>
|-
| [[User:bsd|bsd]]
| Dell Poweredge M620
|
|
|
| {{result|pass}}  <ref>Followed Testcase - Works as expected</ref>
|
| <references/>
|-
| [[User:Tadej|Tadej]]
| HP EliteBook 8530p
|
|
| {{result|pass}} 
| {{result|fail||1017179}}
|
| <references/>
|}


<!-- metadata: https://fedoraproject.org/wiki/User:Jskladan/Sandbox:F20VirtualizationTestDay
<!-- metadata: https://fedoraproject.org/wiki/User:Jskladan/Sandbox:F20VirtualizationTestDay
     To update the results tool, put the metadata in the following form and submit: http://testdays.qa.fedoraproject.org/testdays/admin/update_testday -->
     To update the results tool, put the metadata in the following form and submit: http://testdays.qa.fedoraproject.org/testdays/admin/update_testday  


'''We are tracking test results in a web application [http://autoqa-stg.fedoraproject.org/testdays/show_event?event_id=7 over here]'''
'''We are tracking test results in a web application [http://autoqa-stg.fedoraproject.org/testdays/show_event?event_id=7 over here]'''
Line 153: Line 493:
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.


Should you encounter any problem while using the web application, please contact jskladan on #fedora-qa channel at freenode, or send an email to jskladan@fedoraproject.org
Should you encounter any problem while using the web application, please contact jskladan on #fedora-qa channel at freenode, or send an email to jskladan@fedoraproject.org -->
 
== Long comments ==
<references group="long" />


[[Category:Test Days]]  [[Category:Fedora 20 Test Days]] [[Category:Virtualization]]
  [[Category:Fedora 20 Test Days]] [[Category:Virtualization]]

Latest revision as of 19:38, 26 June 2015

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

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

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

Known issues[edit]

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

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:

Virt Test Day Live CD[edit]

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.

Fedora 20 on a physical machine[edit]

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

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

Upgrade from Fedora 19[edit]

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

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

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

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

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]

New or improved features in Fedora 20:

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.

OpenVZ[edit]

libguestfs and tools[edit]

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

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

Fedora 19 features:

Fedora 18 features:

Misc tests:

All tests:

Debugging[edit]

Test Results[edit]

VM Install[edit]

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

Standard Features[edit]

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

New Features[edit]

User Hardware Virt ACLs ARM on x86 Snapshot UI CPU Hotplug Mulitiqueue NIC References
mrezanin HP Z400
Pass pass
Pass pass
Pass pass
Pass pass
Jorge_Fabregas Dell_Optiplex_790 (F19 with Preview Repo)
Pass pass
Pass pass
Fail fail
[1]
  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 pass
[1]
Pass pass
Fail fail [2]
[3]
Pass pass [4]
Pass pass
[5]
Pass pass [6]
Pass pass
[7]
Pass pass
  1. ↑ Fedora 20 Beta TC2
  2. ↑ RHBZ #1016648
  3. ↑ Fedora-Minimal-armhfp-20-Beta-TC2-sda.raw
  4. ↑ RHBZ #1016604
  5. ↑ No issues for me.
  6. ↑ RHBZ #1016613
  7. ↑ Fedora 20 Beta TC2
bsd Dell Poweredge M620
Pass pass
[1]
  1. ↑ Followed Testcase - Works as expected
Tadej HP EliteBook 8530p
Pass pass
Fail fail [1]
  1. ↑ RHBZ #1017179


Long comments[edit]

  1. ↑ 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.
  2. ↑ # 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
  3. ↑ 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.
  4. ↑ 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).
  5. ↑ 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)
  6. ↑ 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...
  7. ↑ 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
  8. ↑ 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
  9. ↑ Install guest with --os-variant fedora20 and verified guest xml has serial console device and can login using virsh console and virt-manager.
  10. ↑ 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.
  11. ↑ 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.
  12. ↑ 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
  13. ↑ 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.
  14. ↑ 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
  15. ↑ 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.
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:2013-10-08_Virtualization&oldid=416651"