On Fri, Jul 29, 2022 at 07:49:16AM -0400, Carol Bouchard wrote:
TY VM!!! virtproxyd was disabled and I can assure you I didn't disable it.
/run/libvirt/libvirt-sock now exists AND the remote virsh actions were successful.
Background on my fedora36 install. I did not do an upgrade. This was a fresh install on a new laptop. I could see libvirt was running so I assumed it was intact. I had enabled/disabled libvirtd only because my remote virsh commands were not working.
Enabling/disabling libvirtd probably interfered with virtproxyd, as they both want the same sockets. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|