Support for xterm.js console by default for specific vm.

[tlex]

Good day,

I've enabled a serial console on a few vm that support it on one of my hosts and I'm able to select and initiate a serial console session on them by selecting "xterm.js" in the right dropdown menu of the web gui but I would like to know if it is possible anyhow to make this the default view mode when accessing the console from the left "console" button like it is the case when accessing CT consoles or even host shell.
I understand the NoVnc will interact with the serial console as xterm.js does but the resolution is always blurry.
Would that be a feature request or is there anyway to force it in the vm config file ?

Thanks

 

[leesteken]

There is an option to set the default console under Datacenter > Options > Console Viewer. You can also change it in the configuration file. Does that not work for you?

 

[tlex]

I tried both changing the setting from the gui and directly in the datacenter.cfg file and that didn't change anything, the vm console falls back to novnc (when accessing the console from the left "console"button") where when I click the drop down console (right) and select xterm.js (that opens a new console window in xterm.js mode as expected)

 

[tlex]

So just to expose my "problem", I made a quick video.
As shown:

- "Xterm.js" is set as the default console mode at the Datacenter level.
- Containers (and host shell) consoles works as expected using xterm.js
- VM is not using xterm.js as the default mode (thats my issue)
- Xterm.js will only work when initiated from the right "console" menu

Any idea ?
https://www.youtube.com/watch?v=PgvuKog38CU

 

[leesteken]

I did not realize that you used the Console tab of the VM before your video. Maybe it is a bug that the Console tab does not use the default console or maybe it is designed this way? The same happens to me, but I never use the Console tab of the VM.

What happens if you don't go the the Console tab of the VM but press the Console button? (And don't use the menu of the Console button but press on the left or middle of the Console button?) Or when you right-click on the VM and then click the Console from that context menu? I expect both to use the default console you set (xterm.js).

 

[tlex]

I did not realize that you used the Console tab of the VM before your video. Maybe it is a bug that the Console tab does not use the default console or maybe it is designed this way? The same happens to me, but I never use the Console tab of the VM.

What happens if you don't go the the Console tab of the VM but press the Console button? (And don't use the menu of the Console button but press on the left or middle of the Console button?) Or when you right-click on the VM and then click the Console from that context menu? I expect both to use the default console you set (xterm.js).

Doing so will open noVnc as well sadly. The only way to start the console for a vm with xterm.js will be to right-click the right console button and select xterm.js (at least in my case !) - Right clicking the vm and then "console" works to open xterm.js. Thanks for that.
So the only way to get xterm.js to work is to have a popout window openned. the embedded console is not working with xterm.js as it is for ct / host.

 

[GFY]

I too am experiencing this. The default should be VNC for virtual machines and xterm for containers. This used to be the case prior to 8.

 

[calhoward]

I too am experiencing this. The default should be VNC for virtual machines and xterm for containers. This used to be the case prior to 8.

Any solution yet? +1 for same issue.

 

[mietz]

This is not for a specific vm, but it might be a starting point:

M

Post in thread 'Default Console Option has no effect ?'

Saturday at 12:00

I fixed this with a hacky tamper monkey script:

// ==UserScript==
// @name         Proxmox swap embedded console
// @version      1.0
// @description  Swap noVNC to xterm.js in Proxmox embedded console
// @match        *://*/
// @include      /^https:\/\/.*:8006\/#v.*:=node%2F.*:.*:=consolejs:$/
// @grant        none
// ==/UserScript==

(function() {
    'use strict';

    function modifyConsoleSource(div) {
            const iframe = div.querySelector('iframe');
            if (iframe && iframe.src) {
                const urlParams = new URLSearchParams(iframe.src.split('?')[1])...

• mietz