search for: setfiles

[This email is either empty or too large to be displayed at this time]

...hard. > -----Original Message----- > From: Richard W.M. Jones [mailto:rjones@redhat.com] > Sent: Monday, March 5, 2018 8:42 PM > To: Зиновик Игорь Анатольевич <ZinovikIA@nspk.ru> > Cc: libguestfs@redhat.com > Subject: Re: [Libguestfs] virt-v2v 1.38 fails to convert .vmx VM: setfiles ... > Multiple same specifications for /.*. > > On Mon, Mar 05, 2018 at 02:03:17PM +0000, Зиновик Игорь Анатольевич > wrote: > > Hello. > > > > I'm trying to convert VMware based virtual machines (CentOS 7.2) and output > them into oVirt. > > virt-v2v fa...

--- appliance/packagelist.in | 1 + daemon/Makefile.am | 1 + daemon/setfiles.c | 93 ++++++++++++++++++++++++++++++++++++++++++++++++ generator/actions.ml | 22 ++++++++++++ gobject/Makefile.inc | 2 ++ src/MAX_PROC_NR | 2 +- 6 files changed, 120 insertions(+), 1 deletion(-) create mode 100644 daemon/setfiles.c diff --git a/appliance/packagelist...

> -----Original Message----- > From: Richard W.M. Jones [mailto:rjones@redhat.com] > Sent: Tuesday, March 6, 2018 11:49 AM > To: Зиновик Игорь Анатольевич <ZinovikIA@nspk.ru> > Cc: libguestfs@redhat.com > Subject: Re: [Libguestfs] virt-v2v 1.38 fails to convert .vmx VM: setfiles ... > Multiple same specifications for /.*. > > On Tue, Mar 06, 2018 at 08:40:51AM +0000, Зиновик Игорь Анатольевич > wrote: > > > What happens if you run these commands (which should be safe to run > > > because they only operate on a throw-away overlay): > > &g...

...and indeed, in some cases the other systems that completed in minutes had MORE disk usage). > Running `virt-v2v -v -x ...' and observing the output will give you a > good idea of what precisely it was doing for those hours. Well, as I said in my original email, it was hanging at running setfiles: commandrvf: stdout=n stderr=y flags=0x0 commandrvf: setfiles -F -e /sysroot/dev -e /sysroot/proc -e /sysroot/selinux -e /sysroot/sys -r /sysroot -q /sysroot/etc/selinux/targeted/contexts/files/file_contexts /sysroot/ Can't stat exclude path "/sysroot/selinux", No such file or direct...

...--git a/daemon/selinux-relabel.c b/daemon/selinux-relabel.c index 112bee1..2f48ee6 100644 --- a/daemon/selinux-relabel.c +++ b/daemon/selinux-relabel.c @@ -27,6 +27,8 @@ #include "actions.h" #include "optgroups.h" +#include "ignore-value.h" + GUESTFSD_EXT_CMD(str_setfiles, setfiles); #define MAX_ARGS 64 @@ -37,6 +39,20 @@ optgroup_selinuxrelabel_available (void) return prog_exists (str_setfiles); } +static int +setfiles_has_m_option (void) +{ + static int flag = -1; + CLEANUP_FREE char *err = NULL; + + if (flag == -1) { + ignore_value (command (NULL,...

...Message----- > > From: Richard W.M. Jones [mailto:rjones@redhat.com] > > Sent: Monday, March 19, 2018 3:27 PM > > To: Зиновик Игорь Анатольевич <ZinovikIA@nspk.ru> > > Cc: libguestfs@redhat.com > > Subject: Re: [Libguestfs] virt-v2v 1.38 fails to convert .vmx VM: setfiles ... > > Multiple same specifications for /.*. > > > > On Tue, Mar 06, 2018 at 09:31:33AM +0000, Зиновик Игорь Анатольевич > > wrote: > > > > Multiple same specifications for /.*. > > ... > > > > > setfiles: > > > > > /sysroot/e...

...6, 2016 at 11:31:40AM -0500, Derek Atkins wrote: >> > Running `virt-v2v -v -x ...' and observing the output will give you a >> > good idea of what precisely it was doing for those hours. >> >> Well, as I said in my original email, it was hanging at running >> setfiles: >> >> commandrvf: stdout=n stderr=y flags=0x0 >> commandrvf: setfiles -F -e /sysroot/dev -e /sysroot/proc -e >> /sysroot/selinux -e /sysroot/sys -r /sysroot -q >> /sysroot/etc/selinux/targeted/contexts/files/file_contexts /sysroot/ >> Can't stat exclude path...

On Thu, Mar 10, 2016 at 10:14 AM, Hans de Goede <hdegoede at redhat.com> wrote: > Add support for clover / OpenCL kernel input parameters. > > Signed-off-by: Hans de Goede <hdegoede at redhat.com> > --- > .../drivers/nouveau/codegen/nv50_ir_from_tgsi.cpp | 18 +++++++++++++++--- > 1 file changed, 15 insertions(+), 3 deletions(-) > > diff --git

...> because they only operate on a throw-away overlay): > > > > qemu-img create -f qcow2 throwaway.qcow2 /mnt/knp1-vm-otp02/knp1-vm- > > otp02.vmdk I missed out the -b flag: qemu-img create -f qcow2 throwaway.qcow2 -b /mnt/knp1-vm-otp02/knp1-vm-otp02.vmdk anyway ... > setfiles: /sysroot/etc/selinux/targeted/contexts/files/file_contexts: Multiple same specifications for /.*. > /sysroot/etc/selinux/targeted/contexts/files/file_contexts: Invalid argument > guestfsd: error: Can't stat exclude path "/sysroot/selinux", No such file or directory - ignoring....

On Mon, Mar 05, 2018 at 02:03:17PM +0000, Зиновик Игорь Анатольевич wrote: > Hello. > > I'm trying to convert VMware based virtual machines (CentOS 7.2) and output them into oVirt. > virt-v2v fails with following error: > setfiles: /sysroot/etc/selinux/targeted/contexts/files/file_contexts: Multiple same specifications for /.*. > > File `file_contexts' looks same like in recent CentOS 7.4. My conversion server is Fedora 28 (Rawhide), since > it contains virt-v2v 1.38. This has got to be a bug of some kind in t...

[This email is either empty or too large to be displayed at this time]

This shows which files are being relabelled. Also only use -q (suppress non-error output) when we are not verbose. --- daemon/selinux-relabel.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/daemon/selinux-relabel.c b/daemon/selinux-relabel.c index 2f48ee6..e7da42d 100644 --- a/daemon/selinux-relabel.c +++ b/daemon/selinux-relabel.c @@ -112,8 +112,11 @@

On Thu, Mar 10, 2016 at 10:27 AM, Samuel Pitoiset <samuel.pitoiset at gmail.com> wrote: > > > On 03/10/2016 04:23 PM, Ilia Mirkin wrote: >> >> On Thu, Mar 10, 2016 at 10:14 AM, Hans de Goede <hdegoede at redhat.com> >> wrote: >>> >>> Add support for clover / OpenCL kernel input parameters. >>> >>> Signed-off-by: Hans de

On Wed, Nov 16, 2016 at 11:31:40AM -0500, Derek Atkins wrote: > > Running `virt-v2v -v -x ...' and observing the output will give you a > > good idea of what precisely it was doing for those hours. > > Well, as I said in my original email, it was hanging at running setfiles: > > commandrvf: stdout=n stderr=y flags=0x0 > commandrvf: setfiles -F -e /sysroot/dev -e /sysroot/proc -e > /sysroot/selinux -e /sysroot/sys -r /sysroot -q > /sysroot/etc/selinux/targeted/contexts/files/file_contexts /sysroot/ > Can't stat exclude path "/sysroot/selinux&...

Policycoreutils, which includes the 'setfiles' utility which we use, is badly broken in Fedora 26. https://bugzilla.redhat.com/show_bug.cgi?id=1433577 This bug affects a few things because it completely breaks SELinux relabelling. In particular, firstboot functionality fails on Fedora guests because the installed scripts are not labelle...

On Monday, 20 March 2017 19:14:46 CET Richard W.M. Jones wrote: > --- Such behaviour changes :-( LGTM, unless the default behaviour of setfiles changes soon... Thanks, -- Pino Toscano

...ysroot); > } > > - /* Suppress non-error output. */ > - ADD_ARG (argv, i, "-q"); > + if (verbose) > + ADD_ARG (argv, i, "-vv"); > + else > + /* Suppress non-error output. */ > + ADD_ARG (argv, i, "-q"); I've checked the setfiles code (since neither -h nor the manpage mention anything about that), and it seems -v is a simple switch. Since -vv behaves as -v, I think passing just -v should be enough. LGTM otherwise. Thanks, -- Pino Toscano

Rewrite the relabel API to read the policy configured in the guest, invoking setfiles (added as part of the appliance, as part of policycoreutils) to relabel the specified root. In case of failure at any point of the process, a touch of .autorelabel in the root is tried as last-attempt measure to do the relabel. Considering that running SELinux tools in the appliance might be affec...

...oot) in order > to get the default policy. Note that not specifying a root could lead to issues, as the file contexts are relative to a root. So if I say to relabel the path /guestmountpoint/etc/myconfig according to some /path/of/file_contexts without specifying what is the root, how should setfiles know that path is /etc/myconfig mounted at /guestmountpoint? At this point I'm thinking the best option would be making the root a normal (mandatory) argument, leaving path and contexts as optional (with the former being "/" as default value, and the latter as "find it from...