Displaying 3 results from an estimated 3 matches for "virsecurityselinuxrestorealllabel".
2016 Jan 14
1
Re: [libvirt] Quantifying libvirt errors in launching the libguestfs appliance
On Thu, Jan 14, 2016 at 10:12:30AM +0000, Daniel P. Berrange wrote:
> The difference comes in the restore step - where we blow away the
> readonly label and put it back to the original. For disks we never
> restore readonly/shared labels, but for kernels we do. If we just
> kill the restore step for kernels too, we should be fine AFAICT.
Works for me - I can try a patch, or if you can
2016 Jan 15
1
Re: [libvirt] Quantifying libvirt errors in launching the libguestfs appliance
...toreFileLabel(priv, def->os.dtb) < 0)
> rc = -1;
> diff --git i/src/security/security_selinux.c w/src/security/security_selinux.c
> index 721c451..475cdbc 100644
> --- i/src/security/security_selinux.c
> +++ w/src/security/security_selinux.c
> @@ -2034,14 +2034,6 @@ virSecuritySELinuxRestoreAllLabel(virSecurityManagerPtr mgr,
> virSecuritySELinuxRestoreFileLabel(mgr, def->os.loader->nvram) < 0)
> rc = -1;
>
> - if (def->os.kernel &&
> - virSecuritySELinuxRestoreFileLabel(mgr, def->os.kernel) < 0)
> - rc = -1;
>...
2016 Jan 14
2
Re: [libvirt] Quantifying libvirt errors in launching the libguestfs appliance
On 01/14/2016 05:12 AM, Daniel P. Berrange wrote:
> On Thu, Jan 14, 2016 at 10:51:47AM +0100, Jiri Denemark wrote:
>> On Wed, Jan 13, 2016 at 16:25:14 +0100, Martin Kletzander wrote:
>>> On Wed, Jan 13, 2016 at 10:18:42AM +0000, Richard W.M. Jones wrote:
>>>> As people may know, we frequently encounter errors caused by libvirt
>>>> when running the