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 9: Line 9:
| mailing_list = spice-devel@lists.freedesktop.org
| mailing_list = spice-devel@lists.freedesktop.org
}}
}}
{{admon/warning | In construction | The Test Day page is yet in construction. It will be ready for the Test Day - when this message is 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.}}
{{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 16: Line 18:
Today's instalment of Fedora Test Day will focus on '''Spice''', the protocol to access remote VMs and physical linux systems.
Today's instalment of Fedora Test Day will focus on '''Spice''', the protocol to access remote VMs and physical linux systems.


=== New features ===
== Who's available ==
 
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
* Development - Jeremy White (jwhite)
* Quality Assurance - [[User:Djasa|David Jaša]] (djasa),
 
== What do I need for testing? ==
 
An updated [http://fedoraproject.org/get-prerelease Fedora 19 pre-release], [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image]


* Much improved multi-monitor support, see [http://hansdegoede.livejournal.com/12969.html this blog post] for details
=== prerequisites for SSL/TLS ===
* Xspice: spice server running inside the remote system you're connecting to
* spice-html5: a client running inside the browser
* file transfer: ability to copy file from client system to guest/remote system using drag and drop
* new connection methods for virt-viewer/remote-viewer:
** using .vv files
** connecting to [http://ovirt.org/ oVirt]/RHEV-M VMs using ovirt:// URIs (similar to existing <code>virt-viewer qemu:///...</code> invocation)


=== Existing features ===
=== prerequisites for connection to Xspice ===


* connection to remote VMs
You only need any Fedora system (physical or virtual) with <code>xorg-x11-server-Xspice</code> and <code>virt-viewer</code> packages installed.
** optional SSL/TLS encryption
** optional password or SASL authentication
* smartcard sharing/remoting
* clipboard sharing for text and image data, working both ways
* client-mode mouse (with smooth transition between guest/remote system and client system and rendered instantly)
* guest/remote system monitor layout
** arbitrary resolution
** multiple monitors
* video remoting
** detection of video stream
** sync of audio with video
* USB redirection
* migration of VM to another host while VM is running and client stays connected


=== prerequisites for connection to VMs ===


== Who's available ==
=== prerequisites for migration testing ===
 
== How to get generic system? ==
 
This system is good just for testing client and/or Xspice. Generic Fedora Test Day guidelines apply:
 
=== '''Update your machine''' ===
 
If you're running Fedora XX, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or:
 
=== '''Live image''' ===
 
Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. Live images can be found [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ here].


The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
* Development
** Xspice: Jeremy White (jwhite), Alon Levy (alon/alevy/alonlevy)
** spice-html5: Jeremy White
** file transfer: Hans de Goede (hansg)
** connection using ovirt:// URIs: Christophe Fergeau (teuf)
* Quality Assurance - [[User:Djasa|David Jaša]] (djasa), [[User:Martix|Martin Holec]] (Martix)


== What do I need for testing? ==
== How to get virtualization-capable system? ==


=== Live CDs ===
For starters, your physical machine should have:
* Hardware virtualization support (e.g. Intel VT or AMD-V) (see [[How_to_debug_Virtualization_problems#Is_My_Guest_Using_KVM.3F|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 <br><pre>yum groupinstall virtualization</pre>


Live CDs with all required packages installed are provided for this test day. Tips on using a live image are available at [[FedoraLiveCD]].
As for getting the latest virt packages, you have a few options:
{|
! Architecture !! SHA256SUM
|-
| [http://fedorapeople.org/groups/qa/testday-20130530-x86_64.iso x86_64] || c214f3a326221b998be896c59bb5af1718030b3b5ecb85599f77e76309f0cd26
|-
| [http://fedorapeople.org/groups/qa/testday-20130530-i686.iso i686] || da574c08e0469d890a3f33e7638369e8d7f21d9e9bd8e6e506d7d39c5f611856
|}


=== Client ===
=== Fedora 19 on a physical machine ===


'''client''' means client program or client OS and environment. Preferred clients for this test day are:
The preferred testing platform is a fully updated Fedora 19 machine. You have a few options for getting the Fedora 19 bits:
* <code>virt-viewer</code> or <code>remote-viewer</code> running on top of Fedora 19
* '''spice-html5''' from Fedora package opened on any of the supported browsers:
**
You can also use another clients:
* <code>virt-viewer</code> or <code>remote-viewer</code> run on different OS or version
* '''Gnome Boxes'''
* <code>virt-manager</code>
* '''virt-viewer''' for Windows. Installers are available for download [http://spice-space.org/download.html at project site]. Note that USB redirection won't work for you unless you [http://lists.freedesktop.org/archives/spice-devel/2013-May/013479.html build USBClerk yourself]
Don't bother testing these:
* '''spicy''' is a tool used sometimes for testing of some features. Don't expect it to work smoothly, or even work correctly
* '''spicec''' (found in <code>spice-client</code> package on Fedora) is deprecated client that already didn't see any development for quite long time


=== Host ===
* Install with CD/DVD.
** Latest live CD builds ('desktop' is the default): http://alt.fedoraproject.org/pub/alt/nightly-composes/
** Latest 64 Bit DVD: <<FIXME>>


'''host''' is a machine that hosts virtual machines. When client is about to show a VM display, it connects to qemu process running on the host.
* Upgrade from Fedora 18
* you can reuse the host you used for [[Test_Day:2013-05-28_Virtualization|Virtualization Test Day]]
** The supported way is using 'fedup': https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F
* if you don't have the virtualization host yet, follow virtualization test day [[Test_Day:2013-05-28_Virtualization#What.27s_needed_to_test | instructions]]
** Update using 'yum': https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum  <br>This method is not supported, but is very commonly used by developers. If you're a power user this is a possible option!
* alternatively, you can use any other spice-capable virtualization host
* for testing of connecting to oVirt (or RHEV) VMs, you'll need access to a running oVirt (RHEV) setup


=== Remote system ===
=== Fedora 19 virt packages on Fedora 18 ===


A physical or virtual system running '''Xspice''' server is called a remote system from now on
If you aren't ready to make the jump to Fedora 19, this is the next best thing! Run latest virt packages on Fedora 18 from the virt-preview repo:


=== Guest system ===
http://fedoraproject.org/wiki/Virtualization_Preview_Repository


Virtualized system is frequently call '''guest'''. If you don't have any VM with guest system installed, follow [[Test_Day:2013-05-28_Virtualization#VM_Install | virtualization test day instructions]].
=== Run Fedora 19 in a VM with nested virtualization ===


The guest system needs add-on software called '''spice agent''' installed to make all features fully work:
Do you have a new machine with a ton of ram and storage space, running Fedora 18? Nested virt might be an option!
* on Fedora, it is provided by <code>spice-vdagent</code> package, installed by default. It should be running from start, too (one <code>spice-vdagentd</code> process and two <code>spice-vdagent</code> processes - one for login manager and one for user session)
This allows you to create KVM guests _inside_ a Fedora 19 VM.
* on Windows, please install Windows Guest Tools from [http://spice-space.org/download.html project download page]


== Quick VM installation ==
# Install the latest virt packages from virt-preview using the instructions above.
# Install a Fedora 19 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: <br><pre>virt-host-validate</pre>


=== Gnome Boxes ===
Some notes on nested virt with AMD and Intel:


Just start Boxes, create a new VM and follow the guide.
* http://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-amd/
* http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-intel/
* http://kashyapc.wordpress.com/2012/07/28/nested-virtualization-with-intel-take-2-with-fedora-17/


=== virt-install ===
<<FIXME>>: still a template from now on


<code>virt-install</code> can configure a VM for you including all the subtleties and even start an installation:
== How to test? ==
<pre>virt-install -c SESSION --name NAME --memory MEMORY [--cdrom CDROM|--location LOCATION] --os-variant OS [--disk DISKOPTS|--nodisks] --graphics spice --video qxl [--video qxl] --channel spicevmc --redirdev usb,type=spicevmc [--redirdev usb,type=spicevmc] </pre>
where:
* local '''SESSION''' is <code>qemu:///system</code> for system-wide session of <code>qemu:///session</code> for actual user session (this is what Boxes uses). Refer to [http://libvirt.org/remote.html libvirt documentation] if you wish to install VM on a different hypervisor
* '''NAME''' is VM name
* '''MEMORY''' is memory size in MB
* a VM can be installed either from '''CDROM''' or, for some distributions, '''LOCATION''' pointing to installation tree is supported
* '''OS''' is one of options returned by <code>virt-install --os-variant list</code>. It allows <code>virt-install</code> to better optimize the VM setup
* specify '''--nodisks''' for VMs running from live media. '''DISKOPTS''' is a comma-separated list of keys. For file-backed VM disk, you should be fine to specify just <code>path=path/to/file,size=size_in_GB</code>. If you wish to stick with gnome-boxes default VM image location, specify <code>path=~/.local/share/gnome-boxes/images/</code>
* specify up to four <code>--video qxl</code> stanzas in order to support multiple monitor on Windows VMs
* number of <code>--redirdev usb,type=spicevmc</code> stanzas limits number of USB devices that can be redirected to the guest OS
<code>virt-install</code> sets up the VM and starts installation. The installation itself is not automatic though.


== Test Cases ==
High level details on how a contributor can get involved.  This can include (but not limited to):


=== New features ===
* Areas to target with exploratory testing
* A list of pre-defined test cases to execute
* How to report back results


* [[QA:Testcase_Spice_file_transfer | Drag and drop file transfer]]
* [[QA:Testcase_Spice_Xspice | Test XSpice]]
* [[QA:Testcase_Spice_html5 | Test use a pure Javascript Spice client]]
* [[QA:Testcase_Spice_virt-viewer_direct_connection_to_oVirt | Direct connection to oVirt/RHEV VMs]]


=== Existing features ===
== Test Cases ==


* migration
Provide a list of test areas or test cases that you'd like contributors to execute.  For other examples, see [[:Category:Test_Cases]].


== Test Results ==
== Test Results ==


If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] using this key:
Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
* use '''[https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=19&component=spice-gtk spice-gtk]''' component for issues happening on client side
* use '''[https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=19&component=spice-server spice-server]''' component for issues happening on virtualization host
* use '''[https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=19&component=spice-vdagent spice-vdagent]''' component for guest agent issues
* use '''[https://bugs.freedesktop.org/enter_bug.cgi?product=Spice Freedesktop bugzilla]''' to report issues in spice components used in other distributions
* please specify complete environment: client OS and architecture, client (virt-viewer or spice-html5) version, host OS with qemu-kvm and spice-server versions, guest OS version, guest agent version


If you are unsure about exactly how to file the report or what other information to include, just ask on IRC (<code>#spice</code> at irc.gimp.org) and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. Please specify your environment in second column as i is in the template For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility gnome-disk-utility] for bugs in the Palimpsest graphical front end itself. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.


{|
{|
! User
! User
! Test environment
! [[QA:Testcase_sample_1|Sample test 1]]
! [[QA:Testcase_Spice_file_transfer|Drag and drop file transfer]]
! [[QA:Testcase_sample_2|Sample test 2]]
! [[QA:Testcase_Spice_Xspice | Test XSpice]]
! [[QA:Testcase_sample_3|Sample test 3]]
! [[QA:Testcase_Spice_html5 | Test use a pure Javascript Spice client]]
! [[QA:Testcase_sample_4|Sample test 4]]
! [[QA:Testcase_Spice_virt-viewer_direct_connection_to_oVirt | Direct connection to oVirt/RHEV VMs]]
! References
! References
|-
|-
| [[User:SampleUser|Sample User]]
| [[User:SampleUser|Sample User]]
|
* Client: F19, virt-viewer-0.5.6-1.fc19.x86_64
* Host: F19, qemu-kvm-1.4.1-3.fc19.x86_64, spice-server-0.12.2-5.fc19.x86_64
* Guest: F19 with Gnome 3, spice-vdagent-0.14.0-2.fc19.x86_64
| {{result|none}}  
| {{result|none}}  
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| {{result|fail}} <ref>{{bz|12345}}</ref>
| {{result|fail}} <ref>{{bz|12345}}</ref>
| <references/>
|-
| [[User:tassadar|tassadar]]
|
* Client: F19, virt-viewer-0.5.6-1.fc19.x86_64
* Host: F19, qemu-kvm-1.4.2-2.fc19.x86_64, spice-server-0.12.3-1.fc19.x86_64
* Guest: F19 with Gnome 3, spice-vdagent-0.14.0-2.fc19.x86_64
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref>It works, but {{bz|968931}}</ref>
| {{result|info}} <ref>Don't have access to these</ref>
| <references/>
|-
| [[User:mkovarik|mkovarik]]
|
* Client: F19, virt-viewer-0.5.6-1.fc19.x86_64
* Host: F19, qemu-kvm-1.4.2-2.fc19.x86_64, spice-server-0.12.3-1.fc19.x86_64
* Guest: F19 with Gnome 3, spice-vdagent-0.14.0-2.fc19.x86_64
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|none}}
| <references/>
|-
| [[User:jkoten|jkoten]]
|
* Client: F19, virt-viewer-0.5.6-1.fc19.x86_64, gnome-boxes-3.8.3-1.fc19.x86_64
* Host: RHEV-M 3.1
* Guest: Rhel7 Alpha3, spice-vdagent-0.12.1-1.el7.x86_64
| {{result|none}}
| {{result|pass}} <ref>Tested on localhost</ref>
| {{result|none}}
| {{result|fail}} <ref>Boxes crash on gnome session start {{bz|968929}}</ref><ref>Connecting with remote-viewer - Guest crashed on gnome session start{{bz|969069}}</ref>
| <references/>
|-
| [[User:Zbyszek|Zbyszek]]
|
* Client: F19, virt-viewer-0.5.6-1.fc19.x86_64
* Host: x86_64, F19, qemu-kvm-1.4.2-2.fc19.x86_64, spice-server-0.12.3-1.fc19.x86_64
* Guest: i686, testday-20130530-i686.iso + xorg-x11-drv-qxl-0.1.1-0.8.20130514git77a1594.fc19 for {{bz|965101}} <ref>Hit {{bz|969084}}, {{bz|969118}} on the way.</ref>
| {{result|fail}} <ref>Works fine with small files, but hangs when transferring an iso image {{bz|969109}}</ref>
| {{result|pass}} <ref>RFE: https://bugs.freedesktop.org/show_bug.cgi?id=65185</ref>
| {{result|none}}
| {{result|none}}
| <references/>
|-
| [[User:vbudikov|vbudikov]]
|
* Client: F19, virt-viewer-0.5.6-1.fc19.x86_64, gnome-boxes-3.8.2-5.fc19.x86_64
* Host: F19, qemu-kvm-1.4.2-2.fc19.x86_64, spice-server-0.12.3-1.fc19.x86_64
* Guest: F19 with Gnome 3, spice-vdagent-0.14.0-2.fc19.x86_64
| {{result|pass}}
| {{result|pass}}
| {{result|none}}
| {{result|none}}
| <references/>
| <references/>
|-
|-
|}
|}


[[Category:Fedora 19 Test Days|s]]
[[Category:Test Days]]
[[Category:QA Templates]]
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)