|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] incompatibility of netfront driver with bonding module
Masroor Vettuparambil wrote: It might be desirable, but I don't know for now if we can achieve it easily. I need to include the support for arp link monitoring to netfront. Is link monitoring really necessary?If you mean you use link monitoring to change the active slave of the bond0, I think we can do that using ifenslave command inside domU. #ifenslave bond0 eth1 -> enslave new netif(eth1) to bonding device #ifenslave -d bond0 eth0 -> release old netif(eth0) from bonding Regards, Yosuke Regards Masroor,-----Original Message-----From: Yosuke Iwamatsu [mailto:y-iwamatsu@xxxxxxxxxxxxx] Sent: Thursday, April 03, 2008 12:00 PMTo: Masroor Vettuparambil Cc: xen-devel@xxxxxxxxxxxxxxxxxxx Subject: incompatibility of netfront driver with bonding module Hi, Masroor Vettuparambil wrote: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?So I need help, especially on #1. Is it ok to update the xenstore /vm/keys from domU? how to do this? _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |