From Fedora Project Wiki

Line 18: 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.
  
== Who's available ==
+
=== New features ===
  
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
+
* Xspice: spice server running inside the remote system you're connecting to
* Development - Jeremy White (jwhite)
+
* spice-html5: a client running inside the browser
* Quality Assurance - [[User:Djasa|David Jaša]] (djasa),
+
* 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 oVirt/RHEV-M VMs using ovirt:// URIs (similar to existing <code>virt-viewer qemu:///...</code> invocation)
  
== What do I need for testing? ==  
+
=== Existing features ===
  
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]
+
* connection to remote VMs
 +
** 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
  
=== prerequisites for SSL/TLS ===
 
  
=== prerequisites for connection to Xspice ===
+
== Who's available ==
  
You only need any Fedora system (physical or virtual) with <code>xorg-x11-server-Xspice</code> and <code>virt-viewer</code> packages installed.
+
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
 
+
* Development
=== prerequisites for connection to VMs ===
+
** Xspice: Jeremy White (jwhite), Alon Levy (alevy)
 
+
** spice-html5: Jeremy White
=== prerequisites for migration testing ===
+
** file transfer: Dunrong Huang (dunrong), Hans de Goede (hansg; just linux agent)
 
+
** connection using ovirt:// URIs: Christophe Fergeau (teuf)
== How to get generic system? ==
+
* Quality Assurance - [[User:Djasa|David Jaša]] (djasa),  
 
 
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].
 
 
 
 
 
== How to get virtualization-capable system? ==
 
 
 
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>
 
 
 
As for getting the latest virt packages, you have a few options:
 
 
 
=== Fedora 19 on a physical machine ===
 
 
 
The preferred testing platform is a fully updated Fedora 19 machine. You have a few options for getting the Fedora 19 bits:
 
 
 
* 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>>
 
 
 
* Upgrade from Fedora 18
 
** The supported way is using 'fedup': https://fedoraproject.org/wiki/FedUp#How_Can_I_Upgrade_My_System_with_FedUp.3F
 
** 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!
 
 
 
=== Fedora 19 virt packages on Fedora 18 ===
 
 
 
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:
 
 
 
http://fedoraproject.org/wiki/Virtualization_Preview_Repository
 
 
 
=== Run Fedora 19 in a VM with nested virtualization ===
 
 
 
Do you have a new machine with a ton of ram and storage space, running Fedora 18? Nested virt might be an option!
 
This allows you to create KVM guests _inside_ a Fedora 19 VM.
 
 
 
# 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>
 
 
 
Some notes on nested virt with AMD and Intel:
 
 
 
* 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/
 
  
<<FIXME>>: still a template from now on
 
  
 
== How to test? ==
 
== How to test? ==
  
High level details on how a contributor can get involved.  This can include (but not limited to):
 
  
* Areas to target with exploratory testing
+
== What do I need for testing? ==
* A list of pre-defined test cases to execute
 
* How to report back results
 
  
  
 
== Test Cases ==
 
== Test Cases ==
  
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 ==

Revision as of 22:02, 20 May 2013

Fedora Test Days
Echo-testing-48px.png
SPICE Test Day

Date 2013-05-30
Time all day

Website Features/Spice
IRC #spice, #fedora-test-day (webirc)
Mailing list spice-devel@lists.freedesktop.org


Warning.png
In construction
The Test Day page is yet in construction. It will be ready for the Test Day - when this message is removed :) .
Note.png
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 instalment of Fedora Test Day will focus on Spice, the protocol to access remote VMs and physical linux systems.

New features

  • 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 oVirt/RHEV-M VMs using ovirt:// URIs (similar to existing virt-viewer qemu:///... invocation)

Existing features

  • connection to remote VMs
    • 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


Who's available

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

  • Development
    • Xspice: Jeremy White (jwhite), Alon Levy (alevy)
    • spice-html5: Jeremy White
    • file transfer: Dunrong Huang (dunrong), Hans de Goede (hansg; just linux agent)
    • connection using ovirt:// URIs: Christophe Fergeau (teuf)
  • Quality Assurance - David Jaša (djasa),


How to test?

What do I need for testing?

Test Cases

Test Results

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:

If you have problems with any of the tests, report a bug to Bugzilla usually for the component udisks, or 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 result template to enter your result, as shown in the example result line.

User Sample test 1 Sample test 2 Sample test 3 Sample test 4 References
Sample User
none
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345