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.
Description of problem:
Version-Release number of selected component (if applicable):
[root@localhost Desktop]# uname -r
2.6.32-131.0.10.el6.x86_64
# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.160.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. start VM with -chardev
eg: <CLI> -monitor stdio \
-chardev socket,id=s11,path=/tmp/tt11,server,nowait \
-chardev socket,id=s12,path=/tmp/tt12,server,nowait \
-chardev socket,id=s13,path=/tmp/tt13,server,nowait \
2.Hot add virtio-serial-bus
(qemu) device_add virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x8
3.hot add 1st virtioserialport
(qemu)device_add virtserialport,chardev=s11,name=org.linux-kvm.port.11,bus=virtio-serial0.0,id=port11
4.in the guest send data to /dev/vport0p1
in the guest #echo c > /dev/virtio-ports/org.linux-kvm.port.11
on the host #nc -U /tmp/tt11
(after step 4 ,socket could receive data)
5.hot add another virtioserialport
(qemu)device_add virtserialport,chardev=s12,name=org.linux-kvm.port.12,bus=virtio-serial0.0,id=port12
6.in the guest send data to /dev/vport0p2
in the guest #echo c > /dev/virtio-ports/org.linux-kvm.port.12
on the host #nc -U /tmp/tt12
(after step 6 ,socket could receive data)
7.Hot unplug the 2nd virtio serial port
(qemu)device_del port12
(after step7 ,/dev/vport0p2 removed)
8.send data via /dev/vport0p1 in the guest
Actual Results:
After step8,guest could not transfer data via /dev/vport0p1
Expected Results:
After step8,guest still can send data via /dev/vport0p1