[Engine-devel] spice-xpi(firefox) plugin for Windows
Andrew Cathrow
acathrow at redhat.com
Fri May 10 17:01:06 UTC 2013
----- Original Message -----
> From: "David Jaša" <djasa at redhat.com>
> To: "Dead Horse" <deadhorseconsulting at gmail.com>
> Cc: engine-devel at ovirt.org, "Christophe Fergeau" <cfergeau at 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 at 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 at 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 at ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/engine-devel
> > >
> > >
> > >
> > > _______________________________________________
> > > Engine-devel mailing list
> > > Engine-devel at ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/engine-devel
> >
> >
> >
> >
> > _______________________________________________
> > Engine-devel mailing list
> > Engine-devel at 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 at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>
More information about the Engine-devel
mailing list