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.
Description of problem:
[split daemon]Failed to execute virsh cmd without specified connect uri when using default setting
Version-Release number of selected component (if applicable):
libvirt-daemon-7.6.0-2.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Enable split daemon mode;
2.Check the virtqemud and virtproxyd/virtproxyd.socket daemon status:
# systemctl status virtqemud
● virtqemud.service - Virtualization qemu daemon
Loaded: loaded (/usr/lib/systemd/system/virtqemud.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2021-09-09 09:20:45 EDT; 2s ago
# systemctl status virtproxyd.socket
● virtproxyd.socket - Libvirt proxy local socket
Loaded: loaded (/usr/lib/systemd/system/virtproxyd.socket; enabled; vendor preset: disabled)
Active: active (listening) since Thu 2021-09-09 04:43:26 EDT; 4h 38min ago
# systemctl status virtproxyd
○ virtproxyd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/virtproxyd.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Thu 2021-09-09 09:19:45 EDT; 2min 4s ago
3.Execute virsh cmd:
# virsh list
error: failed to connect to the hypervisor
error: no connection driver available for <null>
Actual results:
Failed to execute virsh cmd without specified connect uri when using default setting
Expected results:
Should execute virsh cmds without specified connect uri successfully when using default setting in /etc/libvirt/libvirt.conf.
Additional info:
(In reply to Michal Privoznik from comment #1)
> I think this is fixed with the latest libvirt-7.7.0 build. Can you retest
> please?
Yes, it is fixed with libvirt-7.7.0-3.el9.x86_64.
Verified with libvirt-7.8.0-1.el9.x86_64.
Test steps:
1.Execute 'virsh list' without specified connect uri and not change the default libvirt.conf setting:
#virsh list
Id Name State
--------------------------------
1 avocado-vt-vm2 running
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 (new packages: libvirt), 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/RHBA-2022:2390
Description of problem: [split daemon]Failed to execute virsh cmd without specified connect uri when using default setting Version-Release number of selected component (if applicable): libvirt-daemon-7.6.0-2.el9.x86_64 How reproducible: 100% Steps to Reproduce: 1.Enable split daemon mode; 2.Check the virtqemud and virtproxyd/virtproxyd.socket daemon status: # systemctl status virtqemud ● virtqemud.service - Virtualization qemu daemon Loaded: loaded (/usr/lib/systemd/system/virtqemud.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2021-09-09 09:20:45 EDT; 2s ago # systemctl status virtproxyd.socket ● virtproxyd.socket - Libvirt proxy local socket Loaded: loaded (/usr/lib/systemd/system/virtproxyd.socket; enabled; vendor preset: disabled) Active: active (listening) since Thu 2021-09-09 04:43:26 EDT; 4h 38min ago # systemctl status virtproxyd ○ virtproxyd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/virtproxyd.service; enabled; vendor preset: disabled) Active: inactive (dead) since Thu 2021-09-09 09:19:45 EDT; 2min 4s ago 3.Execute virsh cmd: # virsh list error: failed to connect to the hypervisor error: no connection driver available for <null> Actual results: Failed to execute virsh cmd without specified connect uri when using default setting Expected results: Should execute virsh cmds without specified connect uri successfully when using default setting in /etc/libvirt/libvirt.conf. Additional info: