--Apple-Mail=_A6AC4676-6E84-41E2-AFF2-D3EEAE5C3A78 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 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.
=20 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.
=20 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!:-)
=20 - DHC =20 =20 =20 On Wed, Apr 17, 2013 at 7:45 AM, Christophe Fergeau = <cfergeau@redhat.com> wrote: Hi everyone, =20 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. =20 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=3D5265107 (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: =20 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 =20 (I picked them from the various mingw-* fedora packages). =20 =20 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 =
on Linux platforms. Another fuzzy bit is how to get this plugin to the users' machines... =20 =20 And that's about all I had to say in that email ;) Let me know if =
Thanks, michal plugin that's
useful to oVirt, how you want to integrate this, ... =20 Cheers, =20 Christophe =20 _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel =20 =20 _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
--Apple-Mail=_A6AC4676-6E84-41E2-AFF2-D3EEAE5C3A78 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=iso-8859-1 <html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 18 Apr 2013, at 17:57, Dead Horse wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div><div><div>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.<br>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. (<a href="http://elmarco.fedorapeople.org/spice.cab" target="_blank">http://elmarco.fedorapeople.org/spice.cab</a>)</div></div></div></div></blockquote></div><div><blockquote type="cite"><div dir="ltr"><div><div><div> </div>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: <a href="http://spice-space.org/download/gtk/windows/" target="_blank">http://spice-space.org/download/gtk/windows/</a> are also a bit dated and do not include the plugin (SpiceX.dll).<br></div></div></div></blockquote><div>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.</div><div><br></div><blockquote type="cite"><div dir="ltr"><div><div> <br></div>Perhaps a plugin deployment page linked from the main ovirt landing page would be a prudent way to deploy the plugin?<br></div><div>In any event a working SPICE Plugin for Firefox and newer SPICE Client version under windows would be a very welcome sight indeed.<br></div></div></blockquote>definitely.</div><div>Another alternative planned for 3.3 is SPICE HTML5, it has lots of limitations, but it's purely browser-based solution.</div><div><br><blockquote type="cite"><div dir="ltr"><div> <br></div><div>I think one of the most frequently asked questions or gripes I see about ovirt is around SPICE console issues and concerns.<br></div></div></blockquote>indeed. And we'll have 3 solutions soon!:-)</div><div><br></div><div>Thanks,</div><div>michal<br><blockquote type="cite"><div dir="ltr"><div><br></div>- DHC<br><div><div><div><br> </div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 17, 2013 at 7:45 AM, Christophe Fergeau <span dir="ltr"><<a href="mailto:cfergeau@redhat.com" target="_blank">cfergeau@redhat.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi everyone,<br> <br> Lately I've been hacking on getting the spice-xpi plugin to work on<br> Windows. This is the Firefox plugin that is used on Linux to implement<br> the portal SPICE console.<br> <br> This work has now been merged upstream (<br> <a href="http://cgit.freedesktop.org/spice/spice-xpi/" target="_blank">http://cgit.freedesktop.org/spice/spice-xpi/</a> ), and I've pushed a<br> scratch build using mingw available from<br> <a href="http://koji.fedoraproject.org/koji/taskinfo?taskID=5265107" target="_blank">http://koji.fedoraproject.org/koji/taskinfo?taskID=5265107</a> (this will go<br> away in several days). Copying this dll + its dependencies to the<br> C:\Program Files\Mozilla Firefox\plugins directory are enough to get<br> a spice-xpi plugin to show up in <a href="about:plugins">about:plugins</a>, and to then be able<br> to start a SPICE client from the spice-xpi test page (<br> <a href="http://teuf.fedorapeople.org/plugins/test.html" target="_blank">http://teuf.fedorapeople.org/plugins/test.html</a> ).<br> The dependencies I had to copy are:<br> <br> gspawn-win32-helper-console.exe<br> gspawn-win32-helper.exe<br> iconv.dll<br> libffi-6.dll<br> libgcc_s_sjlj-1.dll<br> libgio-2.0-0.dll<br> libglib-2.0-0.dll<br> libgmodule-2.0-0.dll<br> libgobject-2.0-0.dll<br> libgthread-2.0-0.dll<br> libintl-8.dll<br> libstdc++-6.dll<br> pthreadGC2.dll<br> zlib1.dll<br> <br> (I picked them from the various mingw-* fedora packages).<br> <br> <br> The reason for this email is that to be usable from oVirt, some portal<br> changes are needed as it currently only tries to use the spice-xpi plugin<br> on Linux platforms.<br> Another fuzzy bit is how to get this plugin to the users' machines...<br> <br> <br> And that's about all I had to say in that email ;) Let me know if that's<br> useful to oVirt, how you want to integrate this, ...<br> <br> Cheers,<br> <br> Christophe<br> <br>_______________________________________________<br> Engine-devel mailing list<br> <a href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a><br> <a href="http://lists.ovirt.org/mailman/listinfo/engine-devel" target="_blank">http://lists.ovirt.org/mailman/listinfo/engine-devel</a><br> <br></blockquote></div><br></div> _______________________________________________<br>Engine-devel mailing list<br><a href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a><br>http://lists.ovirt.org/mailman/listinfo/engine-devel<br></blockquote></div><br></body></html> --Apple-Mail=_A6AC4676-6E84-41E2-AFF2-D3EEAE5C3A78--