RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 630825 - Guest kernel panic with spice cause host CapsLock and NumLock on and off in a loop
Summary: Guest kernel panic with spice cause host CapsLock and NumLock on and off in ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-client
Version: 6.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: beta
: 6.1
Assignee: Uri Lublin
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 580954 653260
TreeView+ depends on / blocked
 
Reported: 2010-09-07 05:52 UTC by Mike Cao
Modified: 2013-01-09 23:05 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When a kernel panic occurred on a guest, spice-client blinked the LED lights for the Num lock and Caps Lock keys even when it did not have keyboard focus, making it virtually impossible to type in another window. This bug has been fixed and both keys now work as expected.
Clone Of:
: 653260 (view as bug list)
Environment:
Last Closed: 2011-05-19 13:14:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0583 0 normal SHIPPED_LIVE libcacard and spice-client bug and enhancement update 2011-05-19 09:37:34 UTC

Description Mike Cao 2010-09-07 05:52:13 UTC
Description of problem:


Version-Release number of selected component (if applicable):
host :RHEL6.0 RC
# uname -r
2.6.32-71.el6.x86_64
# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.113.el6.x86_64


How reproducible:
100%

Steps to Reproduce:
1.start VM with -spice 
eg:/usr/libexec/qemu-kvm -M rhel6.0.0 -enable-kvm -m 2048 -smp 2 -name rhel5_ide_64_1 -uuid bdcbfb49-3411-1701-3c36-6bdbc00bedb9 -rtc base=utc,clock=host,driftfix=slew -boot dc -drive file=/home/ide/rhel5u5_64_ide_1.qcow2,if=none,id=drive-ide0-0-0,boot=on,format=qcow2 -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:10:f4:c2:c4,bus=pci.0,addr=0x3 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -device usb-tablet,id=input0 -spice port=5910,disable-ticketing -vga qxl -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -monitor stdio -qmp tcp:0:4441,server,nowait
2.connect the guest by using #/usr/libexec/spicec -h localhost -p port
3.make guest kernel panic ,eg :# echo "cā€œ > /proc/sysrq-rigger

  
Actual results:
NumLock and CapsLock are on and off in a loop ,the LED for NumLock and CapsLock in the keyboard twinkled.


Expected results:


Additional info:
start vm with -vnc will not hit the issue.

Comment 1 Gerd Hoffmann 2010-11-18 13:29:42 UTC
NumLock + CapsLock are blinking in case of a kernel panic even on real hardware.
So spice client making your LEDs blink is actually intentional behavior.

There is a bug though that spice client blinks the LEDs even in case it has not the keyboard focus, making it next to impossible to type in another window.  This has been fixed in upstream spice recently and the rebase planned for 6.1 should pick up the fix.

Comment 2 Mike Cao 2010-11-19 02:13:13 UTC
(In reply to comment #1)
> NumLock + CapsLock are blinking in case of a kernel panic even on real
> hardware.

I tried on RHEL5.6 64 bit Host, exec echo "c" > /proc/sysrq-trigger to make kernel panic ,NumLock +CapsLock does NOT blinking.

Comment 4 Gerd Hoffmann 2011-01-07 10:25:21 UTC
Updated spice client is committed, packages are available here:
http://download.devel.redhat.com/brewroot/packages/spice-client/0.7.1/1.el6/

Comment 7 Mike Cao 2011-03-09 02:50:56 UTC
Verified on spice-client-0.8.0-1.el6.x86_64 
Repeat the steps on comment #0.


Actual Results:
NumLock and CapsLock behave normal.

Based on above ,This issue has been fixed ald.

Comment 8 Mike Cao 2011-03-09 02:57:29 UTC
Based on comment #7,change status to VERIFIED.

Comment 9 Tomas Capek 2011-05-17 11:42:35 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When a kernel panic occurred on a guest, spice-client blinked the LED lights for the Num lock and Caps Lock keys even when it did not have keyboard focus, making it virtually   impossible to type in another window. This bug has been fixed and both keys now work as expected.

Comment 10 errata-xmlrpc 2011-05-19 13:14:59 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0583.html


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