Public bug reported: After enabling sanlock in libvirt, I get the following error: 2013-12-19 20:34:17.499+0000: 5482: error : virLockManagerPluginNew:163 : Plugin /usr/lib/libvirt/lock-driver/sanlock.so not accessible: No such file or directory 2013-12-19 20:34:17.499+0000: 5482: error : virStateInitialize:838 : Initialization of QEMU state driver failed: Plugin /usr/lib/libvirt/lock-driver/sanlock.so not accessible: No such file or directory 2013-12-19 20:34:17.499+0000: 5482: error : daemonRunStateInit:905 : Driver state initialization failed
/usr/lib/libvirt/lock-driver only contains lockd.so . I have installed sanlock, but it is pretty pointless without a libvirt driver for it. For any real sized vm deployment with san storage I would assume this to be a show stopper, since you could accidentally clobber whole machines. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: libvirt sanlock -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1263162 Title: libvirt missing sanlock plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1263162/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs