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 1250850 - qemu should report conflict warning message when multiple virtio-serial using the same path
Summary: qemu should report conflict warning message when multiple virtio-serial usin...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Amit Shah
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1256170
TreeView+ depends on / blocked
 
Reported: 2015-08-06 07:10 UTC by quxiaoya
Modified: 2017-01-30 11:17 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1256170 (view as bug list)
Environment:
Last Closed: 2017-01-30 11:17:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description quxiaoya 2015-08-06 07:10:50 UTC 
Description of problem:

when boot a guest with multiple virtio-serial using same path,qemu didn't report any error message( As serial port cannot tranfer data from guest to host)

Version-Release number of selected component (if applicable):
host info:
# uname -r
3.10.0-302.el7.x86_64
# rpm -qa | grep qemu
qemu-kvm-rhev-2.3.0-14.el7.x86_64

guest info:
# uname -r
3.10.0-300.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. boot a guest with multiple virtio-serial using same path

cli:
/usr/libexec/qemu-kvm -smp 4 -m 4G -M pc -drive file=/home/sys_disk/RHEL-Server-7.2-64-virtio.qcow2-0805,format=qcow2,cache=none,if=none,werror=stop,rerror=stop,id=drive-disk0 -device ide-drive,drive=drive-disk0,id=disk0,bootindex=1 \

-monitor stdio -spice id=on,port=5933,disable-ticketing \
-netdev tap,id=tap0,script=/etc/qemu-ifup -device virtio-net-pci,netdev=tap0,mac=24:be:05:18:95:23 \

-qmp tcp:0:6766,server,nowait \

-device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x4 -chardev socket,id=channel1,path=/tmp/helloworld,server,nowait \

-device virtserialport,nr=1,chardev=channel1,name=com.redhat.rhevm.vdsm1,bus=virtio-serial0.0,id=port1 -chardev socket,id=channel2,path=/tmp/helloworld,server,nowait \

-device virtserialport,nr=2,chardev=channel2,name=com.redhat.rhevm.vdsm2,bus=virtio-serial0.0,id=port2



Actual results:
qemu will not report this conflict error

Expected results:

qemu report this conflict error 

Additional info:
Comment 4 Amit Shah 2017-01-30 11:17:06 UTC 
This is fixed in commit d0a0bfe6729ef6044d76ea49fafa07e29fa598bd which was released as part of upstream qemu 2.2.

RHEL7.3 contains qemu 2.6, so I'm marking this as fixed in CURRENTRELEASE.
Note You need to log in before you can comment on or make changes to this bug.