From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Peter Lieven <pl@kamp.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-stable] Broken live Migration in Qemu 2.5.1.1?
Date: Tue, 7 Jun 2016 10:33:15 +0200 [thread overview]
Message-ID: <575686CB.5080401@profihost.ag> (raw)
In-Reply-To: <575679FE.50904@kamp.de>
Am 07.06.2016 um 09:38 schrieb Peter Lieven:
> 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.
>
> Can you try the patch
>
> net: fix qemu_announce_self not emitting packets
Thx - will wait for a new patch based on Paolo's comments - if that's ok.
Stefan
> I just send to the mailing list.
>
> Thanks,
> Peter
>
prev parent reply other threads:[~2016-06-07 8:33 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
2016-06-07 7:38 ` Peter Lieven
2016-06-07 8:33 ` Stefan Priebe - Profihost AG [this message]
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=575686CB.5080401@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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;
as well as URLs for NNTP newsgroup(s).