----- Original Message -----
From: "Brian Vetter" <bjvetter@gmail.com> To: "Federico Simoncelli" <fsimonce@redhat.com> Cc: "Vered Volansky" <vered@redhat.com>, users@ovirt.org, "David Teigland" <teigland@redhat.com> Sent: Wednesday, October 24, 2012 5:48:21 AM Subject: Re: [Users] Error creating the first storage domain (NFS)
Ugh. Spoke a little too soon. While I got past my problem creating a storage domain, I ran into a new sanlock issue.
When trying to run a VM (the first one so I can create a template), I get an error in the admin UI:
VM DCC4.0 is down. Exit message: Failed to acquire lock: Permission denied.
On a lark, I turned off selinux enforcement and tried it again. It worked just fine.
So what selinux option do I need to enable to get it to work? The only other sanlock specific settings I saw are:
sanlock_use_fusefs --> off sanlock_use_nfs --> on sanlock_use_samba --> off
Do I turn these all on or is there some other setting I need to enable?
No for nfs you just need sanlock_use_nfs. I'd say that if you could verify the scratch build that I prepared at: http://koji.fedoraproject.org/koji/taskinfo?taskID=4620480 (up until starting a vm), then all the new selinux errors/messages that you see in the audit log (/var/log/audit/audit.log) are issues that should be reported to the selinux-policy package. -- Federico