Tftpboot: Difference between revisions
Jump to navigation
Jump to search
Created page with "'''Tftpboot setting to boot diskless VME controllers'''" |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''Tftpboot setting to boot diskless VME controllers''' | '''Tftpboot setting to boot diskless VME controllers''' | ||
If ''/tftpboot'' directory does not exist yet, copy it from ''/usr/downloads'' (it come from Bryan Moffit in April 2025). | |||
File ''/tftpboot/efi/boot/grub2/grub.cfg'' should have following contents: | |||
function load_video { | |||
insmod efi_gop | |||
insmod efi_uga | |||
insmod video_bochs | |||
insmod video_cirrus | |||
insmod all_video | |||
} | |||
load_video | |||
set gfxpayload=keep | |||
insmod gzio | |||
set timeout=2 | |||
menuentry 'Diskless CentOS7 x86_64, any network device' --class redhat --class gnu-linux --class gnu --class os { | |||
linuxefi linux-install/CentOS7-x86_64-Diskless/vmlinuz-3.10.0-1062.9.1.el7.x86_64 zram=1 ip=::::::dhcp root=nfs:192.168.10.1:/diskless/CentOS7/x86_64/root ro vga=0x305 module_blacklist=ipmi_si,ipmi_msghandler,ipmi_devintf,w83977f_wdt | |||
initrdefi linux-install/CentOS7-x86_64-Diskless/initramfs-jvme-3.10.0-1062.9.1.el7.x86_64.img | |||
} | |||
that file will serve all EFI-bootable VME controllers. | |||
In directory ''/tftpboot/pxelinux.cfg'', PXE-bootable controllers boot files are stored. For example: | |||
C0A80A06 -> test6 | |||
test6 | |||
where ''C0A80A06'' is test6's IP address in hex format (192.168.10.6), and ''test6'' has following contents: | |||
default CentOS7 | |||
label CentOS7 | |||
kernel CentOS7-x86_64-Diskless/vmlinuz-3.10.0-1062.9.1.el7.x86_64 | |||
append initrd=CentOS7-x86_64-Diskless/initramfs-jvme-3.10.0-1062.9.1.el7.x86_64.img ip=bootdev:dhcp root=nfs:192.168.10.1:/diskless/CentOS7/x86_64/root,tcp ro ifname=bootdev:00:20:38:0A:07:D7 | |||
It should be mentioned that in both cases VME controller's root directories will be mounted as 'read only'. All individual controller-specific directories will be placed in 'snapshot' area. | |||
Latest revision as of 16:09, 15 May 2025
Tftpboot setting to boot diskless VME controllers
If /tftpboot directory does not exist yet, copy it from /usr/downloads (it come from Bryan Moffit in April 2025).
File /tftpboot/efi/boot/grub2/grub.cfg should have following contents:
function load_video {
insmod efi_gop
insmod efi_uga
insmod video_bochs
insmod video_cirrus
insmod all_video
}
load_video
set gfxpayload=keep
insmod gzio
set timeout=2
menuentry 'Diskless CentOS7 x86_64, any network device' --class redhat --class gnu-linux --class gnu --class os {
linuxefi linux-install/CentOS7-x86_64-Diskless/vmlinuz-3.10.0-1062.9.1.el7.x86_64 zram=1 ip=::::::dhcp root=nfs:192.168.10.1:/diskless/CentOS7/x86_64/root ro vga=0x305 module_blacklist=ipmi_si,ipmi_msghandler,ipmi_devintf,w83977f_wdt
initrdefi linux-install/CentOS7-x86_64-Diskless/initramfs-jvme-3.10.0-1062.9.1.el7.x86_64.img
}
that file will serve all EFI-bootable VME controllers.
In directory /tftpboot/pxelinux.cfg, PXE-bootable controllers boot files are stored. For example:
C0A80A06 -> test6 test6
where C0A80A06 is test6's IP address in hex format (192.168.10.6), and test6 has following contents:
default CentOS7
label CentOS7
kernel CentOS7-x86_64-Diskless/vmlinuz-3.10.0-1062.9.1.el7.x86_64
append initrd=CentOS7-x86_64-Diskless/initramfs-jvme-3.10.0-1062.9.1.el7.x86_64.img ip=bootdev:dhcp root=nfs:192.168.10.1:/diskless/CentOS7/x86_64/root,tcp ro ifname=bootdev:00:20:38:0A:07:D7
It should be mentioned that in both cases VME controller's root directories will be mounted as 'read only'. All individual controller-specific directories will be placed in 'snapshot' area.