On Jun 5, 2007, at 11:29, Michael DeHaan wrote:
What does your full /etc/dhcp.conf as generated by cobbler look
like? How about /var/lib/cobbler/settings?
dhcpd.conf looks reasonable, at least to me:
------
ddns-update-style interim;
allow booting;
allow bootp;
ignore client-updates;
set vendorclass = option vendor-class-identifier;
subnet 172.16.0.0 netmask 255.255.255.0 {
option routers 172.16.0.1;
option subnet-mask 255.255.255.0;
# range dynamic-bootp 172.16.0.101 172.16.0.110;
filename "/pxelinux.0";
default-lease-time 21600;
max-lease-time 43200;
next-server bread;
}
host label1 {
hardware ethernet BF:CC:AC:10:00:65;
fixed-address 172.16.0.101;
next-server bread;
}
------
The two changes I've made to cobbler/settings are manage_dhcp and
yum_core_mirror_from_server.
------
bootloaders:
ia64: /var/lib/cobbler/elilo-3.6-ia64.efi
standard: /usr/lib/syslinux/pxelinux.0
default_kickstart: /etc/cobbler/default.ks
dhcpd_bin: /usr/sbin/dhcpd
dhcpd_conf: /etc/dhcpd.conf
httpd_bin: /usr/sbin/httpd
kernel_options:
ksdevice: eth0
lang: ' '
text: ~
koan_path: ''
manage_dhcp: 1
minimize_syncs: 1
next_server: bread
server: bread
syslog_port: 25150
tftpboot: /tftpboot
tftpd_bin: /usr/sbin/in.tftpd
tftpd_conf: /etc/xinetd.d/tftp
webdir: /var/www/cobbler
xmlrpc_port: 25151
yum_core_mirror_from_server: 1
-----
Is there something I'm supposed to be doing to the stock xen
configuration to enable networking for cobbler?
I ask because even specifying an IP manually to anaconda didn't
get me anywhere. I also don't see something that looks like a
network device in the kernel messages of the domU, though I admit to
not knowing what to look for, or if it ought to be there under Xen.
Thanks,
-Bill
-----
Bill McGonigle, Owner Work: 603.667.4000
BFC Computing, LLC Home: 603.448.1668
bill@xxxxxxxxxxxxxxxx Cell: 603.252.2606
http://www.bfccomputing.com/ Page: 603.442.1833
Blog: http://blog.bfccomputing.com/
VCard: http://bfccomputing.com/vcard/bill.vcf
