Hello Dave, AFAIK, there are wdmd and sanlock bugs now: https://bugzilla.redhat.com/show_bug.cgi?id=832056 https://bugzilla.redhat.com/show_bug.cgi?id=832935 https://bugzilla.redhat.com/show_bug.cgi?id=831908 (selinux enable) https://bugzilla.redhat.com/show_bug.cgi?id=820173 In addition, for sanlock version >= 2.1-1, if you append SANLOCKOPTS="-w 0" into /etc/sysconfig/sanlock then restart sanlock service, sanlock will stop due to a segfault error, please see the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=831906 In fact, we need to updates docs due to sanlock configuration change, and should append/uncomment SANLOCKOPTS="-U sanlock -G sanlock -w 0" line in /etc/sysconfig/sanlock instead of old SANLOCKOPTS="-w 0". But, I haven't try sanlock on F17, maybe, it's different from RHEL6, and hope these are helpful for you ;) Good Luck! Alex ----- Original Message ----- From: "Dave Allan" <dallan@xxxxxxxxxx> To: libvir-list@xxxxxxxxxx Sent: Saturday, June 30, 2012 9:59:12 AM Subject: Re: sanlock on F17 On Fri, Jun 29, 2012 at 08:06:34PM -0400, Dave Allan wrote: > I just tried to set up sanlock on F17 using the instructions at > http://libvirt.org/locking.html, but libvirtd refuses to start with > the sanlock error in the logs: > > Jun 29 19:56:20 nienna sanlock[8423]: 19846 open error -13 > /var/lib/libvirt/sanlock/__LIBVIRT__DISKS__ > > I confirmed that user sanlock can create, read and write files in > /var/lib/libvirt/sanlock Also disabling selinux does not help. > The only thing I can think of that's slightly odd about my setup is > that I'm only concerned with the local machine, so that directory is > not an NFS mount. Anybody have any thoughts on what's going wrong > here? > > TIA, > Dave -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list