[SOLVED] Can't login to KVM guest through console (noVNC doesn't accept symbols)

P

ppo

Renowned Member
Aug 6, 2012
49
0
71
The latest PVE version 5.2 is installed.
I've moved several KVMs from older 3.4 server and realized that can't login to any: "Login incorrect".
Password has "@" symbol so I tried to type it in Login prompt instead of Password prompt and got "2".
Non of symbols are worked.
I have default Eng-Us settings everywhere, on local computer and on PVE host.
NoVNC console on PVE 3.4 doesn't have this issue.
How to deal with this?
 
The quick hack is to login is to use the QEMU monitor and sendkey - this will work but will not solve your problem, just circumvent it for now.
 
Thanks for you answer. It works: when I have to pass "@" symbol in password I go to monitor and type "sendkey shift-2".
However what is the sense of strong passwords if you can't directly use them where they expected to be used?
Is it existing bug somewhere?
 
Last edited:
ppo said:
Thank for you answer. It works: when I have to pass "@" symbol in password I go to monitor and type "sendkey shift-2".
However what is the sense of strong passwords if you can't directly use them where they expected to be used?
Click to expand...

Sure, it's not optimal, but it works. I'd also suggest to use "real" remote access via RDP or SSH. PVE remote console is not safe in the sense that all people that have PVE access to the console of the VM can access it simultaneously, so one person logs in and goes e.g. to the toilet without locking the VM (only your host you're accessing from) and the other person can sneak in.

ppo said:
Is it existing bug somewhere?
Click to expand...

Maybe ... there are similar entries:

https://bugzilla.proxmox.com/buglist.cgi?quicksearch=vnc
 
ppo said:
I have default Eng-Us settings everywhere, on local computer and on PVE host.
Click to expand...
do you have really English as setting or 'default' ? (in vm config and in the datacenter config)
also which browser/client os do you use?

does anything pop up in the console of the browser?
 
dcsapak said:
do you have really English as setting or 'default' ? (in vm config and in the datacenter config)
also which browser/client os do you use?

does anything pop up in the console of the browser?
Click to expand...

Code: 
uname -a
Linux 4.13.0-46-generic #51-Ubuntu SMP Tue Jun 12 12:36:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

cat /etc/debian_version
stretch/sid

lsb_release -a
No LSB modules are available.
Distributor ID: Kubuntu
Description:    Kubuntu 17.10
Release:        17.10
Codename:       artful

Firefox Quantum 61.0.1 (64 bit)
pve_console_1.png
pve_console_2.png
pve_console_3.png
On the last screenshot I actually hold Shift and press 1-2-3-4, i.e no symbol support.
 
dcsapak said:
do you have really English as setting or 'default' ? (in vm config and in the datacenter config)
also which browser/client os do you use?

does anything pop up in the console of the browser?
Click to expand...
Hi,
I see similiar. With an linux-client the keyboard work well, but on an win-10 client the keyboard don't fit.
z and y are swapped and special characters are not typable.
This happens on win10 with different browsers (firefox, edge and chrome).
In datacenter is'nt any language defined, but i've set it without luck.

Udo
 
please try to have datacenter config and vm keyboard config to 'default' (you need to shutdown and start the vm again for this to be set) and then try again
if both is set to default, the keyboard layout of the guest should be set
 
dcsapak said:
please try to have datacenter config and vm keyboard config to 'default' (you need to shutdown and start the vm again for this to be set) and then try again
if both is set to default, the keyboard layout of the guest should be set
Click to expand...
I've set keyboard layout to "default" and started VM (it was stopped).
It didn't help.
 
mhmm... weird, it works here (debian 9 with chrome 69/firefox 62), what is your 'pveversion -v' ?
 
Code: 
pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.17-1-pve)
pve-manager: 5.2-1 (running version: 5.2-1/0fcd7879)
pve-kernel-4.15: 5.2-1
pve-kernel-4.15.17-1-pve: 4.15.17-9
corosync: 2.4.2-pve5
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-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-31
libpve-guest-common-perl: 2.0-16
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-23
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-18
pve-cluster: 5.0-27
pve-container: 2.0-23
pve-docs: 5.2-3
pve-firewall: 3.0-8
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-5
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-5
qemu-server: 5.0-26
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.8-pve1~bpo9
 
dcsapak said:
please upgrade to a current version, there was a big novnc upgrade
Click to expand...
Should I restart server updater dist-upgrade?
Code: 
pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.17-1-pve)
pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
pve-kernel-4.15: 5.2-10
pve-kernel-4.15.18-7-pve: 4.15.18-26
pve-kernel-4.15.17-1-pve: 4.15.17-9
corosync: 2.4.2-pve5
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-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-40
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-30
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-2
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-28
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-36
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.11-pve1~bpo1
 
In order to use the new kernel (which contains quite some security fixes as well) you need to restart.

For testing the novnc version and whether it helps your problem restarting pveproxy should be enough

If in doubt - restart!
 
I've tested on laptop with Windows and console accepts symbols.
I suspect this is combination of my current setup on working place, just strange that it works on PVE 3.x and doesn't on 5.2.
 
You must log in or register to reply here.
Top Bottom