Thanks for pointing out the prefix thing with libvirt, and pointing me
to the correct mailing-list.
On 05/16/2018 05:01 AM, Daniel P. Berrangé wrote:
On Tue, May 15, 2018 at 10:27:32PM -0400, Adrian Lucrèce Céleste wrote:
I've hit a bit of a snag with virt-viewer. I've got it compiled, running,
but whenever I try to connect to a remote instance, I always get this:
[alc@xps org.virt_manager.virt-viewer]$ flatpak run
org.virt_manager.virt-viewer --debug -c
qemu+ssh://upsquared@192.168.10.192/system
(virt-viewer:2): virt-viewer-DEBUG: 22:21:30.782: connecting ...
(virt-viewer:2): virt-viewer-DEBUG: 22:21:30.783: Opening connection to
libvirt with URI qemu+ssh://upsquared@192.168.10.192/system
Enter passphrase for key '/home/alc/.ssh/id_rsa':
(virt-viewer:2): virt-viewer-DEBUG: 22:21:38.758: Error: End of file while
reading data: Ncat: No such file or directory.: Input/output error
Connecting to that URI via virt-manager on the same machine just works. I
just don't know what I'm doing wrong.
Here is my current flatpak manifest:
https://github.com/AdrianKoshka/flathub/blob/org.virt_manager.virt-viewer/org.virt_manger.virt-viewer.json
You are not settig the paths for building libvirt, so it will default
to /usr/local, but all the versions built by distros will use
--prefix=/usr --sysconfdir=/etc --localstatedir=/var.
Thus it will be trying to run netcat with the wrong socket path
eg /usr/local/var/run/libvirt/libvirt-sock, instead of
/var/run/libvirt/libvirt-sock
BTW, the mailing list for virt-viewer is actually the virt-tools-list
https://virt-manager.org/communicate/
Regards,
Daniel
_______________________________________________
Spice-devel mailing list
Spice-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/spice-devel