Just Enough Developed Infrastructure

Cobbler on Centos with Vmware

Cobbler is an install server; batteries are included
Cobbler is a Linux installation server that allows for rapid setup of network installation environments.
With a simple series of commands, network installs can be configured for PXE, reinstallations, media-based net-installs, and virtualized installs (supporting Xen, qemu, KVM, and VMware Server). Cobbler uses a helper program called 'koan' (which interacts with Cobbler) for reinstallation and virtualization support.
This post describes how we use cobbler to setup an automated provisioning of systems for our test lab.
Cobbler's documentation is very extensive, and you can read more at https://fedorahosted.org/cobbler/wiki/
Our lab setup:

  • cobbler running on the box that hosts the virtual machines (this could a virtual machine also)
    • host ip =
  • vmware network (NAT = vmnet8) ,
  • gateway configure in vmware = (vmnet8.conf)
Step 1: Installation (using RPM's)
For more detail see: https://fedorahosted.org/cobbler/wiki/DownloadInstructions
There is a clear relation of cobbler with Fedora, therefore using Centos as a distribution is a good fit. Centos is not the only distribution it works on , but it seems to be simplest way to set things up.
The easiest way to have cobbler installed is to add the EPEL repository. More detail on this at http://rgritsulyak.blogspot.com/2008/09/adding-epel-repository-for-centos-5.html.
Be sure to set the correct architecture for the repository i386 or x86_64
cat <<EOF >> /etc/yum.repos.d/EPEL.repo
 name=Epel from fedora
Now that we have the repository setup, we can easily install cobbler and it's companion services (dhcpd, bind, tftp, http)
# yum install redhat-rpm-config
# yum install dhcpd bind tftp-server httpd
# yum install cobbler
Installed: cobbler.noarch 0:1.4.1-1.el5 Dependency Installed: apr.x86_64 0:1.2.7-11 apr-util.x86_64 0:1.2.7-7.el5 createrepo.noarch 0:0.4.11-3.el5 httpd.x86_64 0:2.2.3-11.el5_2.centos.4 mkisofs.x86_64 9:2.01-10 mod_python.x86_64 0:3.2.8-3.1 postgresql-libs.x86_64 0:8.1.11-1.el5_1.1 python-cheetah.x86_64 0:2.0.1-1.el5 python-devel.x86_64 0:2.4.3-21.el5 tftp-server.x86_64 0:0.42-3.1.el5.centos xinetd.x86_64 2:2.3.14-10.el5 Complete!
Directories that are important are:
  • /var/www/cobbler: where is will host the files it will serve to it's clients by http
  • /var/lib/cobbler
  • /usr/lib/python2.4./site-packages/cobbler
  • /usr/share/cobbler
  • /usr/share/doc/cobbler-1.4.1/
  • /etc/cobbler/
  • /usr/bin/ for the cobbler
  • /etc/init.d/cobblerd
Step 2: First check and fixes of your environment
Cobbler provides a nice script that checks if your environment is correctly configured for using cobbler
[root@myserver ~]# cobbler check
The following potential problems were detected:
#0: The 'server' field in /etc/cobbler/settings must be set to something other than localhost, or kickstarting features will not work.  This should be a resolvable hostname or IP for the boot server as reachable by all machines that will use it.
We will set the server IP to the IP address of the vmnet8 interface =
#1: For PXE to be functional, the 'next_server' field in /etc/cobbler/settings must be set to something other than, and should match the IP of the boot server on the PXE network.
In our case this is the same IP address as the cobbler server = vmnet8 interface =
#2: Must enable selinux boolean to enable Apache and web services components, run: setsebool -P httpd_can_network_connect true
Nice to see that it has good instructions for selinux
#3: you need to set some SELinux content rules to ensure cobbler works correctly in your SELinux environment, run the following: /usr/sbin/semanage fcontext -a -t public_content_t "/var/lib/tftpboot/." && /usr/sbin/semanage fcontext -a -t public_content_t "/var/www/cobbler/images/."
Detailed command to enable http server to reed content from /var/www/cobbler and have tfpboot find its files
#4: service cobblerd is not running
Obviously this isn't running because we did not start it yet
#5: change 'disable' to 'no' in /etc/xinetd.d/tftp
By default tftp is disabled as it not a secure protocol and is know for it's security bugs. This disable to no will have it start. But we can further secure this by having it listen only to the vmnet8 interface by changing the /etc/xinetd.d/tftp
only_from = bind =
[root@myserver]# netstat -anp |grep 69 udp 0 0 6299/xinetd
#6: service httpd is not running
Obviously this isn't running because we did not start it yet
#7: since iptables may be running, ensure 69 (dhcp), 80(http), 25150(cobbler api), and 25151(cobbler api R/W) are unblocked
iptables -I RH-Firewall-1-INPUT -i vmnet8 -m udp -p udp --dport 69 -j ACCEPT
iptables -I RH-Firewall-1-INPUT -i vmnet8 -m tcp -p tcp --dport 80 -j ACCEPT
iptables -I RH-Firewall-1-INPUT -i vmnet8 -m tcp -p tcp --dport 53 -j ACCEPT
iptables -I RH-Firewall-1-INPUT -i vmnet8 -m tcp -p tcp --dport 25150 -j ACCEPT
iptables -I RH-Firewall-1-INPUT -i vmnet8 -m tcp -p udp --dport 25151 -j ACCEPT
Don't forget to save these rules so that the next time they are still available
#8: reposync is not installed, need for cobbler reposync, install/upgrade yum-utils?
Easy to solve with: yum install yum-utils
#9: yumdownloader is not installed, needed for cobbler repo add with --rpm-list parameter, install/upgrade yum-utils?
Is solved by doing #8
#10: fencing tools were not found, and are required to use the (optional) power management features. install cman to use them
If you need these : yum install cman
Step 3: Configuring the webinterface
Again good documentation can be found at https://fedorahosted.org/cobbler/wiki/CobblerWebInterface
By default the webinterface denies all access, this can be changed by changing the setting in /etc/cobbler/modules.conf
[authentication] #module = authn_denyall module = authn_configfile
[authorization] module = authz_allowall
The default password can be changed
# htdigest /etc/cobbler/users.digest "cobbler" $username
/sbin/service cobblerd restart
/sbin/service httpd restart
Now let's make apache and cobbler start after reboot!
# chkconfig httpd on ; chkconfig cobbler on
When cobbler was installed it installed to config files in your apache /etc/httpd/conf.d:
[root@myserver conf.d]# ls /etc/httpd/conf.d/cobbler
/etc/httpd/conf.d/cobbler.conf  /etc/httpd/conf.d/cobbler_svc.conf
If you want to have cobbler only active on the virtual (internal) interface, you need to put the whole config in a virtual host to listen on the internal address only
  • in your /etc/httpd/conf/httpd.conf:
    • NameVirtualHost
  • open the file /etc/httpd/conf.d/cobbler.conf and wrap it with
    • <VirtualHost>
    • Servername cobbler
    • ...
    • </VirtualHost>
  • put cobbler in your /etc/hosts to be resolved to
Ok, let's start for the first time
# /etc/init.d/httpd start & /etc/init.d/bind start & /etc/init.d/xinetd.d start
Now you can access it with
# lynx http://cobbler/cobbler/web
Step 4: Configuring DHCP to place nice with cobbler
Cobbler can manage your dhcp, so that when you define a system in cobbler, it automatically manages your dhcpd.conf
By default vmware on the vmnet8 has also a dhcpd running vmnet-dhcpd. So before having it work, we have to disable the internal dhcp of vmware on the vmnet8 interface.
Note: this is a hack, and when you have to do a vmware-config.pl , chances are that the change is gone!
More details can be found here http://mijnhome.be/blog/blog1.php/2008/11/06/vmware-server-2-disable-dhcp-on-vnet
Don't forget to top vmware first (/etc/init.d/vmware sto)!!!!!! I know this means bringing down all virtual machines first. But otherwise it will require to re-run vmware-config.pl !!!!
# vi /etc/vmware/locations
find and replace all occurences of VMNET8 DHCP = no
Another option might be to edit /usr/lib/vmware/net-services.sh, but I haven't explored this further.
So now that the vmware dhcpd is out of the way, let's configure the dhcpd we installed to listen on our vmnet8 interface:
Edit /etc/sysconfig/dhcpd
# Command line options here
Next you need to enable dhcpd support in cobbler. Edit the /etc/cobbler/cobbler.conf
manage_dns: 1
module = manage_isc
manage_dhcp: 1
And finally edit the /etc/cobbler/dhcp.template to reflect the skeleton you need.
subnet netmask {
 option routers   ;
 option domain-name-servers;
 option subnet-mask;
 range dynamic-bootp;
 filename                   "/pxelinux.0";
 default-lease-time         21600;
 max-lease-time             43200;
 next-server                $next_server;
More details https://fedorahosted.org/cobbler/wiki/ManageDhcp
Note: the router is and not , this is the default behaviour in vmware for a NAT interface , check /etc/vmare/vmnet8/nat/nat.conf
# Linux NAT configuration file
# NAT gateway address
ip =
netmask =
# or ip =
Step 5: Configuring DNS to play nice with cobbler
Similar to the DHCP we need to prepare some things for the DNS too.
First we need to active the DNS support in cobbler (i mean that cobbler can manage your DNS)
edit /etc/cobbler/cobbler.conf
module = manage_bind
manage_dns: 1
Then we specify the domainname and ip ranges we want cobbler to manage (also in /etc/cobbler/cobbler.conf)
manage_forward_zones: [ mydomaintest.com ]
 manage_reverse_zones: [ 192.168.0 ]
Because cobbler overwrites the bind config everytime we do a cobbler sync, we need to edit the template file to reflect our settings
options {
 listen-on port 53 {;  };
 directory       "/var/named";
 dump-file       "/var/named/data/cache_dump.db";
 statistics-file "/var/named/data/named_stats.txt";
 memstatistics-file "/var/named/data/named_mem_stats.txt";
 allow-query     { localhost; };
 recursion yes;
 forwarders { <your dns server here>; };
More details on https://fedorahosted.org/cobbler/wiki/ManageDns
Step 6: Using cobbler
This is the part you have been waiting for I guess ;-) Cobbler has the following: where you start from a distribution, repositories, profiles and systems (and images)
Add a distribution
The easiest way is to download the latest ISO DVD and mount it locally:
# mount -o loop /data/mount/iso/CentOS-5.2-x86_64-bin-DVD.iso /mnt
# cobbler import /mnt --arch=x86_64 --name=centos5.2-x86_64
# cobbler list
distro centos5.2-x86_64
profile centos5.2-x86_64
profile rescue-centos5.2-x86_64
distro centos5.2-xen-x86_64
profile centos5.2-xen-x86_64
You can see that the import actually imported both xen, the regular distro and the rescue .
Add a repository/repositories
Next we add two additional repositories: the first to get the updates and the second one to get the EPEL repository included. In case versions overlap, we define priorities.
# cobbler repo add --name=centos5.2-x86_64-updates --priority=70 --mirror=http://ftp.belnet.be/packages/centos/5.2/updates/x86_64
# cobbler repo add --name=EPEL-x86_64 --priority=40 --mirror=http://fr2.rpmfind.net/linux/epel/5/x86_64/
Now we can ask cobbler to download the repositories
# cobbler reposync
# cobbler reposync --name=EPEL-x86_64 (if you wanted only one to sync)
NOTE 1: we experienced too many open files, when doing an import of another repository - https://bugzilla.redhat.com/show_bug.cgi?id=468282
_do_grab IOError: [Errno 24] Too many open files:
cobbler reposync failed
ulimit -n 8192
NOTE 2: if your download hangs, and you have interrupted download, chances are that you have a corruption. Remove the latest rpm that got downloaded in f.i. in /var/www/cobbler/repo_mirror/EPEL-x86_64
[root@server cobbler]# cobbler list --what=repos
repo EPEL-x86_64
repo centos5.2-x86_64-updates
Add a profile
Next we setup a profile based on a combination of the distro and the repositories
# cobbler profile add --distro=centos5.2-x86_64 --name=centos5.2-x86_64-uptodate --repos="EPEL-x86_64 centos5.2-x86_64-updates"
NOTE 3: when specifying multiple repositories, install can sometimes hang in checking dependencies during the system install. Be sure to give your virtual machine enough memory to parse the list of of packages. Otherwise it will hang erractically during "checking dependencies". 384 MB is not a lot for a virtual machine for parsing multiple repo lists ...
Preparing a kickstart file
Kickstart is a redhat way of describing an automated installation of a machine. A sample can be found at /var/lib/cobbler/kickstart/sample.ks
More detail can be found at: There is also a tool called system-config-kickstart (requires X)
In a kickstart you can change ntpservers, timezone, keyboard layout
Add a system
We fill in the ip (we want it fixed), the mac address to respond to this profile and other configuration options
# cobbler system add --name pxe-test --ip= --mac=00:0C:29:2B:50:5C --profile=centos5.2-x86_update --kickstart=/var/lib/cobbler/kickstart/sample.ks --static=1
# cobbler system edit --name=pxe-test  --dns-name=pxe-test.mydomaintest.com --hostname=pxe-test.mydomaintest.com
# cobbler system edit --name=pxe-test  --gateway= --subnet=
After adding the system run
# cobbler sync
And it will automagically update dhcp, dns, http cobbler
So your actual kickstart with all the variables filled in , you can check it with
# lynx
Step 7: PXE booting
Now you are ready to start your virtual machine to do a boot. Hope everything works out now!
Further topics: