Cheers Cole,
Turned out I hadn't got libvirt (et al) installed on the target. (discovered
when I tried to use virsh)
Once I installed libvirt and restarted virt-manager they all showed up in the
gui and seem to be working.
That was all under the default qemu:///system connection.
______
But now I try to add VMs that were under a qemu:///session connection ...
Try adding the connection and get:
------------------------
Unable to connect to libvirt qemu:///session.
Verify that the 'libvirtd' daemon is running.
Libvirt URI is: qemu:///session
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/connection.py", line 922, in
_do_open
self._backend.open(cb, data)
File "/usr/share/virt-manager/virtinst/connection.py", line 155, in open
open_flags)
File "/usr/lib64/python3.6/site-packages/libvirt.py", line 148, in openAuth
raise libvirtError('virConnectOpenAuth() failed')
libvirt.libvirtError: Failed to connect socket to
'/run/user/1000/libvirt/libvirt-sock': No such file or
directory------------------------
daemon is running but there are no files in /run/user/1000/libvirt
[root@wsa libvirt]# systemctl | grep libvirt
libvirtd.service
loaded active running Virtualization daemon
libvirtd-admin.socket
loaded active running Libvirt admin socket
libvirtd-ro.socket
loaded active running Libvirt local read-only
socket
libvirtd.socket
loaded active running Libvirt local socket
[root@wsa libvirt]# pwd
/run/user/1000/libvirt
[root@wsa libvirt]# ls
total 0
77493 0 drwx------. 2 bob bob 40 Oct 12 17:15 .
67976 0 drwx------. 11 bob bob 520 Oct 12 18:00 ..
[root@wsa libvirt]#
I vaguely recall doing something relating to a user libvirt daemon but can't
find it or see anything obvious on old machine (same libvirt daemons running on
both)
Any ideas ?
On Monday, 10 October 2022 at 15:02:50 BST, Cole Robinson
<crobi...@redhat.com> wrote:
On 10/8/22 9:36 AM, Bob Power wrote:
> Hi,
>
> I'm moving "stuff" to a new machine. (Rocky 8.4 to Alma 8.6)
>
> I have been using virt-manager on the old machine.
>
> I want to open virt-manager on the the new machine and see what I saw on
> the old machine - the connections and list of VMs under those connections.
>
> I have copied everything under /etc/libvirt/qemu over but no joy.
>
> The man pages (man virt-manager) do not list any files.
>
> Can anyone give me a list of file paths used by virt-manager when it
> starts up to populate the GUI
virt-manager's connection list is stored in dconf. But it's probably not
worth trying to transfer that over, instead manually `File->Open
Connection` and recreate the list.
If once connected to local qemu:///system your VMs aren't showing up,
and you copied over /etc/libvirt/qemu files, you may need to restart
libvirtd or virtqemud (or reboot). The proper way to do this would have
been `sudo virsh dumpxml $VMNAME > $VMNAME.xml` on the source and then
`sudo virsh define $VMNAME.xml` on the dest.
- Cole
