On Tuesday 8 May 2012 at 18:56, Frido Roose wrote:
> Hello,
>
> I wonder what the "open error -1" / "release open_disk error" messages in
> sanlock.log actually mean.
>
> I saw these messages in the log on a KVM host that rebooted, and after
> ru
e3900:/var/lib/libvirt/sanlock/ff9b82672a4dd869f9c9b38a6cbe3900:0
for 2,12,4232
598 open error -1 /var/lib/libvirt/sanlock/ff9b82672a4dd869f9c9b38a6cbe3900
598 r42 release open_disk error
/var/lib/libvirt/sanlock/ff9b82672a4dd869f9c9b38a6cbe3900
--
Frido Roose
_
On Thursday 5 April 2012 at 11:40, Daniel P. Berrange wrote:
> On Thu, Apr 05, 2012 at 11:36:55AM +0200, Frido Roose wrote:
> > Hello,
> >
> > I see there is an option with virsh attach-disk to set the cache to "none"
> > for raw devices, but I can't
know I can set this in virt-manager, but then I have to restart the VM to
apply the change, so this is an offline operation.
With virsh edit, I guess I also would have to restart the VM...
--
Frido Roose
Sent with Sparrow (http://www.sparrowm
On Wed, Mar 14, 2012 at 8:32 AM, Alex Jia wrote:
> **
> On 03/13/2012 10:42 PM, Frido Roose wrote:
>
> Hello,
>
> I configured libvirtd with the sanlock lock manager plugin:
>
> # rpm -qa | egrep "libvirt-0|sanlock-[01]"
> libvirt-lock-sanlock-0.9.4-23.el6_
