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.
commit 083c33b3243da8ab266c0ff75b6abb217bcbf440
Author: Ján Tomko <jtomko>
CommitDate: 2015-05-13 12:20:31 +0200
Assign virtio-serial addresses after coldplugging a device
Otherwise we might allow coldplugging a device
that uses an address that is already occupied, creating
an unstartable domain.
https://bugzilla.redhat.com/show_bug.cgi?id=1220195
git describe: v1.2.15-72-g083c33b
Verify this bug with libvirt-1.2.17-2.el7.x86_64
1. Prepare a shut off domain, with below in xml config
# virsh dumpxml r7|grep pty -A 4
<channel type='pty'>
<target type='virtio' name='org.linux-kvm.port.3'/>
<address type='virtio-serial' controller='0' bus='0' port='4'/>
</channel>
2. Prepare below xml file
# cat ch.xml
<channel type='pty'>
<target type='virtio' name='org.linux-kvm.port.4'/>
<address type='virtio-serial' controller='0' bus='0' port='4'/>
</channel>
3. Do cold-plug
# virsh attach-device r7 ch.xml --config
error: Failed to attach device from ch.xml
error: XML error: virtio serial port 4 on controller 0 is already occupied
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-2202.html
Description of problem: Assign virtio-serial addresses after coldplugging a device Version-Release number of selected component (if applicable): libvirt-1.2.15-1.el7.x86_64 qemu-kvm-rhev-2.3.0-1.el7.x86_64 How reproducible: always Steps to Reproduce: [root@localhost ~]# cat channel.xml <channel type='pty'> <target type='virtio' name='org.linux-kvm.port.3'/> <address type='virtio-serial' controller='0' bus='0' port='4'/> </channel> [root@localhost ~]# virsh attach-device r71 channel.xml --config Device attached successfully [root@localhost ~]# vim channel.xml [root@localhost ~]# [root@localhost ~]# cat channel.xml <channel type='pty'> <target type='virtio' name='org.linux-kvm.port.4'/> <address type='virtio-serial' controller='0' bus='0' port='4'/> </channel> [root@localhost ~]# virsh attach-device r71 channel.xml --config Device attached successfully [root@localhost ~]# virsh dumpxml r71 | grep "</channel>" -B5 <target type='serial' port='0'/> </console> <channel type='spicevmc'> <target type='virtio' name='com.redhat.spice.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <channel type='pty'> <target type='virtio' name='org.linux-kvm.port.0'/> <address type='virtio-serial' controller='0' bus='0' port='2'/> </channel> <channel type='pty'> <target type='virtio' name='org.linux-kvm.port.1'/> <address type='virtio-serial' controller='0' bus='0' port='8'/> </channel> <channel type='pty'> <target type='virtio' name='org.linux-kvm.port.3'/> <address type='virtio-serial' controller='0' bus='0' port='4'/> </channel> <channel type='pty'> <target type='virtio' name='org.linux-kvm.port.4'/> <address type='virtio-serial' controller='0' bus='0' port='4'/> </channel> [root@localhost ~]# virsh start r71 error: Failed to start domain r71 error: XML error: virtio serial port 4 on controller 0 is already occupied Actual results: I found a small issue, with "--config" option libvirt still can accept duplicated port for virtio channel devcies, but based on your patches in bug 1076708, the domain can not boot up normally, libvirt need a small patch to fix it. Expected results: Fix it Additional info: