From Floydsmith at aol.com Tue Jul 10 19:16:01 2012 From: Floydsmith at aol.com (Floydsmith at aol.com) Date: Tue, 10 Jul 2012 15:16:01 -0400 (EDT) Subject: fetching kickstart file error in fc 17 install - ks file is on vfat fs Message-ID: <35d81.1f6d880a.3d2dd970@aol.com> Upon trying to kickstart install fc 17 I get the following error: fetching kickstart from /dev/sda1:/k17.ks warning: unable to process initqueu warning: /dev/ram does not exist Then it drops to a debug shell. I boot using DOS 7.10 on sda1 (C:) vfat fs to install as have done successfully for over 7 years. My image is on a DVD. My install batch script uses: \linld097\linld.com initrd=\17pi.i image=\17pi.k "cl=rw root=/dev/ram ks=hd:sda1:\k17.ks" The initrd and kernel are from the install disk. The reason I need to use a DOS/linld boot (as opposed to say some other boot sector method like SYSLINUX or GRUB) is with my method I can (easily) switch to different config.sys file(s) (in scripts) and have linux boot up (unattended) three or more times to perform various configuration setups after the install - the process takes about 2 hours but is fully automated this way. At the very end I can have a script boot up some other OS such as windows XP. Floyd, -------------- next part -------------- An HTML attachment was scrubbed... URL: From Floydsmith at aol.com Wed Jul 11 10:22:43 2012 From: Floydsmith at aol.com (Floydsmith at aol.com) Date: Wed, 11 Jul 2012 06:22:43 -0400 (EDT) Subject: more on fetching kickstart file error in fc 17 install - ks file is on vfat fs Message-ID: <47968.7dd455db.3d2eadf3@aol.com> This is not a problem with fetching config file via vfat using linld as I originally thought since I found my kickstart file in the tmp dir. There is no /dev/ram device as the warning says but I am not sure this is a problem. I can find no log file other than /tmp/ks.info has the line: parsed_kickstart="/tmp/1wviHN-ks.cfg" Here is my greatly reduced for debuging config file: auth --disableshadow keyboard us lang en_US install cdrom timezone America/New_York bootloader --location=none part / --onpart=sda9 --fstype=ext3 clearpart --none rootpw --iscrypted $1$812aSfDP$n3uhf7d//cw1Lh.cei.ue1 autostep --autoscreenshot %packages @base %end -------------- next part -------------- An HTML attachment was scrubbed... URL: From lwj0012 at gmail.com Fri Jul 13 04:42:38 2012 From: lwj0012 at gmail.com (Wenjie Liu) Date: Fri, 13 Jul 2012 12:42:38 +0800 Subject: How to add a command to kickstart? Message-ID: hi, I am a newbie to kickstart, thanks for your time to read my posts. In my project, i want to add some new commands to kickstart. What i have done is write a new class called "police_confirm", and i also put the class and its corresponding command "confirm" to commandMap. But when i use revisor to generate a new livecd, there comes an error, "unknown command confirm", i don't know where the problem is. please give me some advise, thank you! -------------- next part -------------- An HTML attachment was scrubbed... URL: From vpodzime at redhat.com Fri Jul 13 08:57:46 2012 From: vpodzime at redhat.com (Vratislav Podzimek) Date: Fri, 13 Jul 2012 10:57:46 +0200 Subject: How to add a command to kickstart? In-Reply-To: References: Message-ID: <1342169866.3860.11.camel@dhcp-29-14.brq.redhat.com> On Fri, 2012-07-13 at 12:42 +0800, Wenjie Liu wrote: > hi, I am a newbie to kickstart, thanks for your time to read my > posts. > > > In my project, i want to add some new commands to kickstart. What i > have done is write a new class called "police_confirm", and i also put > the class and its corresponding command "confirm" to commandMap. Did you add it to the right part of the commandMap? Could you attach your patch? > But when i use revisor to generate a new livecd, there comes an error, > "unknown command confirm", i don't know where the problem is. > > > please give me some advise, thank you! > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- Vratislav Podzimek Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic From Kay at thewilliams.net Mon Jul 23 17:59:34 2012 From: Kay at thewilliams.net (Kay Williams) Date: Mon, 23 Jul 2012 10:59:34 -0700 Subject: Kickstart option to avoid "Storage Device Warning" Message-ID: <3527434A537F2F42A53BAA31DC03BB6A5BE6AF5611@SERVER1.family.local> Hello, My organization uses a script that calls virt-install providing a kickstart file to automate KVM virtual machine creation. This process needs to be automated as we create and destroy dozens of virtual machines on a nightly basis to test our applications. Our script works fine when installing older OS versions (RHEL 6.2 and prior). But with recent OS versions (RHEL 6.3), Anaconda installation halts with a warning: ------------ Storage Device Warning The storage device below may contain data. Virtio Block Device We could not detect partitions or filesystems on this device. This could be because the device is blank, unpartitioned or virtual. ... [Yes, discard any data] [No, keep any data] ----------- How can we avoid this warning, or accept it automatically? I did not see an option in the recent kickstart documentation. Here is the virt-install command we are using: virt-install --name %{fqdn} --ram 1000 \ --file /var/lib/libvirt/images/%{fqdn}.img \ --file-size 30 \ --location %{url} \ --extra-args "%{boot-options} ks=%{url}/ks.cfg"\ --noreboot And here is the kickstart file: install network --hostname %{fqdn} rootpw --iscrypted "%{crypt-password}" lang en_US clearpart --all --initlabel part / --fstype ext4 --size 1 --grow --asprimary part swap --recommended part /boot --fstype ext2 --size 512 --asprimary bootloader --location=mbr timezone America/Vancouver auth --enablemd5 --enableshadow --enablecache selinux --enforcing reboot Thanks for your assistance, Kay From skvidal at fedoraproject.org Mon Jul 23 18:02:34 2012 From: skvidal at fedoraproject.org (Seth Vidal) Date: Mon, 23 Jul 2012 14:02:34 -0400 (EDT) Subject: Kickstart option to avoid "Storage Device Warning" In-Reply-To: <3527434A537F2F42A53BAA31DC03BB6A5BE6AF5611@SERVER1.family.local> References: <3527434A537F2F42A53BAA31DC03BB6A5BE6AF5611@SERVER1.family.local> Message-ID: On Mon, 23 Jul 2012, Kay Williams wrote: > Hello, > > My organization uses a script that calls virt-install providing a kickstart file to automate KVM virtual machine creation. This process needs to be automated as we create and destroy dozens of virtual machines on a nightly basis to test our applications. Our script works fine when installing older OS versions (RHEL 6.2 and prior). But with recent OS versions (RHEL 6.3), Anaconda installation halts with a warning: > > ------------ > Storage Device Warning > > The storage device below may contain data. > > Virtio Block Device > > > We could not detect partitions or filesystems on this device. > > This could be because the device is blank, unpartitioned or virtual. > ... > > [Yes, discard any data] [No, keep any data] > ----------- > > How can we avoid this warning, or accept it automatically? I did not see an option in the recent kickstart documentation. > > Here is the virt-install command we are using: > > virt-install --name %{fqdn} --ram 1000 \ > --file /var/lib/libvirt/images/%{fqdn}.img \ > --file-size 30 \ > --location %{url} \ > --extra-args "%{boot-options} ks=%{url}/ks.cfg"\ > --noreboot > > And here is the kickstart file: > > install > network --hostname %{fqdn} > rootpw --iscrypted "%{crypt-password}" > lang en_US > clearpart --all --initlabel > part / --fstype ext4 --size 1 --grow --asprimary > part swap --recommended > part /boot --fstype ext2 --size 512 --asprimary > bootloader --location=mbr > timezone America/Vancouver > auth --enablemd5 --enableshadow --enablecache > selinux --enforcing > reboot > > Thanks for your assistance, > Kay > When I added zerombr to my kickstarts that issue went away. I think that should do it b/c the devices will then have a structure that anaconda won't flake out on. -sv From Kay at thewilliams.net Mon Jul 23 19:48:09 2012 From: Kay at thewilliams.net (Kay Williams) Date: Mon, 23 Jul 2012 12:48:09 -0700 Subject: Kickstart option to avoid "Storage Device Warning" In-Reply-To: References: <3527434A537F2F42A53BAA31DC03BB6A5BE6AF5611@SERVER1.family.local> Message-ID: <3527434A537F2F42A53BAA31DC03BB6A5BE6AF5615@SERVER1.family.local> zerombr did the trick. Many thanks. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Seth Vidal Sent: Monday, July 23, 2012 11:03 AM To: Discussion list about Kickstart Subject: Re: Kickstart option to avoid "Storage Device Warning" On Mon, 23 Jul 2012, Kay Williams wrote: > Hello, > > My organization uses a script that calls virt-install providing a kickstart file to automate KVM virtual machine creation. This process needs to be automated as we create and destroy dozens of virtual machines on a nightly basis to test our applications. Our script works fine when installing older OS versions (RHEL 6.2 and prior). But with recent OS versions (RHEL 6.3), Anaconda installation halts with a warning: > > ------------ > Storage Device Warning > > The storage device below may contain data. > > Virtio Block Device > > > We could not detect partitions or filesystems on this device. > > This could be because the device is blank, unpartitioned or virtual. > ... > > [Yes, discard any data] [No, keep any data] > ----------- > > How can we avoid this warning, or accept it automatically? I did not see an option in the recent kickstart documentation. > > Here is the virt-install command we are using: > > virt-install --name %{fqdn} --ram 1000 \ > --file /var/lib/libvirt/images/%{fqdn}.img \ > --file-size 30 \ > --location %{url} \ > --extra-args "%{boot-options} ks=%{url}/ks.cfg"\ > --noreboot > > And here is the kickstart file: > > install > network --hostname %{fqdn} > rootpw --iscrypted "%{crypt-password}" > lang en_US > clearpart --all --initlabel > part / --fstype ext4 --size 1 --grow --asprimary part swap > --recommended part /boot --fstype ext2 --size 512 --asprimary > bootloader --location=mbr timezone America/Vancouver auth --enablemd5 > --enableshadow --enablecache selinux --enforcing reboot > > Thanks for your assistance, > Kay > When I added zerombr to my kickstarts that issue went away. I think that should do it b/c the devices will then have a structure that anaconda won't flake out on. -sv _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From theaton at lanl.gov Thu Jul 26 20:19:52 2012 From: theaton at lanl.gov (Tony Heaton) Date: Thu, 26 Jul 2012 14:19:52 -0600 Subject: Can't get files to %include In-Reply-To: <20120424191144.GA3159@ns2.sdsitehosting.net> References: <20120417124951.GA4998@ns2.sdsitehosting.net> <4F8FE162.9000303@avaya.com> <20120419140439.GA10574@ns2.sdsitehosting.net> <2C4B4AE6B69DF14FACF9B568E586EA8F37773F0C56@ESESSCMS0359.eemea.ericsson.se> <20120424113544.GA1420@ns2.sdsitehosting.net> <4F9692F5.3030107@avaya.com> <20120424191144.GA3159@ns2.sdsitehosting.net> Message-ID: <5011A668.3060104@lanl.gov> I'm having the same problem with %include in %pre. It worked before 5.4 but does not now . The error in the logs is: parse-kickstart [ 20.917210] parse-kickstart ERROR: The following problem occurred on line 0 of the kickstart file: [ 20.917213] [ 20.917214] Unable to open input kickstart file: Could not open/read file:///tmp/part-include [ 20.917215] ERROR: The following problem occurred on line 0 of the kickstart file: Unable to open input kickstart file: Could not open/read file:///tmp/part-include Below is part of kickstart code ################################ # Begining Section . . . . clearpart --all --initlabel zerombr %include /tmp/part-include ################################### %pre #!/bin/bash # Setup partitions dynamically echo "part / --ondisk=sda --fstype ext3 --size 30000" >> /tmp/part-include echo "part swap --ondisk=sda --recommended" >> /tmp/part-include . . . . On 04/24/2012 01:11 PM, John Oliver wrote: > On Tue, Apr 24, 2012 at 02:48:05PM +0300, Adrian Cruceru wrote: >> Hi John, >> >> The %include directives are parsed and used immediately after "%pre". > > If I %include a file that exists on the DVD in %pre, the contents of > that file are run just as if they were in %pre themselves. > >> This information is used for the install process that is between %pre >> and %post. > > See above. > >> Anything you do in %post is too late, system is already installed... you >> can't really specify install packet list "x" after it's already installed... > > I can bang out a series of commands in %post. The description of the > %include section says, "Use the %include /path/to/file command to > include the contents of another file in the kickstart file as though the > contents were at the location of the %include command in the kickstart > file." There could be more, secret, docs somewhere with more > limitations, but... what would be the point of announcing a command that > very strongly hints it does X, tell everyone it does X, and then make it > do Y anyway? > >> Not to mention the fact that %post is already chrooted in the installed >> system, and the "/tmp" folder points to hard disk instead of ram disk. > > Yes, I know. Irrelevant... I can copy files from the DVD to /tmp in > %pre, copy them from /tmp to /mnt/sysimage/tmp in %post --nochroot, and > then access them in /tmp in %post That isn't the issue at all. It > isn't that I'm trying to %include files that don't exist... they do, > they're readable, they contain valid shell commands. > > -- Tony Heaton HPC-5 (505) 667-9015 theaton at lanl.gov "When injustice becomes law, resistance becomes duty." -Thomas Jefferson