I am using Ovirt 3.2 on Fedora 18:

(the engine is built from sources).

I seem to have hit this bug:

in the following configuration:

Single host (no migrations)

Created a VM, installed an OS inside (Fedora18)

stopped the VM.

created template from it.

Created an additional VM from the template using thin provision.

Started the second VM.

in addition to the errors in the logs the storage domains (both data and ISO) crashed, i.e went to "unknown" and "inactive" states respectively. (see the attached engine.log)

I attached the VDSM and engine logs.

is there a way to work around this problem?

It happens repeatedly.

Yuval Meir