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.
+++ This bug was initially created as a clone of Bug #1081881 +++
Description of problem:
1. Add 2 displays for 1 guest, and for 1st display is port allocated
automatically and 2nd display is port fixed, the guest could not be started.
2. Add 2 displays for 1 guest, and for 1st display is port fixed and 2nd
display is port allocated automatically, the guest could not be started.
Version-Release number of selected component:
virt-manager-0.10.0-20.el7.noarch
How reproducible:
100%
Steps to Reproduce:
1. Start virt-manager and shutoff all guests.
2. Open one guest's detail page and remove all displays (VNC or Spice).
3. Add first Spice Display with port automatically allocated by "Add
Hardware" -> "Graphics" -> "Spice Server" Type, and make sure Port
"Automatically allocated" is checked.
4. Add second VNC Display with fixed port "5900" by "Add Hardware" ->
"Graphics" -> "VNC Server" Type, and make sure Port "Automatically
allocated" is not checked and Port is 5900.
5. Start this guest.
Actual result:
-----------------------------------------------------------------------------------------------
Error starting domain: internal error: early end of file from monitor:
possible problem:
qemu-kvm: Failed to start VNC server on `127.0.0.1:0': Failed to bind
socket: Address already in use
Error starting domain: internal error: early end of file from monitor:
possible problem:
qemu-kvm: Failed to start VNC server on `127.0.0.1:0': Failed to bind
socket: Address already in use
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 100, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 122, in
tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1220, in
startup
self._backend.create()
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 698, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error: early end of file from monitor: possible
problem:
qemu-kvm: Failed to start VNC server on `127.0.0.1:0': Failed to bind
socket: Address already in use
-----------------------------------------------------------------------------------------------------
Expected results:
1. Guest could be started since one of display with port "Automatically
allocated"
Additional info:
1. This issue also occurs when first display is fixed port 5900 and
second display is port Automatically allocated.
2. This issue also occurs on RHEL6.