> > Hi, > Currently I'm running cobbler-1.6.6 (from EPEL) on a set of servers and I utilize koan to build Xen VMs. I make use of --static-interface with koan to avoid having to run a DHCP server. Each VM has 2 interfaces defined in cobbler; one "public" and one "management". I've been building CentOS 5.3 VMs happily via the management network for several months now. After importing and configuring the VMs to be built from CentOS 5.4, I noticed that the build process wouldn't get passed the first stage anymore and errors out with, "There was an error configuring your network interface" on the console. Doing some digging, I realized that when using --static-interface, koan will pass a default gateway to the kernel arguments, regardless of what network the interface is on. The management network I build from is entirely private and has no default gateway. I'm assuming something changed in CentOS 5.4 that disallows kickstart builds if the network config is incorrect. I guess CentOS 5.3 was tolerant and chose to ignore this value, but CentOS 5.4 refuses to build.
> Here's what gets passed to libvirt when building: 10.10.1.0/24 is the management network 192.168.1.0/24 is the "public" network > <os> > <type>linux</type> > <kernel>/var/lib/xen/vmlinuz</kernel> > <initrd>/var/lib/xen/initrd.img</initrd> > <cmdline>ksdevice=eth1 lang= ip=10.10.1.11 ks= http://10.10.1.5/cblr/svc/op/ks/system/<http://10.10.1.5/cblr/svc/op/ks/system/hanytest>vm1 netmask=255.255.255.0 text kssendmac gateway=192.168.1.1 </cmdline> > </os> > Should koan be doing an extra check to determine if the gateway is on the same network as the interface, and if not, ignore it entirely? > Thanks in advanced for your help hany
_______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
