On Dec 5, 2025 10:14, Nikolaus Rath <nikolaus@rath.org> wrote:

>> And lastly, how do I tell virt-manager what socket to use? The qemu://system URL doesn't seem to directly map to any socket....
>
> Normally you don't. The socket gets picked based on the URI and whether
> you are opening a read-only or read write connection

In my virt-manager, there is no read-only option when I click on "Add-Connection". There's a "Hypervisor" dropdown and an อบ"Autoconnect" checkbox, but nothing about read-only.

Are we talking about a different element of the UI?

Best,
-Nikolaus

There isn't a way to define a RO conn  *method* via the URI[0], no. I don't recall VMM having an option to do so either. But if you add a hypervisor via the "Custom URI" option, and explicitly use `qemu+unix:///system?socket=/path/to/RO/socket.sock` that *should* force a connection to use the RO socket. I have no idea if that will *work* or not, though, because I think it still uses a `virConnectOpen` instead of `virConnectOpenReadOnly` method.


[0] https://libvirt.org/uri.html