Hi, Mike!
Actually, I can live with a single keyboard layout for now. Thus I
managed to get most of the keys of my keyboard to function correctly by
using the same map for QEMU/KVM and for the guest os (Oracle Linux8).
Exceptions are the "dead keys" such as ` ยด ^ ~
Any tips on solving this problem?
Regards,
Marcus Rocha
Michael Jumper escreveu:
On Fri, Jul 1, 2022 at 5:50 AM Nick Couchman <[email protected]
<mailto:[email protected]>> wrote:
On Thu, Jun 30, 2022 at 11:20 AM Marcus Rocha <[email protected]
<mailto:[email protected]>> wrote:
Hi there!
Any news here, or it is still not possible to configure, for
example, pt-br or br-abnt2 keyboards when accessing KVM VMs
using VNC connections?
If I recall correctly, VNC just uses standard keysyms, rather than
scancodes, to send keystrokes, which means that you shouldn't have
to do anything to change the keyboard layout through Guacamole.
Yes, this is true ... except for KVM, which emulates a hardware
keyboard. Unlike other VNC servers, the KVM VNC server has to be
configured to use a particular keyboard layout for proper translation
from keysym to scancode, and it will only be able to represent key
events for keys on that hardware keyboard regardless of what the VNC
client sends.
It's not really a Guacamole issue, though there are things that could
be done to Guacamole to make KVM happier (such as adding the same
keysym translation layer that we use in RDP). Regardless, it is
absolutely not possible for a VNC client to universally "just work"
with the KVM VNC server, as the KVM VNC server simply cannot represent
key events for keys that are not on the emulated hardware keyboard.
A better way to have proper keyboard support on a KVM-virtualized VM
would be to have that VM host a VNC server (or RDP or SSH) and connect
to that instead.
- Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
