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:
Set graphic port to 65535, guest will fail to start.

# virsh dumpxml $guest
    <graphics type='vnc' port='65534' autoport='no' listen='0.0.0.0'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>

# virsh start $guest
error: Failed to start domain 1
error: internal error: Failed to reserve port 65535

I think if set bitmap->nbits = 65536, or change "bitmap->nbits <= b" to "bitmap->nbits < b", the problem will be gone.

int
virBitmapSetBit(virBitmapPtr bitmap,
                size_t b)
{
    if (bitmap->nbits <= b)
        return -1;

    bitmap->map[VIR_BITMAP_UNIT_OFFSET(b)] |= VIR_BITMAP_BIT(b);
    return 0;
}



Version-Release number of selected component (if applicable):
libvirt-4.3.0-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
65534 can work

Upstream patch posted:

https://www.redhat.com/archives/libvir-list/2018-June/msg01089.html

Upstream commit:

commit 5e828d03bf662331579c24677d29e50b9bc33951
Author: Pavel Hrdina <phrdina>
Date:   Thu Jun 14 09:17:10 2018 +0200

    virtportallocator: Change number of ports to 65536

Verify with:
libvirt-4.5.0-6.el7.x86_64
qemu-kvm-rhev-2.12.0-9.el7.x86_64

Steps to verify:
1. start guest with vnc graphic port='65535':
# virsh start yan-V
Domain yan-V started

# virsh dumpxml yan-V|grep 'graphics t' -A2
    <graphics type='vnc' port='65535' autoport='no' listen='0.0.0.0'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>

# ps aux|grep qemu|grep vnc
 -vnc 0.0.0.0:59635 

2.define a guest with graphic port='65536', try to start it:
# virsh start yan-V 
error: Failed to start domain yan-V
error: unsupported configuration: vnc port must be in range [5900,65535]

3.retest step2 with port='65537':
same as step 2

Since the test result is as expected. mark this bug as 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://access.redhat.com/errata/RHSA-2018:3113