2012/10/13 Dan Kenigsberg <danken@redhat.com>
On Sat, Oct 13, 2012 at 11:25:37AM +0100, Alexandre Santos wrote:
Hi, after getting to the oVirt Node console (F2) I figured out that selinux wasn't allowing the sanlock, so I entered the setsebool virt_use_sanlock 1 and the problem is fixed.
Which version of vdsm is istalled on your node? and which selinux-policy? sanlock should work out-of-the-box.
vdsm-4.10.0-10.fc17 on /etc/sysconfig/selinux SELINUX=enforcing SELINUXTYPE=targeted
However, I started getting permission denied error when trying to start
the
VM that was created on that NFS share. On the ovirt node console, I noticed that the user.group of that share was nobody.nobody instead of vdsm.kvm. I followed the instruction on the wiki about anonguid and anonuid but no luck at all. This was an Ubuntu nfs server. I Installed a FC17 VM on this Ubuntu and tried again and it worked at the first time :-)
I've seen these problem when using nfs v4 without defining it's id mapper properly. The issue went away when (down?)grading to v3.
Ubuntu has a KVM group with guid = 106.
Dan.