The virsh manpage doesn't mention ssh, so it sounds like the file
/usr/share/doc/libvirt-doc/remote.html shipped with libvirt-doc could
use a patch mentioning this.
** Changed in: libvirt (Ubuntu)
Status: Won't Fix = Triaged
** Changed in: libvirt (Ubuntu)
Importance: High = Low
--
** Summary changed:
- qemu+ssh connections to a remote libvirt fail
+ qemu+ssh connections to a remote libvirt fail (from o to n)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
The issue turned out to be due to how libvirt uses nc through ssh .
hggdh had a line in his .ssh/config entry for the host containing
LocalCommand printf whatever
The text being printed out was interpreted by the virsh client as coming
from libvirt, so the first set of characters were
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/868753
Title:
qemu+ssh connections to a remote libvirt fail
Note that LocalCommand is a valid ssh_config option; if virsh cannot
deal with it, it should be documented.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/868753
Title:
qemu+ssh
