Bug 1413938 - Turn on Caps-Lock in keyboard, but can't input uppercase characters in win2016/rhel6.9 guests with qemu cli "-device usb-kbd"
Summary: Turn on Caps-Lock in keyboard, but can't input uppercase characters in win201...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.9
Hardware: x86_64
OS: Windows
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Gerd Hoffmann
QA Contact: hachen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-17 11:41 UTC by xianwang
Modified: 2017-12-06 12:43 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 12:43:20 UTC
Target Upstream Version:


Attachments (Terms of Use)
usb-kbd (98.65 KB, image/png)
2017-01-17 11:41 UTC, xianwang
no flags Details

Description xianwang 2017-01-17 11:41:48 UTC
Created attachment 1241681 [details]
usb-kbd

Description of problem:
Boot a win2016 vm with qemu cli "-device usb-kbd",then turn on Caps-Lock in keyboard, but can't input uppercase characters,it seems input "\" to vm.

Version-Release number of selected component (if applicable):
Host:
2.6.32-682.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.500.el6.x86_64
Guest:
win2016
virtio-win.iso.el6

How reproducible:
100%

Steps to Reproduce:
1.Boot a guest with following qemu cli:
/usr/libexec/qemu-kvm \
    -name 'avocado-vt-vm1' \
    -machine pc  \
    -nodefaults  \
    -vga qxl \
    -device ich9-usb-ehci1,id=usb1,addr=1d.7,multifunction=on,bus=pci.0 \
    -device ich9-usb-uhci1,id=usb1.0,multifunction=on,masterbus=usb1.0,addr=1d.0,firstport=0,bus=pci.0 \
    -drive id=drive_image1,if=none,aio=native,cache=none,format=qcow2,file=/root/win2016-64-virtio.qcow2 \
    -device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,bus=pci.0,addr=04 \
    -drive id=drive_data1,if=none,aio=native,cache=none,format=qcow2,file=/root/data1.qcow2 \
    -device virtio-blk-pci,id=data1,drive=drive_data1,bus=pci.0,addr=05 \
    -device virtio-net-pci,mac=9a:e3:e4:e5:e6:e7,id=idY87fGi,vectors=4,netdev=idjQ51hm,bus=pci.0,addr=06 \
    -netdev tap,id=idjQ51hm,vhost=on,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown \
    -m 2048 \
    -smp 2,maxcpus=2,cores=1,threads=1,sockets=2  \
    -cpu host \
    -drive id=drive_cd1,if=none,snapshot=off,aio=native,cache=none,media=cdrom,file=/root/en_windows_server_2016_x64_dvd_9327751.iso \
    -device ide-drive,id=cd1,drive=drive_cd1,bootindex=1,bus=ide.0,unit=0 \
    -drive id=drive_virtio,if=none,snapshot=off,aio=native,cache=none,media=cdrom,file=/root/virtio-win.iso.el6 \
    -device ide-drive,id=virtio,drive=drive_virtio,bootindex=2,bus=ide.1,unit=1 \
    -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9 \
    -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1  \
    -spice seamless-migration=on,port=5901,disable-ticketing \
    -monitor stdio \
    -device usb-kbd \
    -qmp tcp:0:8881,server,nowait \
    -rtc base=localtime,clock=host,driftfix=slew  \
    -boot order=cdn,once=d,menu=off,strict=off \
    -enable-kvm \
2.Create a txt document in vm, then turn on Caps-Lock in keyboard, then input some characters in guest.

Actual results:
(1)After turning on Caps-Lock in keyboard, can't input uppercase characters in guest, "\"and lowercase characters was got insteading  uppercase in guest.for example, when input "AA", the result is "\aa" in guest. 
(2)When sendkey "shift+a" there will got "A" in guest
 (qemu) sendkey shift-a
 ---get "A" in guest

Expected results:
(1)After turning on Caps-Lock in keyboard, can input uppercase characters in guest.

Additional info:
screenshot is as attachment.

Comment 6 Jan Kurik 2017-12-06 12:43:20 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


Note You need to log in before you can comment on or make changes to this bug.