[pve-devel] Execute monitor command from remote?

[Alexandre DERUMIER]

By the way, another possibility, maybe we could simply add an option in vm config to use novnc or java applet.

( vncconsole: java|html5 )

could be change dynamicaly with qmp "change vnc ..." on vm config update.


This is the same in ovirt, only 1 vnc console type is allowed at the same time.
http://www.ovirt.org/Features/noVNC_console
http://www.ovirt.org/images/2/22/ConsoleOptions_noVNC.png



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

De: "Alexandre DERUMIER" <aderumier at odiso.com> 
À: "Stefan Priebe" <s.priebe at profihost.ag> 
Cc: pve-devel at pve.proxmox.com 
Envoyé: Mardi 3 Juin 2014 03:51:19 
Objet: Re: [pve-devel] Execute monitor command from remote? 

>>Might be possible do you want to hardcode mode VNC_AUTH_VNC as a second 
>>mode? So the first is configurable and the second hardcoded? 

I really don't known. I need to read the vnc protocol documentation. 

Does vnc handle authentification protocol negocitiation ? 



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

De: "Stefan Priebe" <s.priebe at profihost.ag> 
À: "Dietmar Maurer" <dietmar at proxmox.com> 
Cc: pve-devel at pve.proxmox.com, "Alexandre DERUMIER" <aderumier at odiso.com> 
Envoyé: Lundi 2 Juin 2014 21:53:04 
Objet: Re: [pve-devel] Execute monitor command from remote? 

Hi Alexandre, 

Am 02.06.2014 17:51, schrieb Dietmar Maurer: 
>>>> But it does not in qemu. It's an enum in the code supporting only one 
>>>> way. I can't change it. 
>>> 
>>> What is the problem exactly? 
>> 
>> Qemu does not support multiple author at once. It only supports changing auth 
>> type with monitor command that's what i'm using. 
> 
> Also, It seems quite easy to support multiple auth. The server just needs to send all supported auth 
> modes in 
> 
> ui/vnc.c method protocol_version() 
> 
> something like: 
> 
> } else { 
> VNC_DEBUG("Telling client we support auth %d\n", vs->auth); 
> vnc_write_u8(vs, 2); /* num auth */ 
> vnc_write_u8(vs, vs->auth); 
> vnc_write_u8(vs, VNC_AUTH_VNC); 
> vnc_read_when(vs, protocol_client_auth, 1); 
> vnc_flush(vs); 
> } 
> 
> requires further modifications in protocol_client_auth() ... 
> 

Might be possible do you want to hardcode mode VNC_AUTH_VNC as a second 
mode? So the first is configurable and the second hardcoded? 

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