search for: ksdevic

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

...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 ship boxes with two NICs and knew interface 1 was always eth0.? With C7 comes the interface naming convention changes and that's where questions have arisen about that option.? It's been set as ksdevice=eno1 since I k...

Hello, ksdevice specifies which NIC to be used during the network install. The new naming conventions indeed make this more complicated than it needs to be. To go back to the old naming scheme (eth0, eth1 ...) just add this to boot parameters (kernel cmdline): biosdevname=0 net.ifnames=0 HTH Lucian -- Sent fro...

Nux! wrote: > Hello, > > ksdevice specifies which NIC to be used during the network install. > > The new naming conventions indeed make this more complicated than it needs > to be. To go back to the old naming scheme (eth0, eth1 ...) just add this > to boot parameters (kernel cmdline): > biosdevname=0 net.ifnames=0...

...2.168.0.201 -> 192.168.0.7 TFTP Read Request, File: linux-install/CentOS4.3/x86_64/initrd.img, Transfer type: octet But then it never tries to get the ks.cfg. I am booting it with: label centos kernel CentOS4.3/x86_64/vmlinuz append initrd=CentOS4.3/x86_64/initrd.img ramdisk_size=7000 ksdevice=eth0 ks=http://192.168.0.7/network-install/ks.cfg.x86_64 (that last line should be all one line) in the /tftpboot/linux-install/pxelinux.cfg/01-00-0c-29-14-3a-c5 config file which it tftp's so it should know that it needs to get the ks.cfg.x86_64 file. I have this same setup working for i3...

...7, 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 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 we're not using PXE and |> probably won't...

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 we're not using PXE and probably won't for the forseeable future.? This...

On Fri, 3 Nov 2017, Mark Haney wrote: > On 11/01/2017 05:02 PM, James A. Peltier wrote: >> Leaving ksdevice= off the command line will prompt you for the location of >> the kickstart file and the device you want to use to kickstart >> > Well, things just got weird with this.? The first couple of times I included > the biosdevname etc, on the command line with ksdevice=eth0 it worked...

On 11/01/2017 01:57 PM, Tristan Hoar wrote: > > Strictly speaking it is depricated > https://anaconda-installer.readthedocs.io/en/latest/boot-options.html#d > eprecated-options > > Regards, > > Tris > Okay, so it looks like I can simply change ksdevice=eth0? to bootdev=eth0, correct? -- Mark Haney Network Engineer at NeoNova 919-460-3330 option 1 mark.haney at neonova.net www.neonova.net

On 11/01/2017 05:02 PM, James A. Peltier wrote: > Leaving ksdevice= off the command line will prompt you for the location of the kickstart file and the device you want to use to kickstart > Well, things just got weird with this.? The first couple of times I included the biosdevname etc, on the command line with ksdevice=eth0 it worked perfectly.? Sometime ye...

...enu label 32-Bit Installs: menu disable label rhel5host32 menu label RHEL 5.8 Host Install menu indent 3 kernel /var/lib/tftpboot/bootImages/vmlinuz_RHEL5U8x32 append initrd=/var/lib/tftpboot/bootImages/initrd_RHEL5U8x32.img ramdisk_size=9216 noapic acpi=off ksdevice=eth0 console=ttyS0,9600 ks=nfs:37.1.1.1:/var/lib/tftpboot/kickstart/ks_RHEL5U8x32_host.cfg label rhel5vm32 menu label RHEL 5.8 Virtual Machine Install menu indent 3 kernel /var/lib/tftpboot/bootImages/vmlinuz_RHEL5U8x32 append initrd=/var/lib/tftpboot/bootImages/in...

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 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 we're not using PXE and > probably won't for th...

...t 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. > Strictly speaking it is depricated https://anaconda-installer.readthedocs.io/en/latest/boot-options.html#d eprecated-options Regards, Tris ************************************************************* This email and any files transmitted with it are confidential and inte...

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. -- Chris Adams <linux at cmadams.net>

Greetings all, Is there currently any mechanism in pxelinux the would send a mac address of the pxe booted interface through to the linux kernel much like ipappend can send the ip address? Kickstarting a system with multiple interfaces can be troublesome. ksdevice is helpful but only in some circumstances such as forcing eth0, but that doesn't always work since probe order changes depending on what kernel config you have. ksdevice=link is good, however we also have some systems that have one primary interface on the regular network and one private inter...

...h2? >> >> Should I be using the device's MAC address when I set the >> 'network' option in the kickstart file? So instead of 'network >> --device=eth0' I make it 'network -device=aa;bb:cc:dd:eee:ff' ? >> > > kickstart has an option: ksdevice=bootif > > I think that'll let you accomplish what you are trying. Totally unrelated, but this is the reason I love discussions like this getting into the archives. I had no idea this option existed and it just solved an annoying problems I've been trying to think how to solve for...

...I was using this: http://man7.org/linux/man-pages/man7/dracut.cmdline.7.html So my grub entry consists menuentry "Install CentOS 8" { linux /boot/vmlinuz noverifyssl ks=https://something ip=192.168.1.3::192.168.1.1:255.255.255.0::eth0:on:192.168.1.1 biosdevname=0 net.ifnames=0 ksdevice=eth0 inst.sshd sshd=1 initrd /boot/initrd.img } This seems OK to me. But rebooting to start the install for CentOS 8 it just stops and says "system halted". the lines above that have no errors. .3 is the IP I want to use .1 is the GW and the Nameserver in this case. Thanks, Je...

...i_root_xen prompt 0 label manual_install KERNEL /Centos/51/kickstart/vmlinuz APPEND initrd=/Centos/51/kickstart/initrd.img label kickstart_xen KERNEL /Centos/51/kickstart/vmlinuz APPEND initrd=/Centos/51/kickstart/initrd.img ks= http://192.168.1.202/anaconda-ks.cfg ksdevice=link noipv6 label kickstart_noxen KERNEL /Centos/51/kickstart/vmlinuz APPEND initrd=/Centos/51/kickstart/initrd.img ks= http://192.168.1.202/anaconda-ks.noxen.cfg ksdevice=link noipv6 label iscsi_root_xen KERNEL mboot.c32 APPEND /Centos/boot/xen.gz-2.6.18-53.el5 -...

Hi, Is it possible to disable the clear screen when loading syslinux ? Since the IBM BIOS on xSeries systems shows the MAC address of the onboard NICs, I would like to have them on screen when people do a kickstart fro mthe prompt using eg: ksdevice=<MAC address> I personally think that the clear screen is unwanted in most cases since people can add that to the boot message (ctrl-L) if they need it. If all the drivers in POST would do a clear screen, it would be very discomforting and even if syslinux is an exception (being the last...

I am trying to boot a grub entry for CentOS 8 menuentry "Server Install CentOS 8" { linux /boot/vmlinuz noverifyssl ks= https://devgeis.LayeredSolutionsInc.com:443/kickstart/ks_update_to_server8.cfg biosdevname=0 net.ifnames=0 ksdevice=eth0 ip=192.168.1.13 gateway=192.168.1.1 netmask=255.255.255. 0 nameserver=192.168.1.1 inst.sshd sshd=1 initrd /boot/initrd.img } When booting it says that "ip=192.168.1.3" Sorry unknown value. This works on CentOS 7. How do I specify the IP/SN/GW for CentOS kernel...