similar to: bind & kickstart

hello there, I wonder if you could help me: I am trying to install 50 diskless servers using PXE / kickstart, it all starts well, DHCP server issues a dynamic address, tftp issues the kickstart file, the client starts reading the KS file but at some point anaconda brings up an unhandled exception related to Python when reading Comps.xml?? What is really unsettling is the fact that if I plug

I have successfully set up a very nice kickstart install with the i386 version of CentOS 4.3 and it works great. I am using a custom kickstart script and the kernel and initrd from disc1/images. But when I try to duplicate this for a 64 bit setup (changing paths in my tftp server, ks.cfg, etc to point to the 64 bit stuff) it successfully tftp's everything just as it should (tethereal

Hi, I am currently struggling with the right way to configure a bonding device via kickstart (via PXE). I am installing servers which have "eno" network interfaces. Instead of the expected bonding device with two active slaves (bonding mode is balance-alb), I get a bonding device with only one active slave and an independent, non-bonded network device. Also the bonding device

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/15 08:16 PM, Steven Tardy wrote: > >> On Feb 23, 2015, at 6:34 PM, Ashley M. Kirchner >> <ashley at pcraft.com> wrote: >> >> I have a Dell server that has two built-in ethernet devices. When >> I kickstart the machine, they are correctly identified as eth0 >> and eth1 (correctly meaning they

I was just wondering how (or indeed if) people use the %include directive in Kickstart configuration files when building systems via NFS. I've been trying to modularise our Kickstart files a little to make things more readable, having generic defaults and role specific stuff split out into separate configs. I've tried this configuration... [root at archive kickstart]# cat

I have a kickstart file that basically runs the following: install nfs --server=nfserver.blah.local --dir=/vol/updts/staging/CentOS_4.3 #include %some_file.cfg I want to be able to access or "include" a file on the nfs share not the local CDROM I've got this on. How do I do that? === Al

I have a line in my kickstart file (ksdevice) # Network information network --bootproto=dhcp --device=eth0 --onboot=on # Default network to boot ksdevice=eth0 # Auto reboot (to being next install faze) reboot However its still poping up and asking me eth0 or eth1 for install? Has this operation changed? Thanks, Jerry

This should be easy to answer (I hope).? We routinely kickstart boxes to use for managing our customers RADIUS/DHCP configurations (along with other things).? We've had a C7 kickstart in place since I built one in May and are finally starting to roll it out for new installations.? But, I'm curious as to what ksdevice= actually does. With the C6 we routinely used ksdevice=eth0 since we

Hi, I'm kickstarting a vm in ESXi 5.1. ks.cfg is on floppy, install media is ISO file. This works great as long as I don't add an additional repo, in our case it is vmware tools on one of our webservers. If I add the repo line, anaconda asks then for the used network card and indeed, switching to console the interfaces are still unconfigured. Chosing eth0 in gui continues the

Hi, In a corporate environment we are not allowed to use DHCP/PXE for doing network installations. This means we have to look for other solutions. Our solution is to use an ISO image (mounted via a KVM solution) to kick off the network installation. A big problem currently is that the order of the network interfaces is arbitrary (depends on the order of the drivers loaded) and is not

Starting back in RHEL/Cent 5 I found that the only way to make sure your interface enumeration was consistent after install with what you had during install was to create a udev rules file using the mac addresses as the key. It is easy to run a short script in postinstall to create it based on how anaconda has seen them. In order for this to work on Cent 6 you have to set biosdevname=0

<overly trimmed> On 02/25/2015 01:56 PM, Ashley M. Kirchner wrote: > Ok, so some of this now works, but I'm still having problems. With the > bootif option, the system now correctly configures and uses the same > interface to get its kickstart file. However, when the system is done and > boots up, the interfaces are still messed up. So this is what I have in the >

Hey, someone just told me yesterday that I can give my machine an initial IP address, gateway, dns server, and netmask via command line like this: linux ks=http://www.mydomain.com/kick.ks ip=192.168.1.5 netmask=255.255.255.0 gateway=192.168.1.1 dns=192.168.1.10 Is this true? Is the syntax wrong or right? If so, and I call my kick.ks file and it has install cdrom it'll pull the files

On 11/01/2017 03:25 PM, Chris Adams wrote: > Once upon a time, Mark Haney <mark.haney at neonova.net> said: >> Okay, so it looks like I can simply change ksdevice=eth0? to >> bootdev=eth0, correct? > I believe you can just leave both off (IIRC for CentOS 6 as well) if you > add "ipappend 2" to the pxelinux stanza. > I probably should have clarified that

Gordon Messmer wrote: > On 08/25/2016 11:35 PM, Phil Manuel wrote: >> The relevant kickstart section is:- >> >> part /boot/efi --fstype efi --grow --maxsize=200 --size=20 --ondisk=sda >> bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda1 >> autopart --type=lvm > > A couple of things to consider: > * The documentation for

Hi all, Someone played with kickstart bonding with centos 6.4 ? CentOS 6.4, as upstream now support ifcae bonding in kickstart network section. I've an issue with configuring a second bonding iface in kicstart on CentOS 6.4. The first bonding (bond0) works as espected but the second is not configured during installation. I've a 6 nic server (two for "puclic" network, two for

Over the last couple of weeks, additional software was installed using the package manager. I would like to get a custom kickstart file created for our system. For this, I would like to get complete list of software installed so they may be add to the kickstart file package selection. Can anyone tell me if this can be done? If it can, please give me instructions? Finally, where on

----- On 1 Nov, 2017, at 13:07, Chris Adams linux at cmadams.net wrote: | Once upon a time, Mark Haney <mark.haney at neonova.net> said: |> On 11/01/2017 03:25 PM, Chris Adams wrote: |> >Once upon a time, Mark Haney <mark.haney at neonova.net> said: |> >>Okay, so it looks like I can simply change ksdevice=eth0? to |> >>bootdev=eth0, correct? |> >I

I am getting the following error on boot on a new install Centos 51: #/bin/sh ro no such file or directory then a kernel panic I have traced it to the call ''switchroot'' in the init script in the initrd. the exact same build without zen has no problems. the boot messages look like: Attaching to iSCSI storage iscsistart: transport class version 2.0-724. iscsid version 2.0-865

Using a kickstart file that stops with a curses dialog "You have multiple network devices on this system. Which one do you want to install through?" The machine being configured with PXEboot has two ethernet interfaces. What's missing from the network entries below? I'd like this install to proceed without asking which ethernet interface. PXE begins the install with DHCP, so