Re: Need to ask for help again (Migration in cloudstack)

Hi. Just, don't compare 1g vs 10g or even 40g infiniband network. It might look like linear bandwidth growth should lead to proportional time decrease, but migration can stuck forever with 1g and work seconds with 10g or 40g. But, Indeed, autoconvergence is a great feature. 2 окт. 2017 г. 20:32

Re: Need to ask for help again (Migration in cloudstack)

BTW, I went extreme and tested 24CPU/60GB busy VM migrate with dynamic auto-convergence (qemu2.5/libvirt1.3.1 and a nice patch to activate autoconverge flag inside ACS- thx to Mike Tutkowski !), where right after first migration cycle of 58G ram is finished (58GB RAM = Prime95 workload with all 24

Re: Need to ask for help again (Migration in cloudstack)

Hi Ivan, yes you are right, but it works like crap (from downtime perspective), because when we could not live migrate "normally" one 64GB client VM, we manually (instead of ACS doing it...) paused the VM via VIRSH, and then VM was in pauses state for 15min (yes it was only 1GBps management

Re: Need to ask for help again (Migration in cloudstack)

Hello! I want to say thanks to all! Nowadays I had no time to work on this, but I hope I will setup some test environment to try live migration + migration on non-shared. 2017-10-02 13:50 GMT+03:00 Ivan Kudryavtsev : > AFAIK ACS has VM suspend parameter in KVM agent

Re: Need to ask for help again (Migration in cloudstack)

AFAIK ACS has VM suspend parameter in KVM agent which acts when ACS is unable to migrate successfully. Also, I almost have no problem with 8core/16GB migration over 10G, but you are right. Sometimes it doesn't work as expected without autoconvergence and new Qemu/KVM does the work. 2017-10-02

Re: Need to ask for help again (Migration in cloudstack)

A bit late, and not directly related with original question - if you are doing any kind of KVM live migration (ACS or not), make sure you are using qemu 2.5 and libvirt 1.3+, to support dynamic auto-convergence (regular auto-convergence, almost useless, available from qemu 1.6+) - becase live

Re: Need to ask for help again (Migration in cloudstack)

Personal experience with KVM (not cloudstack related) and non-shared storage migration - works most of the time - but can be very slow - even with 10G backplane. On 9/5/17 6:27 AM, Marc-Aurèle Brothier wrote: > Hi Dimitriy, > > I wrote the PR for the live migration in cloudstack (PR 1709). We're

Re: Need to ask for help again (Migration in cloudstack)

Hi Dimitriy, I wrote the PR for the live migration in cloudstack (PR 1709). We're using an older version than upstream so it's hard for me to fix the integration tests errors. All I can tell you, is that you should first configure libvirt correctly for migration. You can play with it by manually

Re: Need to ask for help again (Migration in cloudstack)

Hello, That's what I want, thank you! I want to have Live migration on KVM with non-shared storages. As I understood, migration is performed by LibVirt. 2017-09-01 17:04 GMT+03:00 Simon Weller : > Dmitriy, > > Can you give us a bit more information about what you're

Re: Need to ask for help again (Migration in cloudstack)

Dmitriy, Can you give us a bit more information about what you're trying to do? If you're looking for live migration on non shared storage with KVM, there is an outstanding PR in the works to support that: https://github.com/apache/cloudstack/pull/1709 - Si

Re: Need to ask for help again (Migration in cloudstack)

You might start with this commit https://github.com/apache/cloudstack/commit/21ce3befc8ea9e1a6de449a21499a50ff141a183 and storage_motion_supported column in hypervisor_capabilities table. Thanks, ~ Rajani http://cloudplatform.accelerite.com/ On August 31, 2017 at 6:29 PM, Dmitriy Kaluzhniy

Need to ask for help again (Migration in cloudstack)

Hello! I contacted this mail before, but I wasn't subscribed to mailing list. The reason I'm contacting you - I need advise. During last week I was learning cloudstack code to find where is implemented logic of this statements I found in cloudstack documentation: "(KVM) The VM must not be using