All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <chris.friesen@windriver.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: libvir-list@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] high outage times for qemu virtio network links during live migration, trying to debug
Date: Tue, 26 Jan 2016 14:31:25 -0600	[thread overview]
Message-ID: <56A7D79D.1020307@windriver.com> (raw)
In-Reply-To: <20160126164521.GK15172@redhat.com>

On 01/26/2016 10:45 AM, Daniel P. Berrange wrote:
> On Tue, Jan 26, 2016 at 10:41:12AM -0600, Chris Friesen wrote:

>> My question is, why doesn't qemu continue processing virtio packets while
>> the dirty page scanning and memory transfer over the network is proceeding?
>
> The qemuDomainMigratePrepareTunnel3Params() method is responsible for
> starting the QEMU process on the target host. This should not normally
> have any impact on host networking connectivity, since the CPUs on that
> target QEMU wouldn't be running at that point. Perhaps the mere act of
> starting QEMU and plugging the TAP dev into the network on the target
> host causes some issue though ? eg are you using a bridge that is doing
> STP or something like that.

Well, looks like your suspicions were correct.  Our fast-path backend was 
mistakenly sending out a GARP when the backend was initialized as part of 
creating the qemu process on the target host.  Oops.

Thanks for your help.

Chris

  reply	other threads:[~2016-01-26 20:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26 16:41 [Qemu-devel] high outage times for qemu virtio network links during live migration, trying to debug Chris Friesen
2016-01-26 16:45 ` Daniel P. Berrange
2016-01-26 20:31   ` Chris Friesen [this message]
2016-01-26 16:50 ` Paolo Bonzini
2016-01-26 17:21   ` Chris Friesen
2016-01-26 17:31     ` Paolo Bonzini
2016-01-26 17:49       ` Chris Friesen
2016-01-26 18:07         ` Paolo Bonzini

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=56A7D79D.1020307@windriver.com \
    --to=chris.friesen@windriver.com \
    --cc=berrange@redhat.com \
    --cc=libvir-list@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.