12:38 p.m.
I played a bit with the MIME and browsers.
When switching between spice/vnc/rdp protocols since the connection file
that comes down is extension ".vv" this is an issue. Once you have
associated a MIME type of ".vv"
one of the local clients (SPICE or VNC or RDP) the browser now thinks that
".vv" files should be used with whatever it was associated with only. This
is to say should the extension be something different for each protocol so
each protocol could be used and associated with a local client?
Also I have not yet been able to get RDP to work at all. On windows 7
systems under IE 9 is always greyed nor selectable (using latest master).
Using the connection files ".vv" and opening them with remote-viewer to
tight-vnc for example does not work at all. I have spice certificates and
ssl disabled as well so that cannot get in the way.
Any quick pointers on actually getting RDP to work or the connection files
to work with a local remote-viewer or vnc client?
- DHC
On Fri, Apr 19, 2013 at 3:08 AM, Michal Skrivanek <
michal.skrivanek(a)redhat.com> wrote:
On 18 Apr 2013, at 17:57, Dead Horse wrote:
Nicely done and this would definitely be useful. Nothing is more
nauseating then being forced to use Internet Exploder to interact with an
ovirt/KVM SPICE console under windows.
For the plugin deployment this is definitely a point of pain. At the
moment ovirt users wishing to use the SPICE Activex plugin must use an an
dated version of the SPICE client packaged with the necessary SpiceX.dll. (
http://elmarco.fedorapeople.org/spice.cab)
They must also take manual steps to install and deploy the plugin on
ovirt-engine server (this very painful to users). The versions of the SPICE
client also made available to the community here:
http://spice-space.org/download/gtk/windows/ are also a bit dated and do
not include the plugin (SpiceX.dll).
MIME file SPICE and VNC support is in oVirt master for couple of weeks
now. This should work on all browsers with latest remote-viewer client.
Perhaps a plugin deployment page linked from the main ovirt landing page
would be a prudent way to deploy the plugin?
In any event a working SPICE Plugin for Firefox and newer SPICE Client
version under windows would be a very welcome sight indeed.
definitely.
Another alternative planned for 3.3 is SPICE HTML5, it has lots of
limitations, but it's purely browser-based solution.
I think one of the most frequently asked questions or gripes I see about
ovirt is around SPICE console issues and concerns.
indeed. And we'll have 3 solutions soon!:-)
Thanks,
michal
- DHC
On Wed, Apr 17, 2013 at 7:45 AM, Christophe Fergeau <cfergeau(a)redhat.com>wrote:
> Hi everyone,
>
> Lately I've been hacking on getting the spice-xpi plugin to work on
> Windows. This is the Firefox plugin that is used on Linux to implement
> the portal SPICE console.
>
> This work has now been merged upstream (
> http://cgit.freedesktop.org/spice/spice-xpi/ ), and I've pushed a
> scratch build using mingw available from
> http://koji.fedoraproject.org/koji/taskinfo?taskID=5265107 (this will go
> away in several days). Copying this dll + its dependencies to the
> C:\Program Files\Mozilla Firefox\plugins directory are enough to get
> a spice-xpi plugin to show up in about:plugins, and to then be able
> to start a SPICE client from the spice-xpi test page (
> http://teuf.fedorapeople.org/plugins/test.html ).
> The dependencies I had to copy are:
>
> gspawn-win32-helper-console.exe
> gspawn-win32-helper.exe
> iconv.dll
> libffi-6.dll
> libgcc_s_sjlj-1.dll
> libgio-2.0-0.dll
> libglib-2.0-0.dll
> libgmodule-2.0-0.dll
> libgobject-2.0-0.dll
> libgthread-2.0-0.dll
> libintl-8.dll
> libstdc++-6.dll
> pthreadGC2.dll
> zlib1.dll
>
> (I picked them from the various mingw-* fedora packages).
>
>
> The reason for this email is that to be usable from oVirt, some portal
> changes are needed as it currently only tries to use the spice-xpi plugin
> on Linux platforms.
> Another fuzzy bit is how to get this plugin to the users' machines...
>
>
> And that's about all I had to say in that email ;) Let me know if that's
> useful to oVirt, how you want to integrate this, ...
>
> Cheers,
>
> Christophe
>
> _______________________________________________
> Engine-devel mailing list
> Engine-devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>
>
_______________________________________________
Engine-devel mailing list
Engine-devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel