From: Shu Ming <shuming@linux.vnet.ibm.com>
To: Peter Lieven <pl@dlh.net>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Stalls on Live Migration of VMs with a lot of memory
Date: Wed, 04 Jan 2012 09:38:32 +0800 [thread overview]
Message-ID: <4F03AD98.7020700@linux.vnet.ibm.com> (raw)
In-Reply-To: <032f49425e7284e9f050064cd30855bb@mail.dlh.net>
On 2012-1-4 2:04, Peter Lieven wrote:
> 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 number
> of 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 the
> bandwidth with the migrate_set_speed command) than on 1G connections.
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.
>
> The problem also seems to be worse in qemu-kvm-1.0 than in
> qemu-kvm-0.12.5.
>
> Any hints?
>
> Thanks,
> Peter
>
>
--
Shu Ming<shuming@linux.vnet.ibm.com>
IBM China Systems and Technology Laboratory
next prev parent reply other threads:[~2012-01-04 1:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 18:04 Stalls on Live Migration of VMs with a lot of memory Peter Lieven
2012-01-04 1:38 ` Shu Ming [this message]
2012-01-04 9:11 ` [Qemu-devel] " Peter Lieven
2012-01-04 10:53 ` Peter Lieven
2012-01-04 11:05 ` Paolo Bonzini
2012-01-04 11:22 ` Peter Lieven
2012-01-04 11:28 ` Paolo Bonzini
2012-01-04 11:42 ` Peter Lieven
2012-01-04 12:28 ` Paolo Bonzini
2012-01-04 13:08 ` Peter Lieven
2012-01-04 14:14 ` [Qemu-devel] " Paolo Bonzini
2012-01-04 14:17 ` Peter Lieven
2012-01-04 14:21 ` Peter Lieven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F03AD98.7020700@linux.vnet.ibm.com \
--to=shuming@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=pl@dlh.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox