similar to: kickstart x86_64 with i386 compatibilites

Hi, I?m trying kickstart on CentOS Below is my ks.cfg *[root at localhost ~]# cat /root/ks.cfg* * * #Generated by Kickstart Configurator #platform=x86, AMD64, or Intel EM64T #System language lang en_US #Language modules to install langsupport en_US #System keyboard keyboard us #System mouse mouse #Sytem timezone timezone Asia/Dili #Root password rootpw --iscrypted

This is what I have for configuring software raid on sata drives in my kickstart config <snip kickstart.cfg> clearpart --initlabel --all part swap --size=2048 --ondisk=sdb part swap --size=2048 --ondisk=sda part raid.01 --size=101 --ondisk=sda part raid.02 --size=101 --ondisk=sdb part raid.04 --size=1 --grow --ondisk=sdb part raid.03 --size=1 --grow --ondisk=sda raid / --fstype ext3

For some reason I cannot kickstart via pxe after installing a new SMC 48Port GigE switch. I swapped out an old hub to test and kickstarting still works with the old hub. Does anyone have any suggestions, --

I am trying to a install Centos 5.1 32-bit Xen HVM DomU onto a Centos 5.1 64bit DomU with the default xen installed and the kickstart hangs at random points during the install process. Sometimes retrieving the image, sometimes formatting the filesystem, sometimes installing the packages,etc. I tried upgrading to xen 3.2 and encounter the same problem before rebuilding back to stock Centos 5.1

Dear Friends, I have centos 6.2 64 bit os in my dell server. When I try to install centos or scientific linux using NFS so it is not working and getting me error = "unable to download kickstart file". My kickstart file configuration is : #platform=x86, AMD64, or Intel EM64T #version=DEVEL # Firewall configuration firewall --disabled # Install OS instead of upgrade install # Use NFS

I have a new ESXi server (5.x), and trying to load some VM guests on there. I have the guests configured, but when I try and boot from ISO image, the graphics are so bad it is futile. No worries I normally use kickstart anyways. Because the ESXi (on the same network as my physical servers) cannot talk to the PXE server. But works fine on the network (I can ssh/scp in and out of the ESXi

Hi, I have alot of kickstart and scripting going on as I provision lots of machines, and every now and then I run into a pesky machine or three that's still got that Adeptec zero-channel RAID card sitting on the board. Normally I like to rip it our and throw something more robust in, but if it's a cache machine or whatever, I leave it in. It makes my kickstart file useless until I

Patrick Lists wrote: >>> I fail to see how your repository problem is related to my Kickstart PXE/NFS >>> problem. We can install CentOS 6 (no Kickstart) without problems using PXE. >>> It's the NFS-mounting of the Kickstart-file which fails. What I'd love to learn >>> is how others have made NFS/Kickstart work... >> >> Is CentOS 6 assuming

We have CentOS 6 manual installation working by PXE booting from a RHEL5.6 PXE/TFTP server. However, when we add a Kickstart file in the PXE configuration: kernel CentOS-6-i386/vmlinuz append load_ramdisk=1 initrd=CentOS-6-i386/initrd.img network ks=nfs:130.226.86.4:/u/rpm/kickstart/ks-centos-6-clean-i386.cfg then the CentOS 6 client install reports "Unable to download the

I am trying to use kickstart for automated builds from a DVD. Some of the machines have DVD's drives and some have CDRom drives only. With the CDRom only machines I would like to plug in an external DVD drive via USB and use this to kickstart. The DVD only machines work correctly with a isolinux.cfg as label test kernel vmlinuz append initrd=initrd.img ramdisk_size=8192

On 02/03/2015 11:19 AM, Jay Leafey wrote: > The documentation says that you can just put "vnc" (or > "vncconnect={host}") in the kickstart file in the command section and > proceed from there. Here's a link to an article in Red Hat Magazine > that has a pretty good overview: > >> http://www.redhat.com/magazine/024oct06/features/kickstart/ > > As

Both BaseOS and AppStream are needed. --- virt-p2v-make-kickstart.in | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/virt-p2v-make-kickstart.in b/virt-p2v-make-kickstart.in index 779ba62..cbbfb8a 100644 --- a/virt-p2v-make-kickstart.in +++ b/virt-p2v-make-kickstart.in @@ -176,6 +176,16 @@ repo --name=rhel6_${minor}_server_optional --baseurl=$baseurl/Server/optional/$a

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

I am trying to add a kickstart file to my automatic installation and make it more automatic. However, when I comment out the append ks=... line in the example below, the computer boots properly. If I uncomment that line, then I get a kernel panic: VFS: Cannot open root device "" or 09:02 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root

-----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

Here's what I'm currently doing in ks.cfg: %pre #!/bin/sh echo -n "Please enter blah: " read blah echo $blah > /tmp/ks-blah I know that "read blah" works fine, because after that I see the variable in the /tmp file. The problem is, echo doesn't seem to work at this stage. This pretty much kills the idea of an interactive %pre script. I was thinking to

I have a kickstart file created that works great for installing CentOS on PVM''s and now I want to use it for HVM''s as well. The problem is that when I attempt to run the install, it seems to ignore the kickstart and starts prompting me for all the things I already have specified in the kickstart. Any idea what I could be doing wrong? Here is the command im using to get things

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

Has anyone successfully used a kickstart file in tandem with the "virt-install" command? I can get a generic install to begin if I omit the "-x" flag and the kickstart parameters? It seems that virt-install simply ignores my kickstart parameters. virt-install --location=http://www.gtlib.gatech.edu/pub/centos/4.5/os/i386/ --noautoconsole --file=/dev/VolGroup00/lv_centos45

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