Re: [Libguestfs] [rhev-tech] virt-v2v failure during selinux re-lable

try to ask libguestfs(a)redhat.com if you don't get answer here. On Wed, Dec 28, 2016 at 11:04 PM, John Call <jcall(a)redhat.com&gt; wrote: > Hi everybody, > > I've had great success migrating ~40 VMs from a KVM environment into > RHV. However, recently my virt-v2v process broke on a few VMs. Has > anybody seen this before? Is there a way to simply bypass the relabel > process? This is being documented in case #01764770 (VM XML and complete > logs there) > > Command ran (as root) > # virt-v2v --colours --network ovirtmgmt -i libvirtxml -o rhev -oa sparse > -os /var/lib/exports/export tlrampy1.eams.dir.ca.gov.xml > > <snip...> > > 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/ > /sysroot/etc/selinux/targeted/contexts/files/file_contexts: Invalid > argument > guestfsd: error: /sysroot/etc/selinux/targeted/contexts/files/file_contexts: > Invalid argument: Success > guestfsd: main_loop: proc 467 (selinux_relabel) took 0.02 seconds > libguestfs: trace: v2v: selinux_relabel = -1 (error) > virt-v2v: error: libguestfs error: selinux_relabel: > /sysroot/etc/selinux/targeted/contexts/files/file_contexts: Invalid > argument: Success > > > > Thank you, > > John Call > Red Hat - Solutions Architect > jcall(a)redhat.com > (714) 267-8802 >