I was able to resolve this by disabling the HW watchdog model, and relying on "softdog" eg.

blacklist iTCO_wdt

blacklist iTCO_vendor_support

I guess it's more of the kernel not supporting it rather than an oVirt issue.

What are the implications in this, based on the ovirt wiki wdmd is used as sort of a fencing mechanism to reboot the host on failure. Wouldn't this be considered redundant, considering power management exists also from the ovirt-engine? Are there any downsides in using softdog?

On Thu, Jul 31, 2014 at 6:45 PM, Allon Mureinik <amureini@redhat.com> wrote:

yikes.
would you mind opening a bug on this, so we can track the issue properly?

From: "Andrew Lau" <andrew@andrewklau.com>
To: "users" <users@ovirt.org>
Sent: Thursday, July 31, 2014 4:19:56 AM
Subject: [ovirt-users] Can't attach storage domain / Unsupported watchdog

Hi,

I'm trying out some new boards (Intel Avotons), and it appears wdmd does not like the watchdog device it provides.

Everything in oVirt 3.4.3 seems to run fine until it comes to adding a storage device. It gives me an error about Cannot acquire host id

vdsm logs,
http://fpaste.org/122164/67695431/

# service wdmd start
(logs)
wdmd[14062]: wdmd started S0 H1 G0
wdmd[14062]: /dev/watchdog failed to set timeout
wdmd[14062]: /dev/watchdog disarmed
wdmd[14062]: no watchdog device, load a watchdog driver

# service wdmd status
wdmd dead but subsys locked

I can't seem to find any documentation on what wdmd does, could someone explain?

Thanks,
Andrew

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users