similar to: Using DNS in pxelinux.cfg

Hi all - I'm not sure if it's appropriate to ask this here, but I don't see this question explicitly answered anywhere. Is there an EFI version of "pxelinux.0" that will function basically the same way and read the same pxelinux.cfg/default menu files? I've got a really dodgy grubx64.efi EFI PXE menu up at work, but it can't load the 1.2 gigabyte LiveCD that we use

Hi I am running a pxe diskless node in f13 and I have some proposals to make ovirt-early working in this version. nash is no more available (nash/mkinitrd is replaced by dracut), so this following command fails : "echo "network --device $DEVICE --bootproto dhcp" | nash" it makes the network configuration incomplete. I replace the linuxrc command by dhclient and it's

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

----- "Nicolas Ochem" <nicolas.ochem at alcatel-lucent.com> wrote: > > However for this to work you need to add runtime_mode=ovirt in > pxelinux.cfg/default in the kernel boot options. > Fantastic! Thanks Nicolas, that's done the trick. The node now boots and sets up it's interfaces. The host now appears in the management server user interface and

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

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

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

Here is my script for post install if you want to try it. In order for the shuffling to not occur you do need to create the udev rules file somehow. I am not sure how mangled this will be in email but it is worth a try. It should run OK with nothing else. I have a better version in the works but the enhancements are mainly useful for Fedora 19-21. I did forget to say I also block

Hi, I installed ovirt on fedora 12 (64 bits) successfully but I had to make some changes to make it work. 1. Installation from rpms builded from the lastest git version 2. Patch ace : missing backslashes in sed commands vim /usr/share/ace/modules/ovirt/manifests/freeipa.pp line 33 : '/\\[kdcdefaults\\]/a \\ kdc_ports = 88' single_exec {"set_kdc_defaults":

Define out of order in this case just so I know for sure what you mean. What my solution does, or at least does reliably in my case, is make sure the interfaces are in the same order once installed as the install kernel saw them. It won't re-order them to be sequential based on bus, mac or driver. I am working on that but it will also include naming the devices based on the module

As I sit here staring at my manifests (and pondering a module to control Glassfish), I''m pondering the best way to do a first-run of puppet to get the initial repositories and puppet configuration downloaded. My theory is that I''ll modify rc.local (or replace firstboot-tui, we don''t use it with automated builds) to run puppetd twice - once to request the certificate,

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 correspond to the physical device ports 1 and 2). I need a third one and want that to come up as eth2. After adding the hardware, kickstart now fails because for some reason it goes through a rename process where it makes the newly added

Can anybody explain to me what's going on here? This is a CentOS 4 i386 system. [root at edison ~]# rm -f /etc/prelink.cache [root at edison ~]# /etc/cron.daily/prelink [root at edison ~]# rpm -qf /usr/bin/sqlite3 sqlite-3.3.6-2 [root at edison ~]# rpm --verify sqlite prelink: /usr/bin/sqlite3: at least one of file's dependencies has changed since prelinking S.?.....

does the IPAPPEND option still exist? If so I want clearification on it please. Out of the syslinux documentation it says the following. The flag_val is an OR of the following options: 1: indicates that an option of the following format should be generated and added to the kernel command line: ip=client-ip:boot-server-ip:gw-ip:netmask ... based on the input from the DHCP/BOOTP or PXE boot

I'm using ipappend and getargs.com with a dos boot image to get the environment variables for the IP and MAC. The format of the %ip% environment variable is ip=<client-ip>:<boot-server-ip>:<gw-ip>:<netmask> Is there a way to tell ipappend to assign these to individual arguments. Or does anyone know a good way to parse each of these to individual variables in dos. What

Hi, When we meet UEFI or EFI firmware, lots of linux os release use GRUB bootloader. But I wanna use isolinux to boot the installation environment and also the linux os installed. Some question puzzled me. Now, I look for your help: 1. I didn't found information about how to use syslinux(isolinux,etc.) in uefi. I wanna know that are there some differences of the isolinux configuration

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

FYI -------- Original Message -------- Subject: IPAPPEND on http://syslinux.zytor.com/faq.php#config Date: Mon, 31 Jan 2005 15:20:00 +0100 From: Pascal Terjan <pterjan at mandrakesoft.com> Organization: Mandrakesoft To: david at weekly.org Hi, I needed to get the MAC from which we booted using pxelinux (in order to know which interface we used to boot). I found reading the source that

Is it normal for pxelinux to append something like BOOTIF=01-aa-bb-cc-dd-ee-ff ? the leading 01- is there in my config file name, but this doesn't seem to be right behaviour. Can someone confirm if this is a bug? I tried this on syslinux 3.21. thanks. -- Ram Yalamanchili

Hi, Question number 3 :) I'd like to do something like this: display text.msg append text kssendmac ksdevice=eth1 ks=http://1.2.3.4/footprint/ default localboot label localboot localboot 0x80 label system?5 kernel vmlinuz append initrd=initrd.img ip=1.2.3.5 netmask=255.255.255.192 gateway=1.2.3.1 label system6 kernel vmlinuz append initrd=initrd.img ip=1.2.3.6