[pve-devel] VNC console

Dominik Csapak d.csapak at proxmox.com
Fri Jun 1 10:50:06 CEST 2018

On 06/01/2018 10:40 AM, Gandalf Corvotempesta wrote:
> Il giorno ven 1 giu 2018 alle ore 10:37 Dominik Csapak
> <d.csapak at proxmox.com> ha scritto:
>> you can configure your system to automatically reattach/create (to) a
>> screen session
>> e.g. in ~/.profile
>> [ -z "$STY" ] && screen -Rd "work"
> I wasn't aware of this. This could be an interesting workaround, but
> as wrote previously,
> is still a workaround.
> IMHO, a real VNC (or something similiar that persists) is better.
> But isn't novnc supposed to be a vnc client implemented in html5 ? As
> VNC client, it should persist, acting like a physical console, not
> like a terminal.
> (in fact, there is no need to configure any serial terminal to use novnc)

there still has to be a vnc*server* somewhere, in our case
every time you start the vnc console (for host and container) from the 
web, we start a new (temporary) vnc server that connects to a virtual 
tty (and in case of container connects/creates a dtach session)

in qemu it is different, here the qemu process itself has a persistent 
vncserver to which we connect (this is outside of the guest)

you could of course connect to a ikvm supplied by your server directly,
most server-grade mainboards have such a feature (e.g. in the ipmi, 
idrac, hp ilo, etc)

it is technically possible to have the host shell also start
a dtach session, but i am not sure if we want this? what do my 
colleagues say to this?

More information about the pve-devel mailing list