x86: 0.968
graphic: 0.839
device: 0.836
semantic: 0.807
boot: 0.805
architecture: 0.800
vnc: 0.769
performance: 0.749
mistranslation: 0.740
network: 0.684
socket: 0.660
files: 0.651
PID: 0.632
user-level: 0.630
ppc: 0.599
permissions: 0.564
arm: 0.542
peripherals: 0.524
i386: 0.508
kernel: 0.473
debug: 0.469
hypervisor: 0.462
register: 0.431
risc-v: 0.410
VMM: 0.366
KVM: 0.198
TCG: 0.197
virtual: 0.179
assembly: 0.127
--------------------
x86: 0.971
user-level: 0.959
vnc: 0.929
virtual: 0.770
TCG: 0.188
hypervisor: 0.155
boot: 0.100
debug: 0.098
files: 0.038
KVM: 0.032
socket: 0.021
network: 0.020
kernel: 0.019
register: 0.019
device: 0.015
VMM: 0.014
PID: 0.009
semantic: 0.006
architecture: 0.005
risc-v: 0.002
assembly: 0.002
ppc: 0.002
performance: 0.002
peripherals: 0.002
i386: 0.001
permissions: 0.001
graphic: 0.001
arm: 0.001
mistranslation: 0.000

Incorrect en-us keymap in QEMU 2.11

I'm using the latest Arch Linux installation ISO as a live system and start QEMU with the following command:

$ qemu-system-x86_64 -enable-kvm -boot d -cdrom ~/isos/archlinux-2018.03.01-x86_64.iso -m 512 -vnc :0 -k en-us

Then I use Vinagre to connect to the guest system, boot the default bootloader option, and type the character '<' at the command prompt. The guest prints the character '>' instead of the '<' I typed.

I believe this is caused by the updated en-us keymap in QEMU 2.11. [1]

If I start QEMU with `-k en-gb` (or without the -k switch at all), I can type '<' and get the same character to appear on the guest's command line. The issue happens with the updated en-us keymap. It is also fixed if I replace /usr/share/qemu/keymaps/en-us with the old keymap file (before commit a7815faf).

This problem was originally reported against Packer because we were seeing '>' characters in place of '<' when using it with the QEMU builder. [2]

[1] https://github.com/qemu/qemu/commit/a7815faffb2bd594b92aa3542d7b799cc89c5414
[2] https://github.com/hashicorp/packer/issues/5769