Nope. Nothing more in logs.
My guess is that the timeout problem generates the error.
However, in reality if you run "mount", you have the target partitions mounted....

Therefore, I guess the problem is to understand why "dev/watchdog0 failed to set timeout"....

Any info needed, just ask


2013/12/21 Federico Simoncelli <fsimonce@redhat.com>
----- Original Message -----
> From: "Pascal Jakobi" <pascal.jakobi@gmail.com>
> To: "Federico Simoncelli" <fsimonce@redhat.com>, users@ovirt.org
> Sent: Friday, December 20, 2013 11:54:21 PM
> Subject: Re: [Users] AcquireHostId problem
>
> Dec 20 23:43:59 lab2 kernel: [183033.639261] softdog: Software Watchdog
> Timer: 0.08 initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0
> (nowayout=0)
> Dec 20 23:44:11 lab2 systemd[1]: Starting Watchdog Multiplexing Daemon...
> Dec 20 23:44:11 lab2 wdmd[25072]: wdmd started S0 H1 G179
> Dec 20 23:44:11 lab2 systemd-wdmd[25066]: Starting wdmd: [  OK  ]
> Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog0 failed to set timeout
> Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog0 disarmed
> Dec 20 23:44:11 lab2 wdmd[25072]: /dev/watchdog1 armed with fire_timeout 60
> Dec 20 23:44:11 lab2 systemd[1]: Started Watchdog Multiplexing Daemon.
> Dec 20 23:45:33 lab2 rpc.mountd[2819]: authenticated mount request from
> 192.168.1.41:994 for /home/vdsm/data (/home/vdsm/data)
> Dec 20 23:45:39 lab2 rpc.mountd[2819]: authenticated mount request from
> 192.168.1.41:954 for /home/vdsm/data (/home/vdsm/data)
>
> Seems to work a bit.
> However I still get "unable to attach storage" when creating a domain....

It is probably a different error now. Anything interesting in vdsm.log?

--
Federico



--
Pascal Jakobi
116 rue de Stalingrad
93100 Montreuil, France
+33 6 87 47 58 19
Pascal.Jakobi@gmail.com