All of lore.kernel.org
 help / color / mirror / Atom feed
From: Virajith Jalaparti <virajith.j@gmail.com>
To: Xen User-List <xen-users@lists.xensource.com>,
	xen-devel@lists.xensource.com
Subject: Live migration-delay in gratuitous arp
Date: Tue, 11 Jan 2011 20:51:23 -0600	[thread overview]
Message-ID: <4D2D172B.1060800@gmail.com> (raw)

Hi,

I was trying to perform live migration with a VM on a LAN and measure 
the downtime seen by an application (e.g. ping), the time for which the 
application cannot communicate with the VM. The application is run on a 
machine different from those between which the VM is migrated. I noticed 
that the VM remains unreachable for nearly 1-1.5sec. However the 
xend.log file says that the time (the delta) for the last round of the 
migration is around 100msec. So, the VM is actually paused for just 
around 100msec but the application cannot reach it for 1-1.5sec. I 
believe this is because of the delay in the gratuitous ARP being sent. 
Is the implementation such that the ARP is not sent immediately after 
the migration is finished? Is there an easy tweak (without modifying 
source code) by which I can correct this or do I have to modify the 
source code?

I am using Xen from the repos of CentOS 5.5 on a 64bit machine.

Thanks,
Virajith

                 reply	other threads:[~2011-01-12  2:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4D2D172B.1060800@gmail.com \
    --to=virajith.j@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@lists.xensource.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 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.