From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Lieven <lieven-lists@dlhnet.de>
Cc: Zhang Haoyu <ahzhanghaoyu@gmail.com>,
Bug 1100843 <1100843@bugs.launchpad.net>,
gleb@redhat.com, eblake@redhat.com, quintela@redhat.com,
afaerber@suse.de, xiaoguangrong@linux.vnet.ibm.com,
mtosatti@redhat.com, kvm@vger.kernel.org, mst@redhat.com,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Bug 1100843] Re: Live Migration Causes Performance Issues
Date: Mon, 07 Oct 2013 11:37:11 +0200 [thread overview]
Message-ID: <525280C7.2050402@redhat.com> (raw)
In-Reply-To: <525256FC.6060608@dlhnet.de>
Il 07/10/2013 08:38, Peter Lieven ha scritto:
> On 06.10.2013 15:57, Zhang Haoyu wrote:
>>> >From my testing this has been fixed in the saucy version (1.5.0) of
>> qemu. It is fixed by this patch:
>>> f1c72795af573b24a7da5eb52375c9aba8a37972
>>>
>>> However later in the history this commit was reverted, and again broke
>> this. The other commit that fixes this is:
>>> 211ea74022f51164a7729030b28eec90b6c99a08
>>>
>> See below post,please.
>> https://lists.gnu.org/archive/html/qemu-devel/2013-08/msg05062.html
>
> I would still like to fix qemu to not load roms etc. if we set up a
> migration target. In this case
> we could drop the madvise, skip the checking for zero pages and also
> could avoid sending
> zero pages at all. It would be the cleanest solution.
It's in general not easy to do this if you take non-x86 targets into
account.
Paolo
next prev parent reply other threads:[~2013-10-07 9:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130117163740.7157.55600.malonedeb@gac.canonical.com>
[not found] ` <20130926203354.30826.10562.malone@soybean.canonical.com>
2013-10-06 13:57 ` [Qemu-devel] [Bug 1100843] Re: Live Migration Causes Performance Issues Zhang Haoyu
2013-10-07 6:38 ` Peter Lieven
2013-10-07 9:37 ` Paolo Bonzini [this message]
2013-10-07 9:49 ` [Qemu-devel] " Peter Lieven
2013-10-07 9:55 ` Paolo Bonzini
2013-10-10 8:17 ` 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=525280C7.2050402@redhat.com \
--to=pbonzini@redhat.com \
--cc=1100843@bugs.launchpad.net \
--cc=afaerber@suse.de \
--cc=ahzhanghaoyu@gmail.com \
--cc=eblake@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lieven-lists@dlhnet.de \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=xiaoguangrong@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).