WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Live Migration and Bridge Settings

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Live Migration and Bridge Settings
From: Christopher Boumenot <boumenot@xxxxxxxxx>
Date: Tue, 15 Mar 2005 14:26:51 -0500
Delivery-date: Wed, 16 Mar 2005 07:48:45 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>