OpenNebula

Hi Joaquin

It seems that the monitor probe sends information while the VM is snapshoting... oned then assumes it's been powered off and clears the snapshots in its internal data. When the VM is found again it's moved to running but the snapshots are gone.

This will be solved by preserving snapshots during a powercycle, till then try to tune the timing of the action and the monitoring cycle (although playing with timing in a distributed system is not a good idea...).

Alternatively we can take a look to the monitor probe to report the VM as active while snapsotting.

Thanks

Hi, can the alternative solution of reporting the VM as active when snapshoting be implemented before the 4.14 release?
Unfortunately, tuning the timing of the action isn't possible since the idea is to revert as soon as the job has finished (and the job duration is different in each run). I can try including dead waiting times to even out the jobs to be able to sync to the monitoring cycle but it's not a great solution performance wise.

Thanks

Joaquin Rinaudo wrote:

Hi, can the alternative solution of reporting the VM as active when snapshoting be implemented before the 4.14 release?
Unfortunately, tuning the timing of the action isn't possible since the idea is to revert as soon as the job has finished (and the job duration is different in each run). I can try including dead waiting times to even out the jobs to be able to sync to the monitoring cycle but it's not a great solution performance wise.

Thanks

We need to find out what's the state of a VM while snapshotting, basically the probe executes a virsh list and a dominfo. You may try to hack the state here:

https://github.com/OpenNebula/one/blob/master/src/vmm_mad/remotes/poll_xen_kvm.rb#L68

and here:

https://github.com/OpenNebula/one/blob/master/src/vmm_mad/remotes/poll_xen_kvm.rb#L271

When snapshotting (both taking and reverting a snapshot) the state is set to paused.

virsh --connect qemu:///system --readonly dominfo one-220

Id:             2
    Name:           one-220
    UUID:           87892a7b-f829-bb85-6d99-60b1a2d40547
    OS Type:        hvm
    State:          paused
    CPU(s):         1
    CPU time:       622218.4s
    Max memory:     2097152 KiB
    Used memory:    2097152 KiB
    Persistent:     no
    Autostart:      disable
    Managed save:   no

The commit https://github.com/OpenNebula/one/commit/87cef75a8e42cf4f74a05160255dfb7796690bf7#diff-650e58e49530115caad6187b7283aa25L266 already fixed the issue.

Joaquín