Re: Upgrading OS on hypervisors

2018-12-14 Thread Andrija Panic
No magic as Ivan said, you may want to check dynamic auto-convergence in case of busy VMs (high RAM change ram i.e. busy MSSQL servers and such) - qemu 2.5 needed for this, can be consumed from 4.11 and onwards - but might not be relevant in your case. Some very short interruption IS done - i.e.

Re: URGENT: Unable to schedule async job for command com.cloud.vm.VmWorkStart, unexpected exception

2018-12-14 Thread Andrija Panic
That's funny - does restarting mgmg helps ? I assume you restored full cloud DB "property"... On Fri, Dec 14, 2018, 09:42 Ugo Vasi Hi Andrija, > I restored database but now I can't see any instance, host or system vm. > On dashboard I see a real situation statistics but I can't see any data, > ne

Re: URGENT: Unable to schedule async job for command com.cloud.vm.VmWorkStart, unexpected exception

2018-12-14 Thread Ugo Vasi
Hi Andrija, I restored database but now I can't see any instance, host or system vm. On dashboard I see a real situation statistics but I can't see any data, neither via webUI nor via cloudmonkey... I verify existence of the instances/hosts data on cloud's database tables. Il 13/12/18 17:22