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.

Bug 740168

Summary: virsh send-key and qemu-monitor-command does not work
Product: Red Hat Enterprise Linux 6 Reporter: Huang Wenlong <whuang>
Component: libvirtAssignee: Eric Blake <eblake>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 6.2CC: acathrow, cwei, dallan, eblake, linuxdev-ofuku, mfuruta, myamazak, mzhan, rwu, ydu, yupzhang
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: libvirt-0.9.4-13.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 11:32:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 738411    
Bug Blocks: 725559    

Description Huang Wenlong 2011-09-21 07:51:57 UTC
Description of problem:
virsh send-key  does not work
virsh qemu-monitor-command  does not work  too 

Version-Release number of selected component (if applicable):
libvirt-0.9.4-12.el6.x86_64
qemu-kvm-0.12.1.2-2.192.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. start a guest
2. send key to guest from host
# virsh send-key t62 KEY_N
error: command 'send-key' requires<keycode>  option



# virsh qemu-monitor-command t mouse_move 200 200 --hmp
error: command 'qemu-monitor-command' requires <cmd> option


Actual results:
send-key does not work


Expected results:
send-key  work


Additional info:

libvirt-0.9.4-10.el6.x86_64  send-key works well
so this bug is a regression

Comment 3 Eric Blake 2011-09-21 14:48:30 UTC
regression introduced by patch to bug 738411

Comment 4 Eric Blake 2011-09-21 14:55:18 UTC
Upstream patch proposed:
https://www.redhat.com/archives/libvir-list/2011-September/msg00847.html

Comment 7 yanbing du 2011-09-26 08:32:07 UTC
Test with libvirt-0.9.4-13.el6.x86_64, both virsh send-key and virsh qemu-monitor-command command work well.
Move to Verified.

Comment 8 Jiri Denemark 2011-10-13 09:12:44 UTC
*** Bug 745723 has been marked as a duplicate of this bug. ***

Comment 9 linuxdev-ofuku 2011-10-20 01:58:02 UTC
We were asked to verify the fix in BZ#745723.
And then our engineers verified that "virsh send-key" worked on 
RHEL6.2 snapshot1.
Thanks.

Best regards,
M Hanaki

Comment 10 errata-xmlrpc 2011-12-06 11:32:08 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

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