All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Wray <mike.wray@hpl.hp.com>
To: Mike Brady <mike.brady@devnull.net.nz>
Cc: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.sourceforge.net
Subject: Re: Dom1 always does DHCP requests and vmid increasing
Date: Fri, 30 Jul 2004 09:14:39 +0100	[thread overview]
Message-ID: <410A036F.6070606@hpl.hp.com> (raw)
In-Reply-To: <200407282117.18613.mike.brady@devnull.net.nz>

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

  reply	other threads:[~2004-07-30  8:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-27  9:50 Dom1 always does DHCP requests and vmid increasing Mike Brady
2004-07-27 10:17 ` Ian Pratt
2004-07-27 18:58   ` Mike Brady
2004-07-27 20:00     ` Ian Pratt
2004-07-28  8:27       ` Xen in a "new" distribution suggestion Rune Johan Andresen
2004-07-28  9:17       ` Dom1 always does DHCP requests and vmid increasing Mike Brady
2004-07-30  8:14         ` Mike Wray [this message]
2004-07-29  9:12       ` Mike Brady
2004-07-29 10:17         ` Ian Pratt
2004-07-27 11:14 ` Mark Williamson
2004-07-27 19:21 ` Barry Rountree

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=410A036F.6070606@hpl.hp.com \
    --to=mike.wray@hpl.hp.com \
    --cc=Ian.Pratt@cl.cam.ac.uk \
    --cc=mike.brady@devnull.net.nz \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.