summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/105/graphic/1754295
blob: ad08b049d16fb8b2bf849a1168955ca366720520 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
graphic: 0.839
device: 0.836
semantic: 0.807
boot: 0.805
instruction: 0.771
vnc: 0.769
mistranslation: 0.740
network: 0.684
socket: 0.660
other: 0.250
KVM: 0.198
assembly: 0.127

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