Re: [Users] Sanlock issue when trying to start vm

On 06/20/2012 08:33 AM, Dennis Jacobfeuerborn wrote: > On 06/20/2012 08:17 AM, Rami Vaknin wrote: >> On 06/19/2012 09:36 PM, Dennis Jacobfeuerborn wrote: >>> Hi, >>> after getting the 3.1 beta engine and a host set up I now get an error >>> when >>> trying to start a vm. >>> >>> Engine reports this: >>> VM myvm is down. Exit message: internal error Failed to open socket to >>> sanlock daemon: No such file or directory. >> Please take a look at the following bugs: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=832935 >> https://bugzilla.redhat.com/show_bug.cgi?id=832056 > Thanks, after modprobe softdog and restarting wdmd and sanlock I was able > to start the VM. Unfortunately my experiment with using nested VMs to fake > nodes didn't pan out (the "guest-in-guest" booted for a bit and then froze). > > Is there a way to use pure qemu guests for testing (like in devstack)? > While I do have two systems that support hardware virtualization i cannot > reinstall either of them to use them as a host. > > Regards, > Dennis > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users The CentOS builds include a plugin called vdsm-hook-simpleqemu I think I saw the hook sitting in Git as well so that plug-in might do what you are looking for?