Opennebula 5 beta snapshot & host

Community Support
1

Hi team ,

Thank you all for your prompt supports .
While testing Opennebula 5 beta , i have found some serious boot problems .

1 . I have rebooted my opennebula host while all VM’s are powered on . But after boot back, sunstone GUI shows all vm’s are power on . But actually all machines are in power off state . Because of that I forced to run Recovery > Delete .

2 . I took snapshot of one machine and got success . After shutdown and power on that vm , snapshot’s are gone . I thing this issue is also stick with current stable release 4.14 .

Is it bug?

Regards

2

1 . I have rebooted my opennebula host while all VM’s are powered on . But
after boot back, sunstone GUI shows all vm’s are power on . But actually
all machines are in power off state . Because of that I forced to run Recovery

Delete .

Did you wait a bit for the status update? The process is as follows:

1.- Host goes down
2.- Monitor time expires for the host
3.- OpenNebula tries to restart the monitoring probes
4.- Restarting fails and VMs goes to unknown
5.- OpenNebula periodically tries to recover the host. Eventually it’ll be
up and probes restart
6.- No information about the VMs is found in the monitor info for the host.
VMs are moved to poweroff

This steps takes time, the timeouts can be tuned though

2 . I took snapshot of one machine and got success . After shutdown and
power on that vm , snapshot’s are gone . I thing this issue is also stick
with current stable release 4.14 .

Is it bug?

It is a current limitation of libvirt. The snapshots are kept in the image
but once you “undefine” the domain (e.g. to poweroff or migrate) the
snapshots are gone. There is a flag in oned.conf to modifiy this behavior,
so as soon as this works in libvirt snapshots will not be cleaned.

Regards

Visit Topic
https://forum.opennebula.io/t/opennebula-5-beta-snapshot-host/2382/1
or reply to this email to respond.

You have mailing list mode enabled. To stop receiving notifications for
this particular topic, click here
https://forum.opennebula.io/t/opennebula-5-beta-snapshot-host/2382/unsubscribe
.

To unsubscribe from these emails, change your user preferences
https://forum.opennebula.io/my/preferences or click here
<reply@forum.opennebula.org?subject=unsubscribe> to unsubscribe via email.

Ruben S. Montero, PhD
Project co-Lead and Chief Architect
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | rsmontero@opennebula.org | @OpenNebula

3

Hi,

From the morning till now (5 hours) nothing happens for that freezed machines including virtual router . Its not going to any error states , still “Running” .
One of the machine ID is one-7 .While opening that machine catalog , i got oned.log message like below ,

Mon Jun 13 12:46:23 2016 [Z0][ReM][D]: Req:2160 UID:0 VirtualMachineInfo invoked , 7
Mon Jun 13 12:46:23 2016 [Z0][ReM][D]: Req:2160 UID:0 VirtualMachineInfo result SUCCESS, "<VM><ID>7</ID><UID>0..."

[root@beta ~]# onevm list
    ID USER     GROUP    NAME            STAT UCPU    UMEM HOST             TIME
     3 oneadmin oneadmin vr-IPT-Router-0 runn  1.0    128M beta.cloud   1d 02h25
     7 oneadmin oneadmin CentOS 7.1 - KV runn  1.0    768M beta.cloud   0d 21h23
     8 oneadmin oneadmin CentOS 7.1 - KV runn  1.0    768M beta.cloud   0d 04h01

[root@beta ~]# virsh list
 Id    Name                           State
----------------------------------------------------
 3     one-8                          running
4

Can you send oned.log, at least the messages related to beta.cloud…

BTW, is this the last 5.0 release?

5

Yes it is , latest june 7 release .

Mon Jun 13 12:37:53 2016 [Z0][InM][D]: Host beta.cloud.com (0) successfully monitored.
Mon Jun 13 12:37:53 2016 [Z0][VMM][D]: VM 3 successfully monitored: DISK_SIZE=[ID=0,SIZE=53] DISK_SIZE=[ID=1,SIZE=1] 
Mon Jun 13 12:37:53 2016 [Z0][VMM][D]: VM 7 successfully monitored: DISK_SIZE=[ID=0,SIZE=447] DISK_SIZE=[ID=1,SIZE=1] 
Mon Jun 13 12:37:53 2016 [Z0][VMM][D]: VM 8 successfully monitored: DISK_SIZE=[ID=0,SIZE=799] DISK_SIZE=[ID=1,SIZE=1]  STATE=a CPU=0.0 MEMORY=786432 NETRX=648 NETTX=37608
Mon Jun 13 12:37:59 2016 [Z0][ReM][D]: Req:3376 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Mon Jun 13 12:37:59 2016 [Z0][ReM][D]: Req:3376 UID:0 VirtualMachinePoolInfo result SUCCESS, "<VM_POOL><VM><ID>3</..."
Mon Jun 13 12:37:59 2016 [Z0][ReM][D]: Req:3248 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Mon Jun 13 12:37:59 2016 [Z0][ReM][D]: Req:3248 UID:0 VirtualMachinePoolInfo result SUCCESS, "<VM_POOL><VM><ID>3</..."
Mon Jun 13 12:38:04 2016 [Z0][MKP][D]: Monitoring marketplace OpenNebula Public (0)
Mon Jun 13 12:38:05 2016 [Z0][MKP][D]: Monitoring marketplace Market1 (100)
Mon Jun 13 12:38:05 2016 [Z0][MKP][D]: Marketplace Market1 (100) successfully monitored.
Mon Jun 13 12:38:06 2016 [Z0][MKP][D]: Marketplace OpenNebula Public (0) successfully monitored.
Mon Jun 13 12:38:13 2016 [Z0][InM][D]: Host beta.cloud.com (0) successfully monitored.
Mon Jun 13 12:38:13 2016 [Z0][VMM][D]: VM 3 successfully monitored: DISK_SIZE=[ID=0,SIZE=53] DISK_SIZE=[ID=1,SIZE=1] 
Mon Jun 13 12:38:13 2016 [Z0][VMM][D]: VM 7 successfully monitored: DISK_SIZE=[ID=0,SIZE=447] DISK_SIZE=[ID=1,SIZE=1] 
Mon Jun 13 12:38:13 2016 [Z0][VMM][D]: VM 8 successfully monitored: DISK_SIZE=[ID=0,SIZE=799] DISK_SIZE=[ID=1,SIZE=1]  STATE=a CPU=0.0 MEMORY=786432 NETRX=648 NETTX=37608
Mon Jun 13 12:38:29 2016 [Z0][ReM][D]: Req:9168 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Mon Jun 13 12:38:29 2016 [Z0][ReM][D]: Req:9168 UID:0 VirtualMachinePoolInfo result SUCCESS, "<VM_POOL><VM><ID>3</..."
Mon Jun 13 12:38:29 2016 [Z0][ReM][D]: Req:1072 UID:0 VirtualMachinePoolInfo invoked , -2, -1, -1, -1
Mon Jun 13 12:38:29 2016 [Z0][ReM][D]: Req:1072 UID:0 VirtualMachinePoolInfo result SUCCESS, "<VM_POOL><VM><ID>3</..."
Mon Jun 13 12:38:33 2016 [Z0][InM][D]: Host beta.cloud.com (0) successfully monitored.
Mon Jun 13 12:38:33 2016 [Z0][VMM][D]: VM 3 successfully monitored: DISK_SIZE=[ID=0,SIZE=53] DISK_SIZE=[ID=1,SIZE=1] 
Mon Jun 13 12:38:33 2016 [Z0][VMM][D]: VM 7 successfully monitored: DISK_SIZE=[ID=0,SIZE=447] DISK_SIZE=[ID=1,SIZE=1] 
Mon Jun 13 12:38:33 2016 [Z0][VMM][D]: VM 8 successfully monitored: DISK_SIZE=[ID=0,SIZE=799] DISK_SIZE=[ID=1,SIZE=1]  STATE=a CPU=0.0 MEMORY=786432 NETRX=648 NETTX=37608
Mon Jun 13 12:38:33 2016 [Z0][InM][D]: Monitoring datastore default (1)
Mon Jun 13 12:38:34 2016 [Z0][InM][D]: Monitoring datastore files (2)
Mon Jun 13 12:38:34 2016 [Z0][ImM][D]: Datastore default (1) successfully monitored.
Mon Jun 13 12:38:34 2016 [Z0][ImM][D]: Datastore files (2) successfully monitored.
Mon Jun 13 12:38:47 2016 [Z0][MKP][I]: --Mark--
Mon Jun 13 12:38:53 2016 [Z0][InM][D]: Host beta.cloud.com (0) successfully monitored.
6

THANKS a lot. I can confirm this is a bug.

7

Hi ,

While checking bug report about vm snapshot , i found below link and its closed .

http://dev.opennebula.org/issues/3740

Where i need to add KEEP_SNAPSHOTS option to get the previous snapshots after power off / reboot ?

Regards

8

In the VM_MAD attribute, in oned.conf

VM_MAD = [
    NAME           = "kvm",
    SUNSTONE_NAME  = "KVM",
    EXECUTABLE     = "one_vmm_exec",
    ARGUMENTS      = "-t 15 -r 0 kvm",
    DEFAULT        = "vmm_exec/vmm_exec_kvm.conf",
    TYPE           = "kvm",
    KEEP_SNAPSHOTS = "no",
    IMPORTED_VMS_ACTIONS = "terminate, terminate-hard, hold, release,
suspend,
        resume, delete, reboot, reboot-hard, resched, unresched,
disk-attach,
        disk-detach, nic-attach, nic-detach, snap-create, snap-delete"
]

But note that this may not be supported by the hypervisor.