All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Boumenot <boumenot@yahoo.com>
To: xen-devel@lists.sourceforge.net
Subject: Live Migration and Bridge Settings
Date: Tue, 15 Mar 2005 14:26:51 -0500	[thread overview]
Message-ID: <d17cri$tb6$1@sea.gmane.org> (raw)

Greetings,

I'm having a problem with live migration, and the default network 
settings used by Xen.  I was hoping someone could give me advise on what 
I'm doing wrong.

I currently have three Linux installations, two of the PCs are running 
SuSe 9.1/Xen 2.0.5 with the stock xenU and xen0.  The third PC is 
running coLinux (debian) on a WindowsXP machine that exports the Xen's 
test ttylinux distribution in a flat file.

For this setup I have both Xen hosts NFS mount a directory containing 
the image.  I start a ping process on one of the Xen hosts to monitor 
network connectivity.  I then live migrate the VM from one to host to 
the other.  The ping process will usually fail for approximatley 15-20 
seconds (sometimes upto ~50 seconds), and then eventually restart.  The 
VM migrates properly.

I've looked at several tcpdump traces to see if I could find the 
unsolicited arp being sent, but I don't.  In fact I see the Xen host 
with the ping process re-issue the arp to find the IP address, and then 
the pings succeed.  I added some debug code to the netfront driver to 
verify that the arp is in fact being queued, and everything looks fine.

I started to suspect that something is wrong with my bridge setup.  I 
started out using the default Xen vif-bridge scripts, but I found that 
the VM only had connectivity to dom0.  The VM wasn't able to ping other 
hosts on the subnet.  From my googling, I discovered that people had 
similar problems, and based on their success I changed my init scripts. 
  Instead of Xen creating the bridge, I create my own, and label it 
eth0.  I do this before the init scripts configure eth0.

/sbin/ip link set name hw-eth0 dev eth0
/sbin/brctl addbr eth0
/sbin/brctl addif eth0 hw-eth0
/sbin/ip link set up hw-eth0

This works well for me.

I've also tried the routing setup, but I still had problems reaching 
other hosts from the VM.

While I'm able to migrate domains, I am unable to match the times I had 
read in the literature (<1 second).  Any ideas on where I went wrong, or 
areas that I should be looking at?


Thanks,
Christopher



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

             reply	other threads:[~2005-03-15 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-15 19:26 Christopher Boumenot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-16  8:11 Live Migration and Bridge Settings Ian Pratt
2005-03-16 14:10 ` Christopher Boumenot

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='d17cri$tb6$1@sea.gmane.org' \
    --to=boumenot@yahoo.com \
    --cc=xen-devel@lists.sourceforge.net \
    /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.