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 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?
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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
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. 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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
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? 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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
That worked! Thank you!!! 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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Thursday, July 21, 2016 02:38:41 PM Melissa Mesler wrote:
That worked! Thank you!!!
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@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users
On 21 Jul 2016, at 21:43, Alexander Wels <awels@redhat.com> wrote:
On Thursday, July 21, 2016 02:38:41 PM Melissa Mesler wrote:
That worked! Thank you!!!
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.
Thank you Alex for jumping in Additional note - the 4.0 distribution of spice components does not contain the XPI/ActiveX anymore, so in case you want to use the deprecated way you need to make sure you install the latest 3.6 version of ActiveX/XPI from 3.6 channels/repos Melissa, may I ask what is the thin client you use? Does the vendor have a plan for future? Another non-intrusive option is to use the web-based console clients….which are of varying quality though, so not a feasible replacement in many cases. Thanks, michal
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@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
To be able to use the .vv file, virt-viewer 2.0-8 is required and it can't be found in CentOS 7 repos. CentOS 6 repos contain 2.0-14 version however. Any info about when will the required version land in the CentOS 7 repositories? TIA, Ivan Original Message From: Michal Skrivanek Sent: Friday, July 22, 2016 11:53 To: Alexander Wels; Melissa Mesler Cc: Users@ovirt.org List Subject: Re: [ovirt-users] Spice in 4.0
On 21 Jul 2016, at 21:43, Alexander Wels <awels@redhat.com> wrote:
On Thursday, July 21, 2016 02:38:41 PM Melissa Mesler wrote:
That worked! Thank you!!!
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.
Thank you Alex for jumping in Additional note - the 4.0 distribution of spice components does not contain the XPI/ActiveX anymore, so in case you want to use the deprecated way you need to make sure you install the latest 3.6 version of ActiveX/XPI from 3.6 channels/repos Melissa, may I ask what is the thin client you use? Does the vendor have a plan for future? Another non-intrusive option is to use the web-based console clients….which are of varying quality though, so not a feasible replacement in many cases. Thanks, michal
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@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 28 Jul 2016, at 13:07, Ivan Bulatović <combuster@gmail.com> wrote:
To be able to use the .vv file, virt-viewer 2.0-8 is required and it can't be found in CentOS 7 repos. CentOS 6 repos contain 2.0-14 version however. Any info about when will the required version land in the CentOS 7 repositories?
It is going to be fixed in the final 4.0.2 build by a proper fix of https://bugzilla.redhat.com/show_bug.cgi?id=1285883 You can change it for the timebeing in engine-config’s RemoteViewerSupportedVersions option Thanks, michal
TIA,
Ivan Original Message From: Michal Skrivanek Sent: Friday, July 22, 2016 11:53 To: Alexander Wels; Melissa Mesler Cc: Users@ovirt.org List Subject: Re: [ovirt-users] Spice in 4.0
On 21 Jul 2016, at 21:43, Alexander Wels <awels@redhat.com> wrote:
On Thursday, July 21, 2016 02:38:41 PM Melissa Mesler wrote:
That worked! Thank you!!!
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.
Thank you Alex for jumping in Additional note - the 4.0 distribution of spice components does not contain the XPI/ActiveX anymore, so in case you want to use the deprecated way you need to make sure you install the latest 3.6 version of ActiveX/XPI from 3.6 channels/repos
Melissa, may I ask what is the thin client you use? Does the vendor have a plan for future? Another non-intrusive option is to use the web-based console clients….which are of varying quality though, so not a feasible replacement in many cases.
Thanks, michal
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@ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Thu, Jul 21, 2016 at 9:19 PM, Melissa Mesler <melissa@justmelly.com> 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.
I don't know the details of this thin client, but I suggest requesting it to be supported from the virt-viewer team. Perhaps it's not such a big deal. Y.
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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
We are using the 10Zig clients. We talked to support at 10Zig about the future of these thin clients and even though they are Red Hat certified thin clients, they are dropping spice support and not moving to virt- viewer. We are more than happy to help someone with the development of these in any way as we are kinda stuck and have a lot of these in our inventory. On Fri, Jul 22, 2016, at 07:06 AM, Yaniv Kaul wrote:
On Thu, Jul 21, 2016 at 9:19 PM, Melissa Mesler <melissa@justmelly.com> 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.
I don't know the details of this thin client, but I suggest requesting it to be supported from the virt-viewer team. Perhaps it's not such a big deal. Y.
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@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (5)
-
Alexander Wels -
Ivan Bulatović -
Melissa Mesler -
Michal Skrivanek -
Yaniv Kaul