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:
Still a bug even upstream, but moving to 7.4.
This is an upstream bug that probably won't affect RHEL customers very much. Let's track this upstream instead. (It's also really a bug in qemu, not libguestfs)
Patches posted: https://www.redhat.com/archives/libguestfs/2017-March/msg00017.html
Fixed in libguestfs >= 1.37.1. https://github.com/libguestfs/libguestfs/commit/32d60801443647b3523b9374c431fefdbf054e3c