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 1588595

Summary: Input "yes" cause process can't quit when guest tranfer data to host with virtio-serial-port
Product: Red Hat Enterprise Linux 7 Reporter: Li Xiaohui <xiaohli>
Component: qemu-kvm-rhevAssignee: pagupta
Status: CLOSED NOTABUG QA Contact: Qianqian Zhu <qizhu>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.6CC: chayang, juzhang, knoel, mdeng, michen, qizhu, qzhang, virt-maint, xfu
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-12-07 14:48:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
host receive data successful but guest can't stop to output "y" none

Description Li Xiaohui 2018-06-07 15:08:03 UTC
Created attachment 1448751 [details]
host receive data successful but guest can't stop to output "y"

Description of problem:
Input "yes" cause transfer process in guest can't quit when transfer data from guest to host with virtio-serial-port

Version-Release number of selected component (if applicable):
host: qemu-kvm-rhev-2.12.0-3.el7.x86_64    kernel-3.10.0-895.el7.x86_64
guest: kernel-3.10.0-895.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.boot guest with virtioserialport on host:
/usr/libexec/qemu-kvm -M pc -cpu SandyBridge   
-device virtio-serial-pci,id=virtio-serial0,max_ports=16 
-chardev socket,id=channel1,path=/tmp/helloworld1,server,nowait 
-device virtserialport,chardev=channel1,name=com.redhat.rhevm.vdsm1,bus=virtio-serial0.0,id=port1 
2.on guest: start transfer data and after transfer process started, input "yes", and click "Enter", like screenshot in attachment:
# echo "helloworld1" > /dev/vport1p1
yes
3.on host: then start receive data :
# nc -U /tmp/helloworld1

Actual results:
host received data successful, and guest will always output "y" in command line and no stop, and click "Enter" won't stop the process, only if execute "Ctrl + c" can quit from the process.

Expected results:
after transfer data successful, the transfer data process should quit automatic.

Additional info:

Comment 3 pagupta 2018-12-07 14:48:43 UTC
On host side you are using nc command[1] which will keep connection open unless client closes connection. This is not a bug. 

[1]
<snippet>
.on host: then start receive data :
# nc -U /tmp/helloworld1
</snippet>