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.

libvirt shouldn't allow an ambiguous XML configuration regarding CPU
topology. Example, what guest CPU config does the following XML represent?

<domain>
  ...
  <vcpus>3</vcpus>
  <cpu>
    <topology sockets='2' cores='2' threads='2'/>
  </cpu>
  ...
</domain>

It is unclear, and libvirt shouldn't accept that config. What I think libvirt
should do is make sockets= a readonly attribute that just mirrors the old style
<vcpus> value. We just throw out the any value the user passes for sockets= and sync with vcpus.

Then we clarify the docs that for HVM, <vcpus> is not 'logical guest
cpus' or anything like that, it represents a distinct socket to the guest. That
should allow people to edit <vcpus> like normal. And my understanding is that
HVs that do CPU hotplug do it at the socket level anyways, so setvcpus commands
still retain the correct semantics.

Some background: https://bugzilla.redhat.com/show_bug.cgi?id=708892#c2

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