Hi, today I've decided to upgrade my 3.4 Ovirt cluster to 3.5/ The engine migration was OK. Everything was good .. after I want upgraded the node .. I've installed the rpm on the node and follow : http://www.ovirt.org/OVirt_3.5_Release_Notes#Install_.2F_Upgrade_from_Pre... . Now my vms cannot be started. I've got this error message : 2014-11-11 10:49:37,305 WARN [org.ovirt.engine.core.bll.RunVmCommand] (org.ovirt.thread.pool-8-thread-13) CanDoAction of action RunVm failed. Reasons:VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,SCHEDULING_NO_HOSTS 2014-11-11 10:49:37,307 INFO [org.ovirt.engine.core.bll.RunVmCommand] (org.ovirt.thread.pool-8-thread-13) Lock freed to object EngineLock [exclusiveLocks= key: 0fdea856-9aec-4300-8d88-4cfd330cf4ff value: VM , sharedLocks= ] There is a full log in attachment .. Any help will be appreciated ... James

Gilad, from your latest answer to the same referred thread, here: http://lists.ovirt.org/pipermail/users/2014-September/027891.html I sorted out that it was a problem of mine, coming from a 3.5-rc2 to 3.5-rc3.... now it actually seems that it is indeed a regression from 3.4 to 3.5. So I propose to consider something managing this for 3.5.1 so that a user upgrading from 3.4.x to 3.5.1 will not get this kind of nasty problem.