Okay, great now if you want to set that as the default, so you don't have to
do that manually each time do the following:
ssh into the engine box as root.
engine-config -s ClientModeSpiceDefault=Plugin
That should default it to be plugin for all the VMs.
On Thu, Jul 21, 2016, at 02:14 PM, Alexander Wels wrote:
> On Thursday, July 21, 2016 01:58:05 PM Melissa Mesler wrote:
> > Yes, this is a workaround for us after upgrading to 4.0. I know it's
> > going away in 4.1 but this buys us some time.
> >
> > So the first option didn't work b/c like yous aid, it wasn't there. So
> > we did the second step and it still didn't seem to work. We even tried
> > restarting ovirt but that didn't help either. Any other ideas?
>
> Looking at the code it also set the default mode to 'native' instead of
> plugin. After you set the flag to true and restarted the engine, do you
> see the
> 'plugin' option when you right click on a running VM in webadmin and
> select
> console options? It should be under Console Invocation
>
> > On Thu, Jul 21, 2016, at 01:39 PM, Alexander Wels wrote:
> > > On Thursday, July 21, 2016 01:19:35 PM Melissa Mesler wrote:
> > > > Yes we are trying to get spice working on a thin client where
> > > > we can't
> > > > use virt-viewer. I just don't know the steps in the bugzilla to
> > > > accomplish it as it's not completely clear.
> > >
> > > Okay gotcha,
> > > Note in 4.1 this ability will be completely removed, the bugzilla is
> > > for cases where people need it in some kind of production environment.
> > >
> > > Assuming you can ssh into the machine that is running the engine
> > > (either HE or standard engine) as root:
> > >
> > > engine-config -s EnableDeprecatedClientModeSpicePlugin=true
> > >
> > > If that doesn't work because the option was not added to
engine-config
> > > (couldn't tell from reading the code). Try this:
> > >
> > > sudo su postgres
> > > --this will log you in as the postgres user
> > > psql -d engine
> > > --this will start psql connecing to the engine database. The
> > > default will be
> > > --engine if you didn't specify something else during engine-
> > > setup. psql -l
> > > --will list all the databases.
> > > update vdc_options set option_value=true where
> > > option_name='EnableDeprecatedClientModeSpicePlugin';
> > >
> > > > On Thu, Jul 21, 2016, at 01:14 PM, Alexander Wels wrote:
> > > > > On Thursday, July 21, 2016 01:08:49 PM Melissa Mesler wrote:
> > > > > > So I am trying to get spice working in ovirt 4.0. I found
the
> > > > > > following
> > > > > > solution:
> > > > > >
https://bugzilla.redhat.com/show_bug.cgi?id=1316560
> > > > >
> > > > > That bugzilla relates to the legacy spice.xpi FF plugin, and
> > > > > possibly
> > > > > some
> > > > > activex plugin for IE. The current way is the following:
> > > > >
> > > > > 1. Get virt-viewer for your platform.
> > > > > 2. Associated virt-viewer with .vv files in your browser.
> > > > > 3. Click the button, which will download the .vv file with the
> > > > > appropriate
> > > > > ticket.
> > > > > 4. The browser will launch virt-viewer with the .vv file as a
> > > > >
> > > > > parameter
> > > > >
> > > > > and it
> > > > > should just all work.
> > > > >
> > > > > > Where do you set
> > > > > > vdc_options.EnableDeprecatedClientModeSpicePlugin to
> > > > > > 'true'?? I see it says ENGINE_DB but what steps do
I follow to
> > > > > > do this?
> > > > > > Can someone help me?
> > > > > > _______________________________________________
> > > > > > Users mailing list
> > > > > > Users(a)ovirt.org
> > > > > >
http://lists.ovirt.org/mailman/listinfo/users