-
Bug
-
Resolution: Done-Errata
-
Minor
-
rhel-9.0.0
-
libvirt-10.0.0-1.el9
-
Yes
-
Low
-
rhel-sst-virtualization
-
ssg_virtualization
-
20
-
26
-
None
-
QE ack, Dev ack
-
False
-
-
None
-
None
-
Pass
-
RegressionOnly
-
If docs needed, set a value
-
-
Unspecified
-
10.0.0
-
None
Description of problem:
Wrong error info reported when executing 'virsh list' without starting virtqemud
Version-Release number of selected component (if applicable):
libvirt-8.0.0-3.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Install libvirt pkgs:
- yum -y install libvirt*
2.Executing virsh list without starting virtqemud:
#virsh list
error: failed to connect to the hypervisor
error: Operation not supported: Cannot use direct socket mode if no URI is set
3.
Actual results:
Expected results:
Should report error to remind no existing socket file, such as:
error: failed to connect to the hypervisor
error: Failed to connect socket to '/var/run/libvirt/virtqemud-sock': No such file or directory
Additional info:
- is blocked by
-
RHEL-15267 Rebase libvirt in RHEL-9.4.0
- Closed
- is duplicated by
-
RHEL-16568 virtqemud-ro.socket is not started after install, resulting in error "Operation not supported: Cannot use direct socket mode if no URI is set"
- Closed
- external trackers
- links to
-
RHBA-2023:125049 libvirt bug fix and enhancement update
- mentioned on