Hi, this was indeed a bug in our code. It happened when ballooning was enabled (Cluster / Optimization), but no balloon device was configured (Vm / Resource Allocation).
This is fixed by http://gerrit.ovirt.org/#/c/21783/ and tracked by https://bugzilla.redhat.com/show_bug.cgi?id=1035297. We will merge it to master momentarily and then update the released version as well. Thanks for the report. -- Martin Sivák [email protected] Red Hat Czech RHEV-M SLA / Brno, CZ ----- Original Message ----- > On 11/27/2013 04:10 PM, Gianluca Cecchi wrote: > > On Wed, Nov 27, 2013 at 3:07 PM, Jakub Bittner wrote: > > > >> Hi, > >> I had same issue and sollution was to shutdown all VMs, upgrade nodes and > >> management to latest stable, restart nodes and power on VMs. It happend > >> from > >> 3.1 to 3.2 I think. > > > > In my case, at least for the host selection on boot problem, I already > > powered off all the infra but didn't solve... > > _______________________________________________ > > Users mailing list > > [email protected] > > http://lists.ovirt.org/mailman/listinfo/users > > > > did you VMs have the baloon device enabled? > _______________________________________________ > Users mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
