"A" == Alexey Yaremchuk a.yaremch@yandex.ru writes:
Hi Alexey,
A> Dear experts, I am trying to install a Qlustar OS on several A> Ethernet-linked machines and still compute nodes do not boot. The A> installer reports that there have been no errors, head and FE VM A> nodes do start, Qluman sees them and I could not find any error A> messages from dmesg except insignificant note that firmware load A> for regulatory.db failed. I installed a Debian system on one of A> compute nodes and upon configuring the network interface with a A> static address, established an ssh connection both with the head A> and VM-FE nodes. At least this ensures that cables are OK. If I A> configure it as dhcp, it does not discover dhcp server. If I A> force BIOS boot from the network, I receive either A> PXE-E51: No DHCP or proxyDHCP offers were received A> from Intel Boot Agent, if I make BIOS use only Legacy OpROM, or A> Media Present ... Start PXE Boot over IPv4 ... A> with a silent subsequent fall back into BIOS Setup, if I choose A> to use UEFI driver. I tried different combinations of Boot Device A> Control {UEFI_and_Legacy_OpROM|UEFI_only|Legacy_OpROM_only}, Boot A> from Network Devices {Legacy_OpROM_first|UEFI_driver_first}, OS A> TYPE {Other_OS|Windows_UEFI_mode} in BIOS Setup, and none of them A> worked. Qluman confirms that Boot network is configured as dhcp, A> and systemctl says that there are no failed services.
A> Since I am the only one on the forum with such a problem, A> probably it can be fixed easily. However, I have no idea what to A> check and look forward for help.
you can check in /var/log/syslog on the head whether DHCP and TFTP request arrive. If they don't, your UEFI BIOS might be broken. It's also possible that your legacy BIOS mode is broken and can't handle grub as bootloader which we use in our latest versions. You can try legacy PXElinux support by installing the qlustar-netboot-compat package as described in the release notes:
https://docs.qlustar.com/en-US/Qlustar_Cluster_OS/11.0/html-single/Release_N...
If you do so, you will have to restart qlumand (service qluman-server restart) and write the dnsmasq config.
If all this doesn't work, you will have to check low-level with tcpdump to see what the node sends out to the head when trying to boot.
Best,
Roland