[pve-devel] Execute monitor command from remote?

Stefan Priebe - Profihost AG s.priebe at profihost.ag
Tue Jun 3 10:19:31 CEST 2014


Am 03.06.2014 10:14, schrieb Dietmar Maurer:
>>>   websocket
>>>                Opens an additional TCP listening port dedicated to VNC
>>>                Websocket connections.  By definition the Websocket port is
>>>                5700+display. If host is specified connections will only be
>>>                allowed from this host.  As an alternative the Websocket port
>>>                could be specified by using "websocket"=port.  TLS encryption
>>>                for the Websocket connection is supported if the
>>> required
>>
>> But then we have a tcp port open for each vm. Which might also "conflict" on
>> migration. I really like the current usage of a unix socket for VNC.
> 
> But we already solved that problem for SPICE, so it should be possible for VNC.
> 
> Anyways, this is not really important right now. Just want to show that the current
> approach is not really optional (useless encrypt/decrypt which wastes CPU power).

at which stage?

I've now changed the way it works in a new patchset. will post it.

Stefan



More information about the pve-devel mailing list