Bug 880883

Summary: atkbd.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
Product: Red Hat Enterprise Linux 6 Reporter: Chao Yang <chayang>
Component: spice-gtkAssignee: Christophe Fergeau <cfergeau>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: low    
Version: 6.4CC: acathrow, alevy, areis, armbru, bsarathy, cfergeau, chayang, dblechte, dyasny, ezubillaga, ipilcher, juzhang, marcandre.lureau, michen, mkenneth, qzhang, shuang, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-29 11:39:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Chao Yang 2012-11-28 03:14:05 UTC
Description of problem:
Fresh install a rhel6.4 guest, login guest, check dmesg. A lot of messages pops up:
atkbd.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0).
atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known.


Version-Release number of selected component (if applicable):
qemu-kvm-rhev-0.12.1.2-2.337.el6.x86_64
host kernel vesrion: 2.6.32-344.el6.x86_64
guest kernel version: 2.6.32-343.el6

How reproducible:
100%

Steps to Reproduce:
1. fresh install a 6.4 guest
2. connect to guest by remote-viewer
3. login guest and check dmesg
  
Actual results:


Expected results:


Additional info:
CLI:
 /usr/libexec/qemu-kvm -M rhel6.4.0 -cpu host -enable-kvm -m 8192 -smp 16,sockets=2,cores=4,threads=2 -name emulex_device_assignment -uuid 8842aa9e-2d20-4540-8557-4d04752a28d7 -rtc base=utc,clock=host,driftfix=slew -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0 -drive file=/home/emulex_device_assignment.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,serial=f82002eb-520c-469b-90c2-663277e90437,cache=none,werror=stop,rerror=stop,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,id=hostnet0,vhost=on -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:42:0b:38,bus=pci.0 -chardev spicevmc,id=charchannel1,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0 -spice port=8000,disable-ticketing -k en-us -vga qxl -global qxl-vga.vram_size=67108864 -monitor stdio

Comment 2 Ian Pilcher 2012-12-29 23:19:07 UTC
I am seeing the same thing with a RHEL 6.3 guest on a Fedora 18 host.  Every keypress in the (SPICE) console results in the message being printed.  Needless to say, this makes it extremely difficult to use the console, although it does still work.

This guest worked find on Fedora 17, with the virt-preview repository enabled.  The guest was moved to Fedora 18 by 'virsh defining' the F17 XML file.

Comment 3 Ian Pilcher 2012-12-29 23:26:05 UTC
The problem does not occur when I change the display type to VNC (with cirrus video).

Comment 4 Erasmo Zubillaga 2012-12-30 14:03:06 UTC
Same here, changing the display type to VNC solves the problem. The video card type (cirrus, qxl, etc) doesn't make any difference on my experience.

Using F18 host with custom 3.0 Linux guest.

Comment 6 Alon Levy 2013-05-22 18:23:20 UTC
Which client is in use? (this goes for the original poster and anyone who managed to reproduce)

Comment 7 Chao Yang 2013-05-23 02:34:21 UTC
(In reply to Alon Levy from comment #6)
> Which client is in use? (this goes for the original poster and anyone who
> managed to reproduce)

It's remote-viewer in use.

Comment 8 Alon Levy 2013-05-23 13:04:40 UTC
(In reply to chayang from comment #7)
> (In reply to Alon Levy from comment #6)
> > Which client is in use? (this goes for the original poster and anyone who
> > managed to reproduce)
> 
> It's remote-viewer in use.

Which version?

Comment 9 Marc-Andre Lureau 2013-05-24 01:38:53 UTC
this should be fixed in spice-gtk 0.15, commit eec5f937150e9bc65e02b80ea06bd4bad3a90978

Comment 10 Markus Armbruster 2013-05-24 07:08:30 UTC
Assuming retesting confirms it's fixed: Marc-Andre, got an RHBZ for spice-gtk commit eec5f93?  If yes, this bug can be closed as duplicate of it.  If no, this bug can be used to track it.

Comment 11 Marc-Andre Lureau 2013-05-24 13:14:11 UTC
I don't think there is any bug for it.

Comment 12 Chao Yang 2013-05-28 05:53:16 UTC
It is not reproducible with 
qemu-kvm-0.12.1.2-2.369.el6.x86_64, host kernel-2.6.32-376.el6.x86_64, RHEL6.4 GA guest if connect guest either with spice-gtk-0.14-7.el6.x86_64 in rhel6 or spice-gtk3-0.18-1.fc18.x86_64 in F18. 

Hi Marc-Andre, Markus,
 Is there any relevant fix in either qemu-kvm or kernel? Cause I cannot reproduce this issue with above combination.

Comment 13 Marc-Andre Lureau 2013-05-28 13:34:19 UTC
(In reply to chayang from comment #12)
> It is not reproducible with 
> qemu-kvm-0.12.1.2-2.369.el6.x86_64, host kernel-2.6.32-376.el6.x86_64,
> RHEL6.4 GA guest if connect guest either with spice-gtk-0.14-7.el6.x86_64 in
> rhel6 or spice-gtk3-0.18-1.fc18.x86_64 in F18. 
> 
> Hi Marc-Andre, Markus,
>  Is there any relevant fix in either qemu-kvm or kernel? Cause I cannot
> reproduce this issue with above combination.

The spice-gtk fix has been backported to to RHEL, and is available since spice-gtk 0.15. You would need older spice-gtk version to reproduce.

Comment 14 Markus Armbruster 2013-05-28 14:07:15 UTC
This is a spice-gtk bug, and it has already been fixed.  The big should be closed as duplicate of whatever bug is associated with the fix.  Since I don't know which one to use, I'm reassigning to spice-gtk.

Comment 15 Marc-Andre Lureau 2013-05-29 11:39:58 UTC
found it, bug 868237

*** This bug has been marked as a duplicate of bug 868237 ***