[Libguestfs] [PATCH] launch: show hint to resolve authentication failure from libvirt

Olaf Hering olaf at aepfle.de
Fri Oct 12 15:01:04 UTC 2012


On Fri, Oct 12, Richard W.M. Jones wrote:

> On Fri, Oct 12, 2012 at 04:20:50PM +0200, Olaf Hering wrote:
> > On Wed, Oct 10, Richard W.M. Jones wrote:
> > 
> > > libguestfs use of libvirt is a bit of a mess at the moment, since we
> > > end up opening two connections if you use the -d option ... this is
> > > something I'm intending to fix.
> > > 
> > > Nevertheless, it should be using NULL everywhere, so depending on
> > > whether you run it as root or not, it will use qemu:///system
> > > or qemu:///session.
> > > 
> > > It's somewhere on the to-do list to:
> > > 
> > >   (1) Fix the utilities so they only need to open one connection
> > >       (this will matter in the remote case).
> > > 
> > >   (2) Support authentication in libvirt by mapping libvirt auth
> > >       callbacks to libguestfs events.
> > 
> > Is this the reason why the first command fails, but the others work ok
> > for me?
> > 
> > virt-filesystems -v -c qemu+ssh:///system  -d sles11sp2 --all --long
> > 
> > virt-rescue -v -c qemu+ssh:///system  -d opensuse12 -r
> > virsh -c qemu+ssh:///system list --all
> 
> virt-rescue doesn't use the libvirt backend.  See:

It gets the list of configured devices from libvirt at least. The
message it prints is clear about what you said:

...
virt-rescue: warning: virt-rescue doesn't work with the libvirt backend
at the moment.  As a workaround, forcing attach-method = 'appliance'.
...


Olaf




More information about the Libguestfs mailing list