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.

As it seems, there is nothing to prevent us running several libvirt instances — except of hardcoded pathes to the libvirt socket, images directory and so on.

Keeping in mind libvirt driver lock (https://bugzilla.redhat.com/show_bug.cgi?id=856609), it is a serious limitation of libvirt scalability: there is no use of several CPU while creating VMs (and, maybe, not only creating, but we stuck on this with creating).

It would be nice to make such pathes configurable (with default values == what it uses right now). I will allow us to run several libvirtd instances w/o usage of FS namespaces, that is not too trivial.

The libvirt design is such that there is 1 instance of libvirt which runs privilege, and optionally 1 instance per non-root user account which run unprivileged. Running multiple privileged libvirtd instances is a non-goal.

What is your use case for having multiple privileges instances of libvirtd ?

There is a scalability issue with libvirt on hosts with many CPUs, caused by the driver lock (see bz#856609). It can be solved either on the driver level, or with several libvirtd instances. The former is the better, but one doesn't exclude another.

We are not going to support running multiple instances of libvirtd just to hack around that bug. That bug should simply be fixed.

Agreed, we should focus our scalability efforts on improving locking.