[SOLVED] PVE 5.1-46 update broke xterm.js


Feb 20, 2018
This morning, I updated my home server from PVE 5.1-43 to 5.1-46. Before the update, I had a handful of QEMU VMs that I configured serial sockets for so that I can use xterm.js (it's much faster when I'm on the go since I have a very restrictive bandwidth that noVNC can't quite make it through). They were working great, and I was really happy with the addition of xterm.

Now, since I upgraded to version 5.1-46 from the no-subscription repositories, my Proxmox server seems to be having issues recognizing the configuration of the QEMU serial sockets. In the hardware tab, I can see the serial ports listed (which was a new addition to the update, as they didn't show up on the GUI before), and they're all there. In /etc/pve/qemu-server/1000.conf (and the rest of the configuration files), the line "serial0: socket" is included.
But when I open the drop-down box on the console button, xterm.js is grayed out. I can still use the command line with "qm terminal 1000" and it opens the serial socket just fine, so everything is configured properly, it's just that the GUI xterm module is acting odd. I can, however, still use xterm.js to access the host server, which works fine, it's just a tad inconvenient.

Was there a change made to xterm.js? Is there a simple one-liner that can fix this? Am I just being dumb and broke something?

If it makes a difference, this Proxmox server was installed using the proxmox-ve_5.1-722cc488-1.iso disk and has simply been upgraded with "apt upgrade" since.

My package versions are:

proxmox-ve: 5.1-40 (running kernel: 4.13.13-6-pve)
pve-manager: 5.1-46 (running version: 5.1-46/ae8241d4)
pve-kernel-4.13.13-6-pve: 4.13.13-40
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-4-pve: 4.13.13-35
pve-kernel-4.13.13-2-pve: 4.13.13-33
pve-kernel-4.13.13-1-pve: 4.13.13-31
pve-kernel-4.13.8-3-pve: 4.13.8-30
pve-kernel-4.13.8-2-pve: 4.13.8-28
pve-kernel-4.13.8-1-pve: 4.13.8-27
pve-kernel-4.13.4-1-pve: 4.13.4-26
corosync: 2.4.2-pve3
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-common-perl: 5.0-27
libpve-guest-common-perl: 2.0-14
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-17
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-2
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-11
pve-cluster: 5.0-20
pve-container: 2.0-19
pve-docs: 5.1-16
pve-firewall: 3.0-5
pve-firmware: 2.0-3
pve-ha-manager: 2.0-5
pve-i18n: 1.0-4
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.9.1-8
pve-xtermjs: 1.0-2
qemu-server: 5.0-21
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.4-pve2~bpo9

An example of an affected configuration file (2001.conf to be specific) is:

bootdisk: scsi0
cores: 2
cpu: kvm64,flags=+pcid
ide2: local:iso/debian-9.2.1-amd64-DVD-1.iso,media=cdrom
memory: 1024
name: TestServer
net0: virtio=<<REDACTED>>,bridge=vmbr0
net1: virtio=<<REDACTED>>,bridge=vmbr1
numa: 0
onboot: 1
ostype: l26
scsi0: local-lvm:vm-2001-disk-1,discard=on,size=16G
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=<<REDACTED>>
sockets: 1
Oh, I didn’t even think to write a bug report yet! I thought I was just being dumb somehow.
The latest upgrades to qemu-server and pve-qemu-kvm fixed the issue immediately. Sorry to bother you!


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!