From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Lieven <pl@dlh.net>
Cc: Shu Ming <shuming@linux.vnet.ibm.com>,
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 15:14:40 +0100 [thread overview]
Message-ID: <4F045ED0.1030309@redhat.com> (raw)
In-Reply-To: <4F044F42.2050508@dlh.net>
On 01/04/2012 02:08 PM, Peter Lieven wrote:
>
> thus my only option at the moment is to limit the runtime of the while
> loop in stage 2 or
> are there any post 1.0 patches in git that might already help?
No; even though (as I said) people are aware of the problems and do plan
to fix them, don't hold your breath. :(
Paolo
next prev parent reply other threads:[~2012-01-04 14:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 18:04 [Qemu-devel] Stalls on Live Migration of VMs with a lot of memory Peter Lieven
2012-01-04 1:38 ` Shu Ming
2012-01-04 9:11 ` 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 ` Paolo Bonzini [this message]
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=4F045ED0.1030309@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pl@dlh.net \
--cc=qemu-devel@nongnu.org \
--cc=shuming@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).