Author: Stephen Finucane <sfinu...@redhat.com>
Date: Fri Jul 14 17:00:27 2017 +0100
conf: Deprecate 'keymap' options
Defining the 'keymap' option in libvirt results in the '-k' option being
passed through to QEMU . This QEMU option has some uses, primarily
for users interacting with QEMU via stdin on the text console. However,
for users interacting with QEMU via VNC or Spice, like nova users do, it
is strongly recommended to never add the "-k" option. Doing so will
force QEMU to do keymap conversions which are known to be lossy. This
disproportionately affects users with non-US keyboard layouts, who would
be better served by relying on the guest OS to manage this. Users should
instead rely on their clients and guests to correctly configure this.
This is the second part of the three part deprecation cycle for these
options. At this point, they are retained but deprecated them and their
defaults modified to be unset. This allows us to warn users with libvirt
hypervisors that have configured the options about the pitfalls of the
option and give them time to prepare migration strategies, if necessary.
A replacement option is added to the VMWare group to allow us to retain
this functionality for that hypervisor. Combined with the above, this
will allow us to remove the options in a future release.
** Changed in: nova
Status: In Progress => Fix Released
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Remove nova default keymap option for qemu-kvm (deprecated)
Status in OpenStack Compute (nova):
Status in OpenStack Compute (nova) pike series:
Nowdays, qemu-kvm default keymap option -k en-us, or any keymap option
In OpenStack it renders the web console access to vm unsuable even
with the proper keymap in nova.conf. For exapmle the use of 'Alt-Gr +
key' combination in French, Belgium, spanish, or alike keyboard is not
working, this can be problematic for hard passwords.
Using the linked patch and removing/commenting the keymap options in
nova.conf, makes everything working again (depending on the NoVnc
version which might be patched also on previous ones).
So maybe by default the nova.conf should now comment/remove this
option and we need to remove the default option in the nova code.
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp