> > > > Everything needed, so launching remote-viewer is
> > > > just "remote-viewer /path/to/config.vv".
> > >
> > > If it's just what is needed to launch the viewer, why not stick to the
> > > url syntax?
> >
> > First, the info needed to launch is located on a fixed & well known
> > place on
Hi
On Wed, Dec 19, 2018 at 1:54 PM Gerd Hoffmann wrote:
>
> On Wed, Dec 19, 2018 at 11:44:07AM +0400, Marc-André Lureau wrote:
> > On Wed, Dec 19, 2018 at 11:13 AM Gerd Hoffmann wrote:
> > >
> > > Hi,
> > >
> > > > > Also: remote-viewer accepts config files. I'd suggest to write one,
> > >
On Wed, Dec 19, 2018 at 11:44:07AM +0400, Marc-André Lureau wrote:
> On Wed, Dec 19, 2018 at 11:13 AM Gerd Hoffmann wrote:
> >
> > Hi,
> >
> > > > Also: remote-viewer accepts config files. I'd suggest to write one, so
> > > > it is easy to restart remote-viewer. Also I would not use a temp
On Wed, Dec 19, 2018 at 11:13 AM Gerd Hoffmann wrote:
>
> Hi,
>
> > > Also: remote-viewer accepts config files. I'd suggest to write one, so
> > > it is easy to restart remote-viewer. Also I would not use a temp dir
> >
> > Where should it be written?
>
>
Hi,
> > Also: remote-viewer accepts config files. I'd suggest to write one, so
> > it is easy to restart remote-viewer. Also I would not use a temp dir
>
> Where should it be written?
/run/user/$uid/qemu/$vmname/remote-viewer.vv ?
> What should be the content of
> the .vv file?
Hi
On Tue, Aug 7, 2018 at 6:30 PM Gerd Hoffmann wrote:
>
> Hi,
>
> > > spice arguments over time. So if we want auto-launching of a remote app,
> > > I think it is preferrable to do it via extra args to the existing
> > > "-display spice" format. eg we could add a "client=yes|no" to control
>
On 07/08/2018 16:30, Gerd Hoffmann wrote:
>>>
>>>-display spice,client=yes
>> There is no -display spice, atm.
>>
>> However there is a -display vnc.
> That should not be there. Now that we have a deprecation process
> I should probably actually deprecate it in favor of -vnc.
>
>> It's a bit
Hi,
> > spice arguments over time. So if we want auto-launching of a remote app,
> > I think it is preferrable to do it via extra args to the existing
> > "-display spice" format. eg we could add a "client=yes|no" to control
> > launching the client
> >
> >-display spice,client=yes
>
>
Hi
On Tue, Aug 7, 2018 at 12:15 PM, Daniel P. Berrangé wrote:
> On Fri, Aug 03, 2018 at 07:36:14PM +0200, Marc-André Lureau wrote:
>> Add a new display backend that will configure Spice to allow a remote
>> client to control QEMU in a similar fashion as other display backend
>> like GTK.
>>
>>
On Fri, Aug 03, 2018 at 07:36:14PM +0200, Marc-André Lureau wrote:
> Add a new display backend that will configure Spice to allow a remote
> client to control QEMU in a similar fashion as other display backend
> like GTK.
>
> For this to work, we set up Spice server with a unix socket, and
>
On 08/03/2018 12:36 PM, Marc-André Lureau wrote:
Add a new display backend that will configure Spice to allow a remote
client to control QEMU in a similar fashion as other display backend
like GTK.
For this to work, we set up Spice server with a unix socket, and
register a VC chardev that will
Add a new display backend that will configure Spice to allow a remote
client to control QEMU in a similar fashion as other display backend
like GTK.
For this to work, we set up Spice server with a unix socket, and
register a VC chardev that will be exposed as Spice ports. A QMP
monitor is also
12 matches
Mail list logo
