SELinux label problem on a VM

[Patrick O'Callaghan]

I have a small F29 Server VM (KVM/QEMU) which has not changed recently
and has worked consistently for several months. Now when I try to boot
it I get:

Requested operation is not valid: Setting different SELinux label on
/home/poc/VM/vm-f29b.qcow2 which is already in use

I haven't touched any SElinux settings, though I do update my host F30
system on a daily basis so something may have changed.

The current context for that file is:

$ ls -lZ vm-f29b.qcow2
-rw-------. 1 qemu qemu system_u:object_r:svirt_image_t:s0:c467,c977 21478375424 Aug 11
11:14 vm-f29b.qcow2

Any thoughts on what I should look at?

poc

[Ed Greshko]

On 8/14/19 6:07 PM, Patrick O'Callaghan wrote:
>  I have a small F29 Server VM (KVM/QEMU) which has not changed
> recently
>  and has worked consistently for several months. Now when I try to boot
>  it I get:
>
>  Requested operation is not valid: Setting different SELinux label on
> /home/poc/VM/vm-f29b.qcow2 which is already in use
>
>  I haven't touched any SElinux settings, though I do update my host F30
>  system on a daily basis so something may have changed.
>
>  The current context for that file is:
>
>  $ ls -lZ vm-f29b.qcow2
>  -rw-------. 1 qemu qemu system_u:object_r:svirt_image_t:s0:c467,c977 21478375424 Aug 11
> 11:14 vm-f29b.qcow2
>
>  Any thoughts on what I should look at? 
At first glance seeing "which is already in us" would prompt me to run lsof to
see how
true that may be.


-- 
If simple questions can be answered with a simple google query then why are there so many
of them?

[Patrick O'Callaghan]

On Wed, 2019-08-14 at 18:23 +0800, Ed Greshko wrote:
>  On 8/14/19 6:07 PM, Patrick O'Callaghan wrote:
>  > I have a small F29 Server VM (KVM/QEMU) which has not changed recently
>  > and has worked consistently for several months. Now when I try to boot
>  > it I get:
>  > 
>  > Requested operation is not valid: Setting different SELinux label on
> /home/poc/VM/vm-f29b.qcow2 which is already in use
>  > 
>  > I haven't touched any SElinux settings, though I do update my host F30
>  > system on a daily basis so something may have changed.
>  > 
>  > The current context for that file is:
>  > 
>  > $ ls -lZ vm-f29b.qcow2
>  > -rw-------. 1 qemu qemu system_u:object_r:svirt_image_t:s0:c467,c977 21478375424 Aug
> 11 11:14 vm-f29b.qcow2
>  > 
>  > Any thoughts on what I should look at?
>  
>  At first glance seeing "which is already in us" would prompt me to run lsof to
> see how
>  true that may be. 
Yes, I forgot to mention I did that. 'lsof' returns nothing.

poc

[Ed Greshko]

On 8/14/19 8:13 PM, Patrick O'Callaghan wrote:
>  Yes, I forgot to mention I did that. 'lsof' returns nothing.
I see.

Well, I'm not having any problems.  But I did notice you've changed the
"default" location
for your images.

Would it be possible to move it to the default location to see if the problem persists?

-- 
If simple questions can be answered with a simple google query then why are there so many
of them?

[Patrick O'Callaghan]

On Thu, 2019-08-15 at 08:35 +0800, Ed Greshko wrote:
>  On 8/14/19 8:13 PM, Patrick O'Callaghan wrote:
>  > Yes, I forgot to mention I did that. 'lsof' returns nothing.
>  
>  I see.
>  
>  Well, I'm not having any problems.  But I did notice you've changed the
> "default" location
>  for your images.
>  
>  Would it be possible to move it to the default location to see if the problem persists?
I'll try that, but a) it's been that way since I created it, and b) I
also have a Windows 10 VM and it's not having any problems. One
difference is that the Windows VM runs on its own raw drive, not on a
Qcow2 file, so that might be it.

poc

[Chris Murphy]

On Wed, Aug 14, 2019 at 4:08 AM Patrick O'Callaghan
<pocallaghan(a)gmail.com&gt; wrote:
>  I have a small F29 Server VM (KVM/QEMU) which has not changed recently
>  and has worked consistently for several months. Now when I try to boot
>  it I get:
>
>  Requested operation is not valid: Setting different SELinux label on
> /home/poc/VM/vm-f29b.qcow2 which is already in use 
I don't know if it's related but I'm hitting this on Fedora 31 in testing
https://bugzilla.redhat.com/show_bug.cgi?id=1748079

The one thing I did right before this started, was a complete relabel.
And yet 'enforcing=0' does not fix the problem, whereas 'selinux=0'
does fix it.

If you're still hitting this you might mention in that bug report what
version of selinux-policy you're using.



-- 
Chris Murphy

[Patrick O'Callaghan]

On Mon, 2019-09-02 at 11:19 -0600, Chris Murphy wrote:
>  On Wed, Aug 14, 2019 at 4:08 AM Patrick O'Callaghan
>  <pocallaghan(a)gmail.com&gt; wrote:
>  > I have a small F29 Server VM (KVM/QEMU) which has not changed recently
>  > and has worked consistently for several months. Now when I try to boot
>  > it I get:
>  > 
>  > Requested operation is not valid: Setting different SELinux label on
> /home/poc/VM/vm-f29b.qcow2 which is already in use
>  
>  I don't know if it's related but I'm hitting this on Fedora 31 in testing
>  https://bugzilla.redhat.com/show_bug.cgi?id=1748079
>  
>  The one thing I did right before this started, was a complete relabel.
>  And yet 'enforcing=0' does not fix the problem, whereas 'selinux=0'
>  does fix it.
>  
>  If you're still hitting this you might mention in that bug report what
>  version of selinux-policy you're using. 
It went away after a system update so I never did track down what was
causing it.

poc