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). 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. I think one of the most frequently asked questions or gripes I see about ovirt is around SPICE console issues and concerns. - DHC On Wed, Apr 17, 2013 at 7:45 AM, Christophe Fergeau <cfergeau@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel