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:
When boot qemu-kvm with "-vnc :-5900", the listening port will not be 0 port of host. The listening port will be changed by host. So qemu-kvm should give some friendly messages.  

Version-Release number of selected component (if applicable):
qemu-kvm-rhev-1.5.3-9.el7.x86_64
3.10.0-34.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Boot qemu-kvm with "-vnc :-5900".
# /usr/libexec/qemu-kvm -vnc :-5900 -monitor stdio
2.Check the listening port.
(qemu) info vnc


Actual results:
(qemu) info vnc 
Server:
     address: 0.0.0.0:47569
        auth: none
Client: none

Every time this port is different.

Expected results:
When boot qemu-kvm with "-vnc :-5900", qemu-kvm can not give some warning message or forbids using this port.

Additional info:
I also test "-spice port=0", it will give a error message.
# /usr/libexec/qemu-kvm -vnc :-5900 -spice port=0 -monitor stdio
qemu-kvm: neither port nor tls-port specified for spice

*** This bug has been marked as a duplicate of bug 733600 ***