I think I know what the problem is here actually. When we run libguestfs with the libvirt backend[1], libvirt will try to relabel the disks that we're trying to access. In the process it may relabel them in a way that makes them inaccessible to the original guest.
There are a couple of ways to avoid this. The simpler one is to avoid using the libvirt backend altogether: export LIBGUESTFS_BACKEND=direct The other one is to use the '-d' option (instead of '-a') which should cause libguestfs to copy the SELinux label to libvirt and (if everything goes well) will cause libvirt to use the correct label. Rich. [1] https://libguestfs.org/guestfs.3.html#backend -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html _______________________________________________ Libguestfs mailing list Libguestfs@redhat.com https://www.redhat.com/mailman/listinfo/libguestfs