Comment 7 for bug 1682020

Hi Daniel,

I have checked impact of w/ and w/o -k option with different combinations of default locale configured in client os and guest os.

In case of RHEL image with default locale 'ja_JP' and client default locale set as 'ja_JP', I have noticed that with -k option, only one character was giving problem with Japanese keyboard whereas without -k option I couldn't enter 4 characters and also many other characters were displayed incorrectly.

Presently, -k option passed to qemu can be configured using 'vnc.keymap' parameter on nova compute node, but it's remain the same for all vms running on that particular compute host. If we allow to pass keymap parameter to boot api [1](specs are up for review), then a user can specify which keymap to be used during booting instance based on the keymap that he/she will configure in the client os (machine from where user will access the vm using vnc console). This way, I think user should be able to get better results.

Please let me know what do you think abouut it.

Thank you.

[1] : https://review.openstack.org/#/c/448830