[pve-devel] Execute monitor command from remote?
Stefan Priebe - Profihost AG
s.priebe at profihost.ag
Tue Jun 3 10:08:34 CEST 2014
Am 03.06.2014 09:58, schrieb Dietmar Maurer:
>>> OK - but which advantage do we get
>>
>> You patch seem to break VNC when started via /etc/inetd.conf
>>
>> Also, simply using normal VNC features seems more correct to me.
>>
>>> beside we need to care about another
>>> patch while upgrading qemu versions?
>>
>> The idea is to send such patches to qemu project, so that they get merged into
>> the project.
>
> And it is still unclear to me if we should use the qemu websocket option?
>
> # man kvm
>
> 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.
Stefan
More information about the pve-devel
mailing list