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

Re: [Xen-devel] Dom1 always does DHCP requests and vmid increasing

To: Mike Brady <mike.brady@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Dom1 always does DHCP requests and vmid increasing
From: Mike Wray <mike.wray@xxxxxxxxxx>
Date: Fri, 30 Jul 2004 09:14:39 +0100
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 30 Jul 2004 09:32:42 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <200407282117.18613.mike.brady@xxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <E1BpY85-0001ci-00@xxxxxxxxxxxxxxxxx> <200407282117.18613.mike.brady@xxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040421
Mike Brady wrote:

I don't have tcpdump installed at the moment, but will do so shortly.

In the mean time I have been playing around a bit and have found the following.

1) Putting an ip=192.168.42.36 on the config file stops the DHCP request, but the domain still has two addresses - the 192.168.42.36 and 192.168.42.35 (this is what is on the ifcfg-eth0 file).

2) In looking at the create.py script (after a crash course in Python :-) I noticed that the 1.2.3.4 address is actually assigned as the nfsserver address, not the IP address. To test this I set the nfs_server variable to '169.254.1.0' and now this address shows up in the DHCP server log. The log entry is below.

Jul 28 20:49:22 spitfire dhcpd: DHCPREQUEST for 255.255.255.255 (169.254.1.0) from aa:00:00:00:00:11 via eth0: wrong network. Jul 28 20:49:22 spitfire dhcpd: DHCPNAK on 255.255.255.255 to aa:00:00:00:00:11 via eth0
Jul 28 20:49:24 spitfire dhcpd: DHCPDISCOVER from aa:00:00:00:00:11 via eth0
Jul 28 20:49:25 spitfire dhcpd: DHCPOFFER on 192.168.42.96 to aa:00:00:00:00:11 via eth0 Jul 28 20:49:25 spitfire dhcpd: DHCPREQUEST for 192.168.42.96 (192.168.42.51) from aa:00:00:00:00:11 via eth0 Jul 28 20:49:25 spitfire dhcpd: DHCPACK on 192.168.42.96 to aa:00:00:00:00:11 via eth0

I am still looking at the xm code to try and understand it.


xm just assembles the components of the ip= parameter to the kernel.
If you use 'xm create -n' it will print out the resulting configuration
and you will be able to see the kernel ip parameter it will use.

The ip= param to the kernel has the format

ip=ipaddr:nfsserver:gateway:hostname:interface:dhcpmode

and xm defaults it to

ip=:1.2.3.4:::eth0:off

which has DHCP off. So it's a double puzzle, why does the kernel
use dhcp when it's set off, and why is it using dhcp for the
nfs server address anyway?

If the DHCP requests are a problem for you I could add a
parameter to xm create to tell it not to set the ip= param
at all.

Mike


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel