Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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.
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.
(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.
(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 9Marc-Andre Lureau
2013-05-24 01:38:53 UTC
this should be fixed in spice-gtk 0.15, commit eec5f937150e9bc65e02b80ea06bd4bad3a90978
Comment 10Markus 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 11Marc-Andre Lureau
2013-05-24 13:14:11 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 13Marc-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 14Markus 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 15Marc-Andre Lureau
2013-05-29 11:39:58 UTC
found it, bug 868237
*** This bug has been marked as a duplicate of bug 868237 ***