Test Day:2013-05-30 Spice

Fedora Test Days
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

In construction
The Test Day page is yet in construction. It will be ready for the Test Day - when this message is removed :) .

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
• migration of VM to another host while VM is running and client stays connected

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),

What do I need for testing?

Client

client means client program or client OS and environment. Preferred clients for this test day are:

• virt-viewer or remote-viewer running on top of Fedora 19
• spice-html5 from Fedora package opened on any of the supported browsers:

You can also use another clients:

• virt-viewer or remote-viewer run on different OS or version
• Gnome Boxes
• virt-manager
• virt-viewer for Windows. Installers are available for download at project site. Note that USB redirection won't work for you unless you 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 spice-client package on Fedora) is deprecated client that already didn't see any development for quite long time

Host

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.

• you can reuse the host you used for Virtualization Test Day
• if you don't have the virtualization host yet, follow instructions on Virtualization Test Day
• alternatively, you can use any other spice-capable virtualization host

Remote system

A physical or virtual system running Xspice server is called a remote system from now on

Guest system

Virtualized system needs add-on software called spice agent installed to make all features fully work:

• on Fedora, it is provided by spice-vdagent package, installed by default. It should be running from start, too (one spice-vdagentd process and two spice-vdagent processes - one for login manager and one for user session)
• on Windows, please install Windows Guest Tools from project download page

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	warn	fail