cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrija Panic (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-6203) KVM live migration improvement
Date Thu, 22 Jun 2017 22:07:00 GMT


Andrija Panic commented on CLOUDSTACK-6203:

Marcus, or someone, can you please provide example of sane values, for heavy DB server ?
We applied this tunables on 4.5 and 4.8, and after it regular VMs (not IO busy) migration
failed completely, and VMs end up in stopped state...

I used 10000 (10sec) for vm.migrate.downtime, and set 1 for vm.migrate.pauseafter.


> KVM live migration improvement
> ------------------------------
>                 Key: CLOUDSTACK-6203
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>            Reporter: Marcus Sorensen
>            Assignee: Marcus Sorensen
>             Fix For: 4.4.0
> Run the KVM live migration in a thread so we can monitor it. This will allow us to see
how long migrations are taking and do things like pause the vm if migration is stalling (per
user defined time limit) to quickly complete migration, or set the domain's max downtime during
cut-over between machines (higher values make migration of busy vms easier, lower values may
make migration stall).  In the future we can add the autoconvergence flag that stalls VMs
for a few ticks to allow memory copy to catch up, but it will be awhile before libvirt that's
shipped in a distro supports it, so these tunables may be useful now.

This message was sent by Atlassian JIRA

View raw message