----- Original Message ----- > From: "Dan Kenigsberg" <dan...@redhat.com> > To: "Alexandre Santos" <santosa...@gmail.com> > Cc: users@ovirt.org > Sent: Saturday, October 13, 2012 11:11:13 PM > Subject: Re: [Users] Can't start a VM - sanlock permission denied > > 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.
Just happened to me as well with oVirt node 2.5.2 (0.1.fc17) (Latest on http://wiki.ovirt.org/wiki/OVirt_3.1_release_notes#oVirt_Node) > > > > > 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. > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users