Hi Fabian,
The automatic reconnection bug was solved for OpenNebula 3.0 [1].
I agree with you that a lost DB connection could lead to inconsistencies...
but I don't think that's the case here, otherwise everything would stop
working, even the onehost list command.
Regards.
[1] http://dev.openneb
Hello
On 26.09.2011 13:44, Carlos Martín Sánchez wrote:
The host_shares contains the "running_vms" column; you need to update that
column value with OpenNebula stopped.
We are still trying to figure out what causes this bug, so if you come
across it again, it would be great if you could write d
Hi Steve,
I assume you are using OpenNebula 2.2.
The host_shares contains the "running_vms" column; you need to update that
column value with OpenNebula stopped.
We are still trying to figure out what causes this bug, so if you come
across it again, it would be great if you could write down the
We have a host which frequently underreports the number of
VM's it is running.. this is a problem because most
of our user templates are using a rank of "- RUNNING_VMS".
As you can see from the output included below, onehost list
and onehost show report only 5 running VM's but
onevm list reports
