Enable UEFI Red Hat support on Cobbler (2.6.7) - HOW?
by Ž D
Hallo. I was successful in UEFI boot and install, here are details:
1) Cobbler server : 2.6.9
source: ?, ?
build time: Fri Jun 12 07:42:24 2015
Cobbler is installed on Oracle Linux 6.6
2) I am installing Oracle Linux R6-U6-x86_64 on the Oracle Server x3-2
3) DHCP service is provided by another box, the config is:
host my-hostname.domain.com {
hardware ethernet 00:10:e0:aa:aa:aa;
fixed-address 10.xx.xx.xx;
next-server 10.yy.yy.yy; # my cobbler server
filename "/grub/BOOTX64.efi";
}
4) How to find proper BOOTX64.efi file, read the doc:
http://docs.oracle.com/cd/E37670_01/E41137/E41137.pdf
See the paragraph 1.4.7 (starts on page 9), the page 10 talks about
UEFI-based PXE client.
This is the key: UEFI-based PXE clients can use the BOOTX64.efi boot
loader, which is available as EFI/BOOT/BOOTX64.efi from the Oracle Linux
6 Update 6 Media Pack DVD image.
So I placed BOOTX64.efi in <my_cobbler_server>:/var/lib/tftpboot/grub/
5) I also have the file splash.xpm.gz in
<my_cobbler_server>:/var/lib/tftpboot/grub/
6) The file /var/lib/tftpboot/grub/00:10:e0:aa:aa:aa looks like
timeout=10
splashimage=(nd)/splash.xpm.gz
title OL-R6-U6-x86_64-UEFI
root (nd)
kernel /images/OL-R6-U6-x86_64/vmlinuz ksdevice=bootif lang= text
ks=http://my_cobbler_server/cblr/svc/op/ks/system/host_name
initrd /images/OL-R6-U6-x86_64/initrd.img
7) The kickstart file is
# ks for OL 6.6 UEFI
install
text
url --url=http://10.yy.yy.yy/cobbler/links/OL-R6-U6-x86_64
lang en_US.UTF-8
keyboard us
rootpw --iscrypted $1$zw2wh8P1$zZMsVBx4.HbZNxM8p1uPX1
firewall --disabled
authconfig --enableshadow --enablemd5
selinux --disabled
timezone --utc America/Los_Angeles
reboot
bootloader --location=partition
clearpart --all --initlabel
part /boot/efi --fstype=vfat --size=200 --asprimary --ondisk=sda
part /boot --fstype=ext4 --size=500 --label=/boot --asprimary --ondisk=sda
part / --fstype=ext4 --size=8192 --grow --maxsize=51200 --label=/
--ondisk=sda
part /var --fstype=ext4 --size=4096 --label=/var --ondisk=sda
part /u01 --fstype=ext3 --size=4096 --label=/u01 --ondisk=sda
part swap --size=16384 --label=swap --ondisk=sda
%packages
@base
@core
device-mapper-multipath
kexec-tools
net-tools
pciutils
sysfsutils
system-config-kickstart
wget
lsscsi
nfs-utils
8) Works for me. Let me know if you need any other detail?
--
Thanks,
Zarko
7 years, 10 months
unsubscribe
by Sethuraman, Murali
________________________________________________________
The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
8 years
Multiple subnets, multiple dhcp --dhcp-tag, profiles, distro
by Tory M Blue
So I'm running into some issues and I'm sure it's a minor brain fart
on my part. But the documentation has not squared me away.
I have a cobbler server running DHCP for 3 networks, my cobbler
server has 3 interfaces and I have 3 dhcp stanzas (whatever).
I can set a different next server, which is the interface IP on that
subnet/vlan. No issue. I can build a system from the 10.13.4 network
just fine. But if I try to build from the 10.13.200 net, I can get a
dhcp address, load the kernel, but the issue is the Distro has the IP
address from the 10.13.4.x network in it so the pxelinux.cfg/default
has the wrong subnet/vlan hardcoded; and thus tries to load the
kickstart
LABEL CentOS7-x86_64_Standard
kernel /images/CentOS7-x86_64/vmlinuz
MENU LABEL CentOS7-x86_64_Standard
append initrd=/images/CentOS7-x86_64/initrd.img ksdevice lang=
kssendmac text
ks=http://10.13.4.101/cblr/svc/op/ks/profile/CentOS7-x86_64_Standard
ipappend 2
So obviously if a host is on the 10.13.200 net, receives a 10.13.200.x
address, and starts booting, cobbler is sending it that kickstart line
and it should not be going to 10.13.4.101 when the local network is
ready to receive at 10.13.200.101.
The metadata tree has the 10.13.4.101 address, and I thought about
setting it to $next_server, but it seems if I do it in the profile via
cobbler_web, it over writes the default file with 10.13.4.101 (the
cobbler host server IP)
I've removed $next-server from the cobbler settings file
#next_server: 10.13.4.101
But server is still configured.
server: 10.13.4.101
So the issue is really the server configuration inside settings. it
mentions --server-override, but I don't want to have a handful of
profiles for the same image.. I would like to just boot up a server
and say use Profile-CentOS-standard and ignore which network it's
coming from., want wildcards or other to figure things out.
Any ideas? really i've been searching and "nothing" I've found has
made me understand where I'm falling short. -dhcp-tags,
--server-override
Thanks
tory
################## DHCP ############
ddns-update-style interim;
allow booting;
allow bootp;
ignore client-updates;
set vendorclass = option vendor-class-identifier;
subnet 10.13.4.0 netmask 255.255.255.0 {
option routers 10.13.4.6;
option domain-name-servers 10.13.4.220, 10.13.7.101, 10.13.7.102;
option domain-name "eng.domain.net";
option subnet-mask 255.255.255.0;
range dynamic-bootp 10.13.4.75 10.13.4.99;
filename "/pxelinux.0";
default-lease-time 21600;
max-lease-time 43200;
next-server 10.13.4.101;
}
subnet 10.13.5.0 netmask 255.255.255.0 {
option routers 10.13.5.6;
option domain-name-servers 10.13.4.220, 10.13.7.101, 10.13.7.102;
option domain-name "eng.domain.net";
option subnet-mask 255.255.255.0;
range dynamic-bootp 10.13.5.220 10.13.5.239;
filename "/pxelinux.0";
default-lease-time 21600;
max-lease-time 43200;
next-server 10.13.5.100;
}
subnet 10.13.200.0 netmask 255.255.255.0 {
option routers 10.13.200.6;
option domain-name-servers 216.249.24.15, 10.13.6.56;
option domain-name "gc.sv.domain.net";
option subnet-mask 255.255.255.0;
range dynamic-bootp 10.13.200.75 10.13.200.85;
filename "/pxelinux.0";
default-lease-time 21600;
max-lease-time 43200;
next-server 10.13.200.101;
}
8 years
How Cobbler Triggers Works
by slgray
Hi, I am new to cobbler and I want to use triggers use to do some post
install tasks, suck as create a system profile when the system finish the
first boot from cobbler .
I have read the docs at
http://cobbler.github.io/manuals/2.6.0/4/4/1_-_Triggers.html. But still do
not know how to call the triggers, which url I should send request to.
Hope somebody can provide detail docs for how triggers work, Thanks.
--
*Regards,*
*Slgray*
8 years
cobbler efi boot issue
by slgray
My cobbler server works well with BIOS boot servers. When comes to efi boot
servers, it can not boot. Have the same problem as this GitHub issue.
https://github.com/cobbler/cobbler/issues/1572
The author says he fix this by replacing ‘grub-x86_64.efi’, but it not
works in my environment.
There this no boot menu, and boot from the first entry.
Cobbler version:2.6.11
8 years
