On 05/24/2012 01:05 PM, Carlos Martín Sánchez wrote:
Hi,
This is fixed in OpenNebula 3.4+, see [1]. I think you should be able to
apply these changes [2] in 3.2 without any problems.
Regarding your question, you can't force a VM in the suspended state to be
monitored and restored to the running
Hi,
This is fixed in OpenNebula 3.4+, see [1]. I think you should be able to
apply these changes [2] in 3.2 without any problems.
Regarding your question, you can't force a VM in the suspended state to be
monitored and restored to the running state, unless you change in the DB
the vm_pool columns
Hi,
I got:
Wed May 23 14:22:28 2012 [VMM][I]: ExitCode: 0
Wed May 23 14:22:28 2012 [VMM][W]: Adding custom monitoring attribute:
NAME one-588
Wed May 23 14:22:28 2012 [VMM][D]: Monitor Information:
CPU : 0
Memory: 3584000
Net_TX: 12001
Net_RX: 452
Wed May 23 1
