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] incompatibility of netfront driver with bonding module

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] incompatibility of netfront driver with bonding module
From: "Masroor Vettuparambil" <Masroor.Vettuparambil@xxxxxxxxxxxx>
Date: Mon, 31 Mar 2008 11:40:35 -0400
Cc: Yosuke Iwamatsu <y-iwamatsu@xxxxxxxxxxxxx>
Delivery-date: Mon, 31 Mar 2008 08:41:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AciTRY+udV6J0lrcTou2qzReJmnC/Q==
Thread-topic: incompatibility of netfront driver with bonding module
Hi all,
 
I am trying a live migration of pass-through enabled domU. The idea is configuring a bonding interface and enslave the pass-through NIC to it. During migration, enslave a vif and detach the NIC. But this is not working because of the incompatibility of netfront driver with bonding module.
 
1. Normally, bonding will inherit the mac from the first slave and assign it to all the other slaves added later. So the mac of vif will be updated. But during migration, the mac of vif is getting updated from xenstore(/vm/). So how about having a set_mac_address entry in netfront that update the xenstore?
2. arp link monitoring method relies on the slave driver's rx/tx timestamp. But in netfront, dev->last_rx and dev->trans_start are not being used, and fails to detect the link status.
3. In mii link monitoring, it relies on the netif_carrier_ok status. But as netfront is using itsown netfront_carrier_* functions, the status is not getting updated to bonding module.
 
So I need help, especially on #1. Is it ok to update the xenstore /vm/ keys from domU? how to do this?
 
thanks,
Masroor
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] incompatibility of netfront driver with bonding module, Masroor Vettuparambil <=