Re: Ubuntu 14.04 + qemu 2.5 vs. ACS 4.8 advice needed

Here is the error that we caught with Libvirt 1.3.1: 2017-07-21 11:46:27,501 WARN [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null) Plug Nic failed due to org.libvirt.LibvirtException: internal error: unable to execute QEMU command 'device_add': Hot-plugged device

Ubuntu 14.04 + qemu 2.5 vs. ACS 4.8 advice needed

Hi all, we are using ACS 4.8, on Ubuntu 14.04 (stock version qemu/libvirt - 2.0.0/1.2.2) and we have issues during live migration of "busy" VMs (high RAM change rate), so we plan to introduce additional flag+global parameter in ACS, which will auto converge flag libvirt to enable auto convergence

Re: Modifying a service offering in the cloudstack DB

Hi Daniel, Resource calculation will not be greatly affected by 4Mhz – you should be safe here. Keep in mind you are running with something like a 75% alert and 85% disable threshold on your clusters (see cluster settings / global settings) – and unless you increase the disable threshold to

Re: Modifying a service offering in the cloudstack DB

Hi, Daniel. You are completely right. Change your CPU Freq in DB is safe, an CPU overprovisioning will help you. 2017-07-21 14:57 GMT+07:00 : > Hi Dag, Hi Ivan, > > thanks to both of you for your reply. I would like to build on the > question of my colleague

Re: Modifying a service offering in the cloudstack DB

Hi Dag, Hi Ivan, thanks to both of you for your reply. I would like to build on the question of my colleague Christian. Can you elaborate what would happen if we’d just change the service offering in the database? From my understanding the main problem is, that during VM creation the old and

Re: Modifying a service offering in the cloudstack DB

Hi Christian – my twopence worth – for the sake of 4Mhz the DB change should be OK, it seems a bit overkill to create and replace all your service offerings just to accommodate your new 1995MHz hardware. Regards, Dag Sonstebo Cloud Architect ShapeBlue On 21/07/2017, 08:07, "Ivan Kudryavtsev"

Re: Modifying a service offering in the cloudstack DB

Hi. You just have to restart all affected VMs after offering change, because running VMs only get new resources after restart. It might be better to configure CPU overprovisioning in case you met system limits. 21 июл. 2017 г. 13:59 пользователь написал: >

Re: Modifying a service offering in the cloudstack DB

Hi Ivan, thanks für die quick reply. Would you mind elaborating somewhat further on the potential implications. Can I avoid unfaire resource provisioning by modifiying all existing service offerings equally, e.g. changing the CPU Speed of all offering from 1999 to 1995 MHz? Cheers,