[Spice-devel] [Users] oVirt console plans

[Brown, Chris (GE Healthcare)]

Hans,
Here are the results of testing I did with and without usbtablet. No usbtablet assumes spice defaults EG: PS2 mouse

BTW for now I am using a VDSM hook script to enable usbtablet and workaround the issues. (TY Andy C.)

Spice defaults:
- Red Hat 7.3 -->  Mouse unusable
- Red Hat 9 -->  Mouse unusable
- Fedora core 1 - 14 -->  Mouse unusable
- Fedora core 15 Mouse useable
- Fedora core 16 Mouse useable
- Red Hat Enterprise 3.x -->  Mouse unusable
- Red Hat Enterprise 4.x -->  Mouse unusable
- Red Hat Enterprise 5.x -->  Mouse unusable
- Red Hat Enterpise 6.x -->  Mouse useable
- SLES 10 -->  Mouse unusable
- SLES 11 -->  Mouse unusable
- SLES 11 SP1 -->  Mouse unusable
- OpenSUSE 11.1 -->  Mouse unusable
- OpenSUSE 11.2 -->  Mouse useable
- OpenSUSE 11.3 -->  Mouse useable
- OpenSUSE 11.4 -->  Mouse useable
- Windows 2000 SP4 -->  Mouse unusable
- Windows XP -->  Mouse unusable
- Windows Vista -->  Mouse unusable
- Windows Server 2003 -->  Mouse unusable
- Windows Server 2003 R2 -->  Mouse unusable
- Windows Server 2008 -->  Mouse unusable
- Windows Server 2008 R2 -->  Mouse unusable
- Solaris 10 Update9  -->  Mouse unusable
- Solaris 11 Express -->  Mouse unusable
- Solaris 11 -->  Mouse unusable

Spice + usbtablet results:
- Red Hat 7.3 -->  Mouse useable
- Red Hat 9 -->  Mouse useable
- Fedora core 1 - 14 -->  Mouse useable
- Fedora core 15 Mouse useable
- Fedora core 16 Mouse useable
- Red Hat Enterprise 3.x -->  Mouse useable
- Red Hat Enterprise 4.x -->  Mouse useable
- Red Hat Enterprise 5.x -->  Mouse useable
- Red Hat Enterpise 6.x -->  Mouse useable
- SLES 10 -->  Mouse useable
- SLES 11 -->  Mouse useable
- SLES 11 SP1 -->  Mouse useable
- OpenSUSE 11.1 -->  Mouse useable
- OpenSUSE 11.2 -->  Mouse useable
- OpenSUSE 11.3 -->  Mouse useable
- OpenSUSE 11.4 -->  Mouse useable
- Windows 2000 SP4 -->  Mouse useable
- Windows XP -->  Mouse useable
- Windows Vista -->  Mouse useable
- Windows Server 2003 -->  Mouse useable
- Windows Server 2003 R2 -->  Mouse useable
- Windows Server 2008 -->  Mouse useable
- Windows Server 2008 R2 -->  Mouse useable
- Solaris 10 Update9  -->  Mouse unusable (still does not work w/solaris)
- Solaris 11 Express -->  Mouse unusable (still does not work w/solaris)
- Solaris 11 -->  Mouse unusable (still does not work w/solaris)

regards,
Chris

-----Original Message-----
From: Hans de Goede [mailto:hdegoede at redhat.com] 
Sent: Thursday, February 02, 2012 2:04 PM
To: Brown, Chris (GE Healthcare)
Cc: Itamar Heim; André Felício; spice-devel at lists.freedesktop.org; users at ovirt.org
Subject: Re: [Spice-devel] [Users] oVirt console plans

Hi,

On 02/01/2012 06:04 PM, Brown, Chris (GE Healthcare) wrote:
> Not a problem I am happy to help in any way that I can.
> To Clarify I executed the same tests with the same results using both RHEV and ovirt.
> I am using:
> RHEV 3.0.1
> oVirt (FC16 + oVirt Nightly builds)
>
> Node wise I use EL6 in my case Scientific Linux 6.x.
>
> The behavior I observe with the mouse in windows or legacy linux guests for example with a spice console is:
> - Erratic mouse movements - mouse jumps all over the spice console 
> randomly
> - Mouse stuck to console border - the mouse simply sticks to the top of the console (EG: first row of pixels) and moves left to right there only.
> - No left or right mouse input seems to be recognized in either of the 
> above cases
>
> The spice console used in both the case of RHEV or ovirt:
> -->  
> --> http://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/RHEV/
> --> SRPMS/rhevm-spice-client-3.0-21.el6.src.rpm
> For ovirt I rebuild the above rpm and extract the msi and cabs then 
> place them into the appropriate (/usr/share/rhevm/rhevm.ear/...) 
> locations

Ok, so you're testing the console under Windows clients? Otherwise this is not all that relevant, and it would be good to know which Linux version you are using for the tests.

> When testing outside of ovirt I have used both spiec and spicey to connect to the guest console:

Ok, some more questions:
* Are you using the windows or linux version of spicec /spicy for your testing?
* Which versions? (output rpm -q spice-gtk spice-client would help)
* Can you try building & installing the latest spice (0.10.1) and/or spice-gtk
   (0.9) on a Linux client machine and try the spicec / spicy from that and see
   if that makes a difference? I just tried a RHEL-5 vm on a RHEL-6.2 host
   without the agent and the mouse works fine.

Regards,

Hans