[Users] oVirt console plans

[Brown, Chris (GE Healthcare)]

The issue I am getting at is at install time. Having the agent after the fact is fine for those guests to which it can be added.
However there are those guests where it still cannot be added at all even if an install can be done by hand/keyboard only (very painful).
This includes legacy linux guests, bsd guests or Solaris guest for example to which are still actively used by many for whatever reason (we do).
I look at this from the perspective of a power user or developer using the PuP to install a new development or test VM for example.
Not being able to interact with a guest mouse at install time for those users makes for a no go scenario.
I also look at the fact that VMware, and OVM (Ovirt/RHEV competitors) for example do not suffer this shortcoming (again keep in mind install time).
- Chris

-----Original Message-----
From: Yaniv Kaul [mailto:ykaul at redhat.com] 
Sent: Tuesday, January 31, 2012 12:15 AM
To: Brown, Chris (GE Healthcare)
Cc: Itamar Heim; André Felício; spice-devel at lists.freedesktop.org; users at ovirt.org; David Blechter
Subject: Re: [Users] oVirt console plans

On 01/31/2012 07:38 AM, Brown, Chris (GE Healthcare) wrote:
> I did some more extensive testing tonight to see how many guests would have issues with a SPICE based console. This testing was specifically during guest OS install time.

On how many of them was the Spice guest agent installed? Without it, you will not have client-side mouse, which contributes to a much better mouse behaviour.

>
> Here is the list and the results
> - 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

Out of curiosity, and assuming you haven't spent all night on this - how 
are you testing so many different operating systems?
And moreover, if you are already into testing so many, any other issues 
encountered? Networking works OK across all of them?
Impressive work,
Y.

>
> Of the above guests all of them were fine with a VNC console.
> The windows guests could be loaded via vnc then the qxl drivers installed after install and all was well.
> However the older Linux guests and all solaris guests were not able to be made to work with spice during run time forcing VNC to be used if mouse interaction is required.
>
> IMHO if spice will be the only supported console type then some work needs to be done to take older linux guests and other operating systems into consideration.
> This particularly applies to the PuP when developers or users are loading guests from scratch.
>
> - Chris
>
> ________________________________
>
> From: Brown, Chris (GE Healthcare)
> Sent: Mon 1/30/2012 2:09 PM
> To: 'Itamar Heim'; André Felício
> Cc: spice-devel at lists.freedesktop.org; users at ovirt.org; David Blechter
> Subject: RE: [Users] oVirt console plans
>
>
>
> You can just rebuild the current RHEV spice-xpi source RPM and drop the resulting files into you ovirt install.
> - Found here: http://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/RHEV/SRPMS/rhevm-spice-client-3.0-21.el6.src.rpm
> - rpmbuild --rebuild rhevm-spice-client-3.0-21.el6.src.rpm (install dependent packages via yum if build fails due to deps, not that many needed)
> - unpack the resulting spice-xpi client isntallers and cabs from the rpms using: rpm2cpio
> - rpm2cpio<nameofrpm>  | cpio -ivd
> - place the files into their corresponding locations on your ovirt install.
> - you can find the paths where things go via rpm -qlp<packagename>  replace "rhevm" with "engine" pathing wise
> - Pathing on ovirt should be something like:
> -->  /usr/share/ovirt-engine/engine.ear/engineanger.ear/
> -->  /usr/share/ovirt-engine/enginer.ear/userportal.ear/ovirt.org...
> -restart jboss and you will be good to go
>
> - Chris
>
> -----Original Message-----
> From: users-bounces at ovirt.org [mailto:users-bounces at ovirt.org] On Behalf Of Itamar Heim
> Sent: Monday, January 30, 2012 2:01 PM
> To: André Felício
> Cc: spice-devel at lists.freedesktop.org; users at ovirt.org; David Blechter
> Subject: Re: [Users] oVirt console plans
>
> On 01/30/2012 09:58 PM, André Felício wrote:
>>>> There are many SO (windows) that access by SPICE is a little tricky.
>>> What's tricky with Spice? If there's anything we can do to help make
>>> Spice easier to use, let us know.
>> I tried compiling spice-xpi for windows it several times and it still
>> fails. Anyone have the spice-client and spice-xpi compiled for
>> windows?
> cc'ing spice-devel to provide input on status/availability of spice-xpi for windows and/or spice-activex.
>
>> OVirt appears VNC console in the option but does not have a way to
>> access it over webadmin.
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users