[SOLVED] qm terminal [vmid] results in nothing - no logs, no errors?

GarrettB

GarrettB

Well-Known Member
Proxmox Subscriber
Jun 4, 2018
105
16
58
Hi, need help troubleshooting a no-response behavior after opening an xterm.js window for a VM.

I created a new VM with Ubuntu 18.04 and selected settings like my other VMs:

  • I have "serial0: socket" and "sockets: 1" in the config file. I also changed the grub file to read "console=tty0 console=ttyS0,115200" and updated grub, rebooted, and qemu-guest-agent is installed, etc. Everything ordinary for my setups.
  • I can access VM via port 22 with Putty without problems.
  • I am having no issues on other VMs with the xterm.js access. Also, noVNC works okay and shows tty1 in the console screen.
  • I have inspected the browser's console and network responses...no errors. Browser console reads "xtermjs starting".
  • I attempted "qm terminal [vmid]" from the node and

Any suggestions on what to check next?

VM configuration:

agent: 1
bootdisk: scsi0
cores: 2
cpulimit: 1
ide2: none,media=cdrom
memory: 2048
name: Passbolt-U18
net0: virtio=5E:F7:9F:6E:CB:44,bridge=vmbr4,tag=4
numa: 0
ostype: l26
scsi0: MDADMvmimages:140/vm-140-disk-0.raw,size=10G,ssd=1
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=87331282-aff0-4e8f-8f90-4e61f4a5f323
sockets: 1
vmgenid: a5b360b1-55ed-46dd-b45f-1c548fecfeb3
#qmdump#map:scsi0:drive-scsi0:MDADMvmimages:raw:
 
Last edited:
can you post the complete vm config ?
 
Also, this shows in syslog after xterm.js launch attempt (no apparent errors):

Code: 
Apr 26 08:51:24 pve pvedaemon[18032]: <root@pam> successful auth for user 'root@pam'
Apr 26 08:51:42 pve pvedaemon[29399]: starting qemu termproxy UPID:pve:000072D7:0EEC53B3:5CC2FEDE:vncproxy:140:root@pam:
Apr 26 08:51:42 pve pvedaemon[7487]: <root@pam> starting task UPID:pve:000072D7:0EEC53B3:5CC2FEDE:vncproxy:140:root@pam:
Apr 26 08:51:43 pve pvedaemon[8965]: <root@pam> successful auth for user 'root@pam'
Apr 26 08:51:46 pve pvedaemon[7487]: <root@pam> end task UPID:pve:000072D7:0EEC53B3:5CC2FEDE:vncproxy:140:root@pam: OK
 
I just discovered after reading through dmesg again that grub was still showing ttys0 instead of ttyS0. although I'm sure I updated it, after running update-grub again and rebooting, I'm good to go.
 
You must log in or register to reply here.
Top Bottom