On Wed, May 14, 2014 at 11:20 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:

Hi Gianluca, reported issue should be already fixed in VDSM shipped with oVirt 3.4.1.
Check http://www.ovirt.org/OVirt_3.4.1_release_notes
for upgrade instructions.

Already done and all is ok.

But please see my point 4) in this answer into the thread regarding problems with updated vdsm and engine still on 3.4.0 in an AIO environment on Fedora 19:

http://lists.ovirt.org/pipermail/users/2014-May/024220.html

Gianluca