I'm running into this in what I suspect is the same situation as Michal Nowak: openQA. But in Fedora. openQA (well, its test runner, os-autoinst) works by running virtual machines and interacting with them over VNC. It seems that with qemu 2.11, typing certain characters doesn't work right, where it worked fine with 2.10. The case I ran into is the < case: when os-autoinst intends to type a < (which it does by sending the keysym for shift and then the keysym 60, for <), it winds up typing a > . This winds up causing os-autoinst's test suite to fail when attempting to build the package on Fedora Rawhide. The test suite passes on Fedora 27 (qemu 2.10).
Aha. This looks like my bug!
I'm running into this in what I suspect is the same situation as Michal Nowak: openQA. But in Fedora. openQA (well, its test runner, os-autoinst) works by running virtual machines and interacting with them over VNC. It seems that with qemu 2.11, typing certain characters doesn't work right, where it worked fine with 2.10. The case I ran into is the < case: when os-autoinst intends to type a < (which it does by sending the keysym for shift and then the keysym 60, for <), it winds up typing a > . This winds up causing os-autoinst's test suite to fail when attempting to build the package on Fedora Rawhide. The test suite passes on Fedora 27 (qemu 2.10).
The qemu command in my test is:
/usr/bin/ qemu-system- i386 -serial file:serial0 -soundhw ac97 -vga cirrus -m 1024 -netdev user,id=qanet0 -device virtio- net,netdev= qanet0, mac=52: 54:00:12: 34:56 -device ide-drive, drive=hd1, serial= 1 -drive file=raid/ l1,cache= unsafe, if=none, id=hd1, format= qcow2 -drive media=cdrom, if=none, id=cd0, format= raw,file= /builddir/ build/BUILD/ os-autoinst- 25191d50d54eade d10b6b26199bb98 6728dcd5c2/ t/data/ /Core-7. 2.iso -device ide-cd,drive=cd0 -boot once=d, menu=on, splash- time=5000 -smp 1 -no-shutdown -vnc :90,share= force-shared -qmp unix:qmp_ socket, server, nowait -monitor unix:hmp_ socket, server, nowait -S -monitor telnet: 127.0.0. 1:15222, server, nowait
note there doesn't appear to be any explicit keyboard map setting there.