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 3.1 networking questions

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Xen 3.1 networking questions
From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
Date: Thu, 15 Nov 2007 18:40:33 +0000
Delivery-date: Thu, 15 Nov 2007 10:39:28 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=+STmGmPoH+Tb2jk+T9ev2tzZhyEUISvvdcSSRbbd7Kk=; b=NjagmwXkFElp/WD0HaCGYG6jtyXQ5Z9Rn+3MqhR6bYmMXaVLnHLCdFRb3vkxiIhBnoCnHhnjnnAx9Cj1H8MPL/plgXI3v2y+3uNn840cxqCmqlaNPGr6HzFbkF506QBuVg9JI4xNz8HEmprneI7jmzKhVJt2UvmwzXE3DbWghoI=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=E8Gspy8P6dVJ3I5WBKKeXuoCwZ/PA2rOUC8BrwWnunv37WuJea33zHO7JzbWcNdU5dz49v+Ape5+RispfuTw5J9bPEH7//v5PlylaXSsNEqPlLHxGtBK3batc9SQv/qmnBgWkqfsQnkp9Ez5Jhmsflt5ASnBi10hpER9kMZfYRg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071115160131.GB12268@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <473BEFC3.3030901@xxxxxxxx> <473C1C4B.2080404@xxxxxxxx> <473C2CCE.1030303@xxxxxxxx> <473C3B3D.2060807@xxxxxxxxx> <473C539F.5070602@xxxxxxxx> <473C5B26.8040005@xxxxxxxxx> <20071115160131.GB12268@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.9 (Windows/20071031)
Jens Seidel wrote:
On Thu, Nov 15, 2007 at 02:43:50PM +0000, Nico Kadel-Garcia wrote:
Florian Engelmann wrote:
how to hardcode a vif interface?

Nico Kadel-Garcia schrieb:
Florian Engelmann wrote:
Ok at the moment I use NAT and i can connect to the internet, but I always have to change the router. Xen starts a new vifx.0 interface which is my domUs router. The IP changes every time. How to fix that???
Don't use "ip=", use "mac=" and either use DHCP or set the IP address in the operating systemm itself. You can also hardcode the vif instance, and I recommend this for network monitoring reasons.
It should be in your documentation. You use  something like:

   vif=[ 'vifname=xen.(whatever), mac=00:16:3E:01:(whichever), ' ]

I think I remember that I also needed the ip=10.0.1.1 argument. Not to
initialise the network in the domU (I do this via ifconfig, route) but
the get the IP address of the dom0 (=gateway) in the 10.x.x.x network.

Specifying ip=10.0.1.1 seems to ensures that dom0 gets the address
10.0.1.128 whereas it otherwise could get 10.0.2.128 or whatever and
makes it impossible to use a not dhcp setup with routing.

At least this is what I vague remember ...

Jens
This is definitely not the case. I recently built about 40 Xen guest domains with the MAC address and vifnames hardcoded, and all other network setttings done by the guest OS.

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