From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Knorr Subject: Re: help with bugs Date: Fri, 5 Aug 2005 15:20:02 +0200 Message-ID: <20050805132002.GA15968@bytesex> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > I'd be inclined to rename the physical interface to pethN, and create > veth0 as eth0. I think this should solve the DHCP issue. Hmm, just an idea, not sure how well that would work in practice, maybe the network script should not even attempt to copy the ip addresses, but instead use ifup and ifdown, i.e. something like this: ifdown eth0 ip link set eth0 name peth0 ip link set veth0 name eth0 brctl addbr xen-br0 brctl addif xen-br0 peth0 brctl addif xen-br0 vif0.0 ip link set peth0 up ip link set vif0.0 up ip link set xen-br0 up ifup eth0 At least suse, fedora and debian have ifup and ifdown to control interfaces, not sure about others ... > So you don't use veth0? No. Partly because it's not entriely clear to me how the setup should look like (hope I got it right above), partly because the same setup works for both xen2 and xen3 then. And, no, I don't run services for the domUs on dom0 ... Gerd -- panic("it works"); /* avoid being flooded with debug messages */