[Engine-devel] spice-xpi(firefox) plugin for Windows
--tsOsTdHNUZQcU9Ye Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 --tsOsTdHNUZQcU9Ye Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) iEYEARECAAYFAlFumXkACgkQJKRp+3pW945+vwCglgqxiHD3g6EOC12U9Ydg8pVS kmMAoIRXM5MepmgnvK+UJMF1rjiVJ4r/ =QcGM -----END PGP SIGNATURE----- --tsOsTdHNUZQcU9Ye--
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
--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--
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@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@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
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
--=-Kdkjr0SX9cwEKKRzqcoE Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, writing from top of my head so this may not be 100 % accurate: Dead Horse p=C3=AD=C5=A1e v P=C3=A1 10. 05. 2013 v 11:38 -0500:
I played a bit with the MIME and browsers. =20 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" =20 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?
I guess that this exception should apply just for RDP because {virt,remote}-viewer supports both spice and vnc AFAIK.
=20 =20 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.=20
Given ^^^ and that another vnc client would need to add the .vv file format support, I don't think that it's a good idea
I have spice certificates and ssl disabled as well so that cannot get in the way.
Unlike spice and vnc, rdp server is not provided by qemu but by VM itself, so in order to make it work, engine must learn VM IP address from RHEV Agent (so RHEV Agent service must be up'n'running in the VM) and the VM must be configured to accept incoming RDP connections. Because {virt,remote}-viewer doesn't support RDP (AFAIK) and no other client has support for .vv files, I don't think that they should be generated for rdp connection so if engine indeed generates the files, that sound like a bug for me (for the time being, till {virt,remote}-viewer gains RDP support or some rdp client gets .vv file format support). David
=20 =20 Any quick pointers on actually getting RDP to work or the connection files to work with a local remote-viewer or vnc client? =20 =20 - DHC =20 =20 =20 On Fri, Apr 19, 2013 at 3:08 AM, Michal Skrivanek <michal.skrivanek@redhat.com> wrote: =20 On 18 Apr 2013, at 17:57, Dead Horse wrote: =20 > 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) >=20 > 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). >=20 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 =20 >=20 >=20 > Perhaps a plugin deployment page linked from the main ovirt > landing page would be a prudent way to deploy the plugin? >=20 > In any event a working SPICE Plugin for Firefox and newer > SPICE Client version under windows would be a very welcome > sight indeed. >=20 definitely. Another alternative planned for 3.3 is SPICE HTML5, it has lots of limitations, but it's purely browser-based solution. =20 >=20 >=20 > I think one of the most frequently asked questions or gripes > I see about ovirt is around SPICE console issues and > concerns. >=20 indeed. And we'll have 3 solutions soon!:-) =20 =20 Thanks, michal =20 >=20 >=20 > - DHC >=20 >=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=3D52= 65107 (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 plugin > 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 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 >=20 > _______________________________________________ > Engine-devel mailing list > Engine-devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel =20 =20 =20 =20 _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
--=20 David Ja=C5=A1a, RHCE SPICE QE based in Brno GPG Key: 22C33E24=20 Fingerprint: 513A 060B D1B4 2A72 7F0D 0278 B125 CD00 22C3 3E24 --=-Kdkjr0SX9cwEKKRzqcoE Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Disposition: attachment; filename="smime.p7s" Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMdTCCBjQw ggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0 Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDE1NVoX DTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy dENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcN AQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOrlr6KMoOMpohBllVHrdRvEg/q6r8jR+EK 75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSMzR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC +y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxD z2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSDkOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr /+N2JLKutIxMYqQOJebr/f/h5t95m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0w ggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFc fH6WNU7y1LhRgjAfBgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRa MFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYh aHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6 Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5j b20vc2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0 dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cu c3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqDCH14qywG XLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy6QMVQjbbMXlt UfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPIzKKR9tQW8gGK+2+R HxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKfKSETEPrHh7p5shuuNktv sv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HORz9v3vQwR4e3ksLc2JZOAFK+s sS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9sIPP7ON0fz095HdThKjiVJe6vofq +n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCieuoBJ9OlqmsVWQvifIYf40dJPZkk9YgGT zWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7tw1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGq Up/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQG2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb1 9mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIGOTCCBSGg AwIBAgIDBl1jMA0GCSqGSIb3DQEBBQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcN MTMwNDEwMTE0ODI4WhcNMTQwNDEwMTM1MDM0WjBXMRkwFwYDVQQNExAxUktWVnliSEdDZnRMWjY3 MRkwFwYDVQQDDBBkamFzYUByZWRoYXQuY29tMR8wHQYJKoZIhvcNAQkBFhBkamFzYUByZWRoYXQu Y29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAx8unM64NLnlRZujXHb0ilCaqc7KB r1MwlyCtOWAyH4M/24zvfyRQyTz4ZkHd1sMeewJ5ap1/128hLSqMY/6So5yhL6UlK3nM1r9H9PTz CiPEMZmDazIzMb/Mt/4N3kkJBLpWPFRB5aB+COcex7a4dlmnUJASVWkVwvHRmfa06anME7DTccV5 cV95FKqoRUXawopdu5W2NhailCtbQJAbMIGf9FpH+J98swAsVHdvjZkSDnZcoQIPHzoPrEBawb7C vsmCe8p7pv5Dxtx3T47FdAXJiO9u+QJkaBFjfiA9ywN8fFo3Q/Jr4vl6WqEr1SyQjgL9/dWeQSYI 8LzByChnXQIDAQABo4IC1jCCAtIwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYI KwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBQ5AqZ3fyU5HOme+iF4KA3f8RxHPjAfBgNVHSME GDAWgBRTcu2SnODaywFcfH6WNU7y1LhRgjAbBgNVHREEFDASgRBkamFzYUByZWRoYXQuY29tMIIB TAYDVR0gBIIBQzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6Ly93 d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENl cnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1ZWQg YWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRoZSBT dGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3Nl IGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYGA1UdHwQv MC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUF BwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3Mx L2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3Vi LmNsYXNzMS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29t LzANBgkqhkiG9w0BAQUFAAOCAQEArlvH1bAdnpLvyeMQzPtJYs65ur7cpYnrxrIZ3P/r0F7juzIU fb1S+M9sYBhalmBoZQMySlVveDYHUHPDsNJQtqUzYAJMbVTdRtviCSq3wmYtG/VJOOif11gM25u4 HcgXVuhF3di5G0CHwAIx0mjUi7fPJ3WMeFKWp550ZqpbFK/i9A5fJGfHk3MfXOhAu7vkEEjJY+gA BpFqvk134+30mP4KoXfNGZpekWvj6lS/tfaxuuSTusPcY0yIGGtJqqFtL1tRlTIoaDGiok5O0k6W pMFPtm+dGnOyKT4HQMFCaAgBOVCQFDYthuGlnUlJOP/BheuvaMfwgIqM4ir+DIqOyjGCAhswggIX AgEBMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh c3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwZdYzAJBgUrDgMCGgUAoF0wGAYJ KoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNTEwMTY1MzUzWjAjBgkq hkiG9w0BCQQxFgQU0PK22KeH48c+pq8i3njccw9KvcIwDQYJKoZIhvcNAQEBBQAEggEAgL/gKmgW YcsibkXnKcpLDtMWezCrwZ7I3Ur9lhgo/CT4CbEtnFyi2w6pO1cWEhU13DsTUahN9Jq4B+92rDUz izPwESTIA27IDxyDn0S4dbHlMgkIMmC4YcCr3CkhTGCaxeuZlPcNoAnFD63SiI33uWDNx/GT0A19 bgOn4PBuHuR5nPaT6xFPloTUQgcXCtzIYFtj/SzskZB4Z/BW2nl4YuTRdmXItfsARr6NnlhizOCp KPcmT5jdcHOkcOQSpUy2i+tnccple63SCnXqgGp2T4GAr5vKW5s5zmGZw8pJqCanMwwbUuSNQJ55 aSuxbhmCgIfZVi7WRDaa318Zcj8JKQAAAAAAAA== --=-Kdkjr0SX9cwEKKRzqcoE--
----- Original Message -----
From: "David Jaša" <djasa@redhat.com> To: "Dead Horse" <deadhorseconsulting@gmail.com> Cc: engine-devel@ovirt.org, "Christophe Fergeau" <cfergeau@redhat.com> Sent: Friday, May 10, 2013 12:53:53 PM Subject: Re: [Engine-devel] spice-xpi(firefox) plugin for Windows
Hi,
writing from top of my head so this may not be 100 % accurate:
Dead Horse píše v Pá 10. 05. 2013 v 11:38 -0500:
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?
I guess that this exception should apply just for RDP because {virt,remote}-viewer supports both spice and vnc AFAIK.
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.
Given ^^^ and that another vnc client would need to add the .vv file format support, I don't think that it's a good idea
I have spice certificates and ssl disabled as well so that cannot get in the way.
Unlike spice and vnc, rdp server is not provided by qemu but by VM itself, so in order to make it work, engine must learn VM IP address from RHEV Agent (so RHEV Agent service must be up'n'running in the VM) and the VM must be configured to accept incoming RDP connections.
Because {virt,remote}-viewer doesn't support RDP (AFAIK) and no other client has support for .vv files, I don't think that they should be generated for rdp connection so if engine indeed generates the files, that sound like a bug for me (for the time being, till {virt,remote}-viewer gains RDP support or some rdp client gets .vv file format support).
VV's are only created for Spice and VNC not for RDP today.
David
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@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@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 > > > > _______________________________________________ > Engine-devel mailing list > Engine-devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
--
David Jaša, RHCE
SPICE QE based in Brno GPG Key: 22C33E24 Fingerprint: 513A 060B D1B4 2A72 7F0D 0278 B125 CD00 22C3 3E24
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
On May 10, 2013, at 18:53 , David Jaša <djasa@redhat.com> wrote:
Hi,
writing from top of my head so this may not be 100 % accurate:
Dead Horse píše v Pá 10. 05. 2013 v 11:38 -0500:
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?
I guess that this exception should apply just for RDP because {virt,remote}-viewer supports both spice and vnc AFAIK. RDP is being worked on by Franta right now. It should make it for 3.3...
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.
Given ^^^ and that another vnc client would need to add the .vv file format support, I don't think that it's a good idea
I have spice certificates and ssl disabled as well so that cannot get in the way.
Unlike spice and vnc, rdp server is not provided by qemu but by VM itself, so in order to make it work, engine must learn VM IP address from RHEV Agent (so RHEV Agent service must be up'n'running in the VM) and the VM must be configured to accept incoming RDP connections.
Because {virt,remote}-viewer doesn't support RDP (AFAIK) and no other client has support for .vv files, I don't think that they should be generated for rdp connection so if engine indeed generates the files, that sound like a bug for me (for the time being, till {virt,remote}-viewer gains RDP support or some rdp client gets .vv file format support).
David
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@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@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
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
--
David Jaša, RHCE
SPICE QE based in Brno GPG Key: 22C33E24 Fingerprint: 513A 060B D1B4 2A72 7F0D 0278 B125 CD00 22C3 3E24
participants (5)
-
Andrew Cathrow -
Christophe Fergeau -
David Jaša -
Dead Horse -
Michal Skrivanek