Santhosh Kokala
2014-Apr-11 05:40 UTC
[libvirt-users] libvirt: error : internal error: cannot apply process capabilities -1
Hi All, I am running libvirt-1.1.2 on Scientific Linux release 6.1 (Carbon). I compiled the libvirtd rpms and installed them on to my system. I see this error 2014-04-11 05:37:42.351+0000: 12378: error : virCommandWait:2348 : internal error: Child process (LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/libexec/qemu-kvm -help) unexpected exit status 1: libvirt: error : internal error: cannot apply process capabilities -1 Whenever libvirtd restarts. Because of this error I also cannot create a domain with os_type set to "hvm". Virsh capabilities also does not list this os_type. Can someone let me if I am missing something obvious? Santhosh
Martin Kletzander
2014-Apr-11 07:21 UTC
Re: [libvirt-users] libvirt: error : internal error: cannot apply process capabilities -1
On Fri, Apr 11, 2014 at 05:40:25AM +0000, Santhosh Kokala wrote:>Hi All, >I am running libvirt-1.1.2 on Scientific Linux release 6.1 (Carbon). I compiled the libvirtd rpms and installed them on to my system. I see this error > >2014-04-11 05:37:42.351+0000: 12378: error : virCommandWait:2348 : internal error: Child process (LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/libexec/qemu-kvm -help) unexpected exit status 1: libvirt: error : internal error: cannot apply process capabilities -1 > >Whenever libvirtd restarts. Because of this error I also cannot create a domain with os_type set to "hvm". Virsh capabilities also does not list this os_type. >This is because we failed to start the process mentioned in the error message. Unfortunately, we're not doing much of a debugging in that area of the code, so there isn't much information to see even if you have debug messages turned on. Basically, this means capng_apply(3) failed with -1, but that's all we know now. You can try running libvirt under gdb, set breakpoint in capng_apply and ... see what you can get from that. Unfortunately that's all I know about capng, maybe someone else will provide better insight. The only way this is a bug in libvirt is if we're for example compiled with libcap-ng that provides PR_CAPBSET_DROP, but the kernel doesn't somehow. Otherwise I see no patch changing anything in the capng area of the code between 1.1.2 and current HEAD. Martin>Can someone let me if I am missing something obvious? > >Santhosh>_______________________________________________ >libvirt-users mailing list >libvirt-users@redhat.com >https://www.redhat.com/mailman/listinfo/libvirt-users