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.
In rhel6 it is different, press ^C virt-rescue will not be terminated, but have no response:
><rescue> ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C^C^C^C^C^C^C^C^C^C^C
+++ This bug was initially created as a clone of Bug #1152819 +++
Description of problem:
Currently if i want to end a running commands, these commands often can not finish correctly, the only way is to exit virt-rescue. If the commands have a acceptable time to return, then i can wait until it return. But if the commands can not return when it run incorrectly or have a very long time to return, then i have to quit virt-rescue to end that commands.
If i use virt-rescue to fix a bad virt machine, there is a high probability to encounter this situation.
Version-Release number of selected component (if applicable):
libguestfs-1.27.62-1.1.el7
How reproducible:
100%
Steps to Reproduce:
1. Get a rhel guest image: rhel.img
2. #virt-rescue --network -a rhel.img
><rescue> ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
3. Press ^C
Actual results:
><rescue> ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
qemu: terminating on signal 2
^C will let you exit virt-rescue
Expected results:
Can press ^C or other keys to end command 'ping 8.8.8.8' and not exit virt-rescue
Additional info:
Comment 3Richard W.M. Jones
2016-08-23 18:03:01 UTC
Low priority bug, complex to fix, not fixed upstream, so closing.