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:
Better to report an error if there are two same virtio-serial address in the guest's xml
Version-Release number of selected component (if applicable):
kernel-2.6.32-348.el6.x86_64
libvirt-0.10.2-12.el6.x86_64
qemu-kvm-0.12.1.2-2.346.el6.x86_64
How reproducible:
100%
1 prepare a guest add the following to the guest xml
# virsh list --all
rhelnew shut off
# virsh edit rhelnew
---
---
<channel type='unix'>
<source mode='bind' path='/var/lib/libvirt/qemu/rhelnew.agent'/>
<target type='virtio' name='org.qemu.guest_agent.0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
<channel type='spicevmc'>
<target type='virtio' name='com.redhat.spice.0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
----
-----
then save the xml
2 start the guest will report error
# virsh start rhelnew
error: Failed to start domain rhelnew
error: Unable to read from monitor: Connection reset by peer
# virsh start rhelnew
error: Failed to start domain rhelnew
error: internal error process exited while connecting to monitor: 2012-12-27 03:24:14.029+0000: 27788: debug : virFileClose:72 : Closed fd 31
2012-12-27 03:24:14.029+0000: 27788: debug : virFileClose:72 : Closed fd 39
2012-12-27 03:24:14.031+0000: 27788: debug : virFileClose:72 : Closed fd 3
char device redirected to /dev/pts/6
qemu-kvm: -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel1,id=channel1,name=com.redhat.spice.0: virtio-serial-bus: A port already exists at id 1
qemu-kvm: -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel1,id=channel1,name=com.redhat.spice.0: Device 'virtserialport' could not be initialized
Actual results:
it didn't report error while there were two same virtio-serial address exsitting in the guest xml
Expected results:
Better to report an error if there are two same virtio-serial address in the guest's xml ,just like the pci address
# virsh edit rhelnew
---
<video>
<model type='qxl' vram='65536' heads='1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</video>
<memballoon model='virtio'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
----
then save will report error
# virsh edit rhelnew
error: XML error: Attempted double use of PCI Address '0:0:2.0'
Failed. Try again? [y,n,f,?]:
Comment 2RHEL Program Management
2012-12-31 06:47:15 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Verified as below:
[root@localhost ~]# rpm -q libvirt
libvirt-1.2.15-1.el7.x86_64
Prepare a block of xml as below
<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='1'/>
</channel>
Then save the xml with the configuration.
[root@localhost ~]# virsh edit r71
error: XML error: virtio serial port 1 on controller 0 is already occupied
Failed. Try again? [y,n,i,f,?]:
We can get expected results, move to verified.
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: Better to report an error if there are two same virtio-serial address in the guest's xml Version-Release number of selected component (if applicable): kernel-2.6.32-348.el6.x86_64 libvirt-0.10.2-12.el6.x86_64 qemu-kvm-0.12.1.2-2.346.el6.x86_64 How reproducible: 100% 1 prepare a guest add the following to the guest xml # virsh list --all rhelnew shut off # virsh edit rhelnew --- --- <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/rhelnew.agent'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <channel type='spicevmc'> <target type='virtio' name='com.redhat.spice.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> ---- ----- then save the xml 2 start the guest will report error # virsh start rhelnew error: Failed to start domain rhelnew error: Unable to read from monitor: Connection reset by peer # virsh start rhelnew error: Failed to start domain rhelnew error: internal error process exited while connecting to monitor: 2012-12-27 03:24:14.029+0000: 27788: debug : virFileClose:72 : Closed fd 31 2012-12-27 03:24:14.029+0000: 27788: debug : virFileClose:72 : Closed fd 39 2012-12-27 03:24:14.031+0000: 27788: debug : virFileClose:72 : Closed fd 3 char device redirected to /dev/pts/6 qemu-kvm: -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel1,id=channel1,name=com.redhat.spice.0: virtio-serial-bus: A port already exists at id 1 qemu-kvm: -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel1,id=channel1,name=com.redhat.spice.0: Device 'virtserialport' could not be initialized Actual results: it didn't report error while there were two same virtio-serial address exsitting in the guest xml Expected results: Better to report an error if there are two same virtio-serial address in the guest's xml ,just like the pci address # virsh edit rhelnew --- <video> <model type='qxl' vram='65536' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> ---- then save will report error # virsh edit rhelnew error: XML error: Attempted double use of PCI Address '0:0:2.0' Failed. Try again? [y,n,f,?]: