[Users] sanlock issues

oVirt Node Hypervisor release 2.5.0 (2.0.fc17) Can't start a VM. Same error in any of /var/log/libvirt/qemu/vmname.log libvir: Locking error : unsupported configuration: Read/write, exclusive access, disks were present, but no leases specified I've tried several suggestions including: modprobe softdog systemctl restart wdmd.service systemctl restart sanlock.service I haven't changed the default configs but I'm heading there next.

On 08/07/2012 02:35 AM, Jacob Wyatt wrote:
oVirt Node Hypervisor release 2.5.0 (2.0.fc17)
Can't start a VM. Same error in any of /var/log/libvirt/qemu/vmname.log
libvir: Locking error : unsupported configuration: Read/write, exclusive access, disks were present, but no leases specified
I've tried several suggestions including:
modprobe softdog systemctl restart wdmd.service systemctl restart sanlock.service
I haven't changed the default configs but I'm heading there next. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
What does "grep -v ^# /etc/libvirt/qemu-sanlock.conf" say? Have you tried `/usr/lib/systemd/systemd-vdsmd reconfigure` ?

Hi! Since I'm a storage guy, I would like to know more about this! Are these watchdog/SANlock features LVM functionality, or is it a part of oVirt? Since I can't find any info about it in oVirt wiki documentation... Since LUN's are mapped to all the machines in the cluster, I guess it is not on that level, but more on the Logical Volume level, since it is the LV that is used by the host. I would like to get some deeper info about how the the storage architecture is implemented, and what the storage strategy is for the future...Someone can enlighten me? Show me to some documentation? Rgrds Johan -----users-bounces@ovirt.org skrev: ----- Till: Jacob Wyatt <jwyatt@ggc.edu> Från: Mark Wu Sänt av: users-bounces@ovirt.org Datum: 2012.08.07 09:14 Kopia: "users@ovirt.org" <users@ovirt.org> Ärende: Re: [Users] sanlock issues On 08/07/2012 02:35 AM, Jacob Wyatt wrote:
oVirt Node Hypervisor release 2.5.0 (2.0.fc17)
Can't start a VM. Same error in any of /var/log/libvirt/qemu/vmname.log
libvir: Locking error : unsupported configuration: Read/write, exclusive access, disks were present, but no leases specified
I've tried several suggestions including:
modprobe softdog systemctl restart wdmd.service systemctl restart sanlock.service
I haven't changed the default configs but I'm heading there next. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
What does "grep -v ^# /etc/libvirt/qemu-sanlock.conf" say? Have you tried `/usr/lib/systemd/systemd-vdsmd reconfigure` ? _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On 08/07/2012 03:47 PM, Johan Kragsterman wrote:
Hi!
Since I'm a storage guy, I would like to know more about this! Are these watchdog/SANlock features LVM functionality, or is it a part of oVirt? Since I can't find any info about it in oVirt wiki documentation... http://wiki.ovirt.org/wiki/SANLock Hope it helps for you.
Since LUN's are mapped to all the machines in the cluster, I guess it is not on that level, but more on the Logical Volume level, since it is the LV that is used by the host.
I would like to get some deeper info about how the the storage architecture is implemented, and what the storage strategy is for the future...Someone can enlighten me? Show me to some documentation?
Rgrds Johan
-----users-bounces@ovirt.org skrev: ----- Till: Jacob Wyatt<jwyatt@ggc.edu> Från: Mark Wu Sänt av: users-bounces@ovirt.org Datum: 2012.08.07 09:14 Kopia: "users@ovirt.org"<users@ovirt.org> Ärende: Re: [Users] sanlock issues
On 08/07/2012 02:35 AM, Jacob Wyatt wrote:
oVirt Node Hypervisor release 2.5.0 (2.0.fc17)
Can't start a VM. Same error in any of /var/log/libvirt/qemu/vmname.log
libvir: Locking error : unsupported configuration: Read/write, exclusive access, disks were present, but no leases specified
I've tried several suggestions including:
modprobe softdog systemctl restart wdmd.service systemctl restart sanlock.service
I haven't changed the default configs but I'm heading there next. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
What does "grep -v ^# /etc/libvirt/qemu-sanlock.conf" say?
Have you tried `/usr/lib/systemd/systemd-vdsmd reconfigure` ?
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

# grep -v ^# /etc/libvirt/qemu-sanlock.conf auto_disk_leases=0 require_lease_for_disks=0 I did try systemd-vdsmd reconfigure. ________________________________________ From: Mark Wu [wudxw@linux.vnet.ibm.com] What does "grep -v ^# /etc/libvirt/qemu-sanlock.conf" say? Have you tried `/usr/lib/systemd/systemd-vdsmd reconfigure` ?
participants (3)
-
Jacob Wyatt
-
Johan Kragsterman
-
Mark Wu