[pve-devel] Execute monitor command from remote?

[Alexandre DERUMIER]

>>And it is still unclear to me if we should use the qemu websocket option?

I don't known if we can mix both websocket and classic vnc socket ?

also, websocket listen on tcp, do we want to listen on 127.0.0.1, then use a netcat|socat when we the console is launched ?


also, novnc and firefox wss, for self signed certificate, need to manual register the ca certificate, for each wss://hostname+port combination.

So, I think best way is to handle wss in pveproxy, like this the ca certificate is already ok. (and we just need to open 8006 port outside)


----- Mail original ----- 

De: "Dietmar Maurer" <dietmar at proxmox.com> 
À: "Stefan Priebe - Profihost AG" <s.priebe at profihost.ag> 
Cc: pve-devel at pve.proxmox.com 
Envoyé: Mardi 3 Juin 2014 09:58:29 
Objet: Re: [pve-devel] Execute monitor command from remote? 

> > 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 


_______________________________________________ 
pve-devel mailing list 
pve-devel at pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel