From: Peter Lieven <pl@kamp.de>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
qemu-stable@nongnu.org, yanghy@cn.fujitsu.com,
jasowang@redhat.com
Subject: Re: [Qemu-devel] [Qemu-stable] Broken live Migration in Qemu 2.5.1.1?
Date: Tue, 7 Jun 2016 09:11:18 +0200 [thread overview]
Message-ID: <57567396.4070205@kamp.de> (raw)
In-Reply-To: <A4DB3EB4-D244-48E8-95E3-51AF66241F4B@profihost.ag>
Am 06.06.2016 um 18:13 schrieb Stefan Priebe - Profihost AG:
> We're most probably seeing the same while migrating a machine running balanceng but haven't thought this might be a qemu bug. Instead we're investigating with balanceng people.
>
> Waiting for your further results.
This obviously is a regression. It was introduced between v2.4.0 and v2.5.0. I can clearly see RARPs being no longer emitted after this commit:
fefe2a78abde932e0f340b21bded2c86def1d242 is the first bad commit
commit fefe2a78abde932e0f340b21bded2c86def1d242
Author: Yang Hongyang <yanghy@cn.fujitsu.com>
Date: Wed Oct 7 11:52:16 2015 +0800
net: merge qemu_deliver_packet and qemu_deliver_packet_iov
qemu_deliver_packet_iov already have the compat delivery, we
can drop qemu_deliver_packet.
Signed-off-by: Yang Hongyang <yanghy@cn.fujitsu.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
I will analyze further.
Peter
next prev parent reply other threads:[~2016-06-07 7:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 13:32 [Qemu-devel] Broken live Migration in Qemu 2.5.1.1? Peter Lieven
2016-06-06 15:51 ` Peter Lieven
2016-06-06 16:13 ` [Qemu-devel] [Qemu-stable] " Stefan Priebe - Profihost AG
2016-06-07 7:11 ` Peter Lieven [this message]
2016-06-07 7:38 ` Peter Lieven
2016-06-07 8:33 ` Stefan Priebe - Profihost AG
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=57567396.4070205@kamp.de \
--to=pl@kamp.de \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=s.priebe@profihost.ag \
--cc=yanghy@cn.fujitsu.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).