[Libguestfs] [libvirt] Quantifying libvirt errors in launching the libguestfs appliance

[Richard W.M. Jones]

On Wed, Jan 13, 2016 at 03:50:47PM +0000, Richard W.M. Jones wrote:
> On Wed, Jan 13, 2016 at 04:25:14PM +0100, Martin Kletzander wrote:
> > For each of the kernels, libvirt labels them (with both DAC and selinux
> > labels), then proceeds to launching qemu.  If this is done parallel, the
> > race is pretty obvious.  Could you remind me why you couldn't use
> > <seclabel model='none'/> or <seclabel relabel='no'/> or something that
> > would mitigate this?
> 
> We value having sVirt :-)
> 
> However I'm just about to rerun the tests with <seclabel type='none'/>
> to see if the problem goes away.  Will let you know tomorrow once they
> have run again.

Yes - using <seclabel type=none> does prevent all of the errors.  Of
course this isn't a solution because we want to use sVirt.

> > >https://bugzilla.redhat.com/1298122
> > >https://bugzilla.redhat.com/1298124

I will mark these as duplicates.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v