|
From: | Peter Lieven |
Subject: | Re: [Qemu-devel] Stalls on Live Migration of VMs with a lot of memory |
Date: | Wed, 04 Jan 2012 10:11:32 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15 |
On 04.01.2012 02:38, Shu Ming wrote:
maybe i should have been more precise. i use hugetblfs and memory pre allocation. so all 32G are allocated and most of them are dup. one problem seems to be an issue that has already been observed in 2010 but not addressed.On 2012-1-4 2:04, Peter Lieven wrote:Is the migration accomplished finally? How long will that be? I did a test on VM with 4G and it took me about two seconds.Hi all,is there any known issue when migrating VMs with a lot of (e.g. 32GB) of memory. It seems that there is some portion in the migration code which takes too much time when the numberof memory pages is large.Symptoms are: Irresponsive VNC connection, VM stalls and also irresponsive QEMU Monitor (via TCP).The problem seems to be worse on 10G connections between 2 Nodes (i already tried limiting thebandwidth with the migrate_set_speed command) than on 1G connections.
the rate limiter only counts bytes transferred. if there a lot of dup pages we end up reading almost the whole ram in one cycle. i already patched the source to exit the while loop in stage 2 if either the file rate limiter kicks in *or* there have
been more pages * PAGE_SIZE bytes read than the rate limit allows.this has improved the situation a bit, but it i have a few other ideas where time could be saved.
peter
The problem also seems to be worse in qemu-kvm-1.0 than in qemu-kvm-0.12.5.Any hints? Thanks, Peter
[Prev in Thread] | Current Thread | [Next in Thread] |