1999 The Central Ohio Linux User Group. // All rights reserved. // Released under the GPL, v. 2. See: LICENSE.TXT // This file: template/header.php // // // echo "\n"; print ""; echo "\n"; echo ""; echo ""; echo "Rossberry.com - The Home of the Mobile Linux Lab"; if ($title != "") { echo " -- $title"; } echo "\n"; // The next line lets us link the header page below // the top ditrectory, and have the buttons work // RPH -- 011124 echo ""; // // scheme://user:pass@host:port/path?query#fragment // //$REQUEST_URI = $_SERVER[REQUEST_URI]; $url=parse_url("$REQUEST_URI"); $svr=$url[host]; //$svr="www.rossberry.net"; $svr="www.rossberry.com"; $server = $server_name ; print ""; ?>


Home of the Mobile Linux Lab

Home Overview Philosophy Infrastructure
Version Control Blogs Files cfengine

DHCPD setup

As discussed on the Infrastructure page I prefer to run my dhcp server on one of the vm's. It makes sense to run it with the build server so that all the OS configuration services for the vm's are in the same place.


yum -y install dhcp

Since this is a permanent vm that provides services to other vm's, it should have static ip's on both the standard xen interface and on the hostonly interface that you added. If you followed my examples on the dom0 setup page for editing your network.xml files, your default xen interface (hopefully eth0) is Edit /etc/sysconfig/network-scripts/ifcfg-eth0 and make this vm Likewise make eth1 service network restart to reset everything up nicely, then verify the interface ip's. You should be able to ping the .1 addresses on both nics. If your dom0 is on an active network, you should be able to ping addresses on that network as well as long as eth0 is active. If eth0 is down, then you should not be able to see the larger network.

Grab dhcpd.conf, dhcpd.hostonly.conf, dhcpd.nat.conf, and drop them in /etc on buildhost. If you used different ip's, then you will need to adjust the conf files appropriately. service dhcpd restart should come back cleanly. If there are errors, you will have to check /var/log/messages. Unfortunately, dhcpd server is very verbose and just tailing /var/log/messages will not get you the information you need. It is about 30 lines from the end of the file. Once you have it working, setup dhcp to start on boot.

If you look at dhcpd.hostonly.conf or dhcpd.nat.conf you will see that the hardware addresses are sequential. This is to enable the dhcpd server to work in conjunction with the clone_vm.sh script to produce vm's at predictable addresses.

1999 The Central Ohio Linux User Group. // All rights reserved. // Released under the GPL, v. 2. See: LICENSE.TXT // This file: template/footer.php // print "

"; // print " \n \n \n "; // $url=parse_url("$REQUEST_URI"); $scheme = $url[scheme]; $host = $url[host]; $whereami = $url[path]; $basename = exec("basename $whereami"); $REFERRER=exec("basename $whereami .php"); $SMURF = exec(" ls | grep $REFERRER | grep txt "); if ($SMURF != "") { ## echo ""; ## This next line of code opens the displayed code in a new window when uncommented echo ""; echo "\"View of "; echo ""; echo "$basename"; } else { print "\n"; print "\n"; } // print " Contact mll@rossberry.com Copyright\n © 2010, 2011 Jim Wildman.\n "; print "
All rights reserved.
"; ?>