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-users

Re: [Xen-users] xen hotplug scripts not working

To: Christian Placzek <clp@xxxxxxxxxxx>
Subject: Re: [Xen-users] xen hotplug scripts not working
From: Tim Post <tim.post@xxxxxxxxxxxxxxx>
Date: Fri, 16 Mar 2007 03:21:44 +0800
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 15 Mar 2007 12:21:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45F9993D.9000408@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Net Kinetics
References: <45F9993D.9000408@xxxxxxxxxxx>
Reply-to: tim.post@xxxxxxxxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 2007-03-15 at 20:06 +0100, Christian Placzek wrote:

> auto eth1
> allow-hotplug eth1
> iface eth1 inet static
>        address 10.1.1.201
>        netmask 255.255.255.0
>        network 1.1.1.0

Stop using network-bridge , its there to construct and deconstruct a
bridge so that Xen itself is non destructive (no changing of network
init needed to install it).

Since you are doing the more production-sensible thing by letting Debian
handle your bridges in init, there's no need to be using network-bridge.
Better, more structured and sensible control over all of that is partly
achieved by how you construct your guests.

First thing to do, get rid of network-bridge

In /etc/xen/scripts/ do 

echo -e "#!/bin/sh\nexit 0" > network-dummy && chmod +x network-dummy

Then in /etc/xen/ change xend-config.sxp to call network-dummy instead
of network-bridge.

Secondly (just suggesting) : 

Specify vifname= in the vif [] containers in the guests to keep it all
nice and neat. If you name the vif after the domname (or something else
specific and meaningful), bandwidth accounting becomes *very* easy over
an entire farm, which sounds like it would also lend well to your setup.

Best,
--Tim


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

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