[GH-ISSUE #652] Webvirtcloud cannot connection to new libvirt version #377

New issue

Open

opened 2026-02-27 15:58:26 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 15:58:26 +03:00

Owner

Originally created by @hungviet99 on GitHub (Jun 26, 2024).
Original GitHub issue: https://github.com/retspen/webvirtcloud/issues/652

In RHEL 9, the libvirt library uses modular daemons that handle individual virtualization driver, so redhat changed from libvirt to virtqemud daemon handles QEMU drivers.

I configured file /etc/libvirt/virtqemud.conf following:

[root@dbp-mgmt-01 common]# cat /etc/libvirt/virtqemud.conf | egrep -v "^*#|^$"
listen_tls = 0
listen_tcp = 1
tcp_port = "16509"
listen_addr = "0.0.0.0"
auth_tcp = "none"

and then restart virtqemud.service but i still couldn't connect to libvirt server with port 16509.

[root@dbp-mgmt-01 common]# virsh -c qemu+tcp://localhost:16509/system list
error: failed to connect to the hypervisor
error: unable to connect to server at 'localhost:16509': Connection refused

How can I open port 16509 so webvirtcloud can connect to it?

Originally created by @hungviet99 on GitHub (Jun 26, 2024). Original GitHub issue: https://github.com/retspen/webvirtcloud/issues/652 In RHEL 9, the libvirt library uses modular daemons that handle individual virtualization driver, so redhat changed from libvirt to virtqemud daemon handles QEMU drivers. I configured file `/etc/libvirt/virtqemud.conf` following: ``` [root@dbp-mgmt-01 common]# cat /etc/libvirt/virtqemud.conf | egrep -v "^*#|^$" listen_tls = 0 listen_tcp = 1 tcp_port = "16509" listen_addr = "0.0.0.0" auth_tcp = "none" ``` and then restart virtqemud.service but i still couldn't connect to libvirt server with port 16509. ``` [root@dbp-mgmt-01 common]# virsh -c qemu+tcp://localhost:16509/system list error: failed to connect to the hypervisor error: unable to connect to server at 'localhost:16509': Connection refused ``` How can I open port 16509 so webvirtcloud can connect to it?

kerem commented

2026-02-27 15:58:27 +03:00

Author

Owner

@catborise commented on GitHub (Jun 28, 2024):

you must start libvirt service with virtproxyd-tcp.socket to connect remote host.

@catborise commented on GitHub (Jun 28, 2024): you must start libvirt service with virtproxyd-tcp.socket to connect remote host.