Posts made by dangbird

@chris_unit As long as it is default NO. Otherwise you have to change it to bzimage and bzimage32 in fog system settings TFTP Server

@chris_unit I just went into my FOG Gui, clicked Fog Config->Kernel Update->Kernel 5.10.50 Tom Elliot 64(Third One I think) and then I clicked Download on the right. It installed. I rebooted for good measure and all worked.

@george1421
FOR SURE your way works PERFECTLY.
I forgot I cannot use $ inside grub.cfg for any variables…
SO you got it working for me.
I APPRECIATE you very much. Let me know any specifics of how I can contribute in return.
I will work on a “Load XenServer from Scratch using FOG” write up at a minimum.

PROBLEM SOLVED after I took out my variables and used your Copy and Paste VI etc.

THANK YOU!

@george1421
WOW - Thats great. I am getting the Boot to Fog Menu, then Selecting the new item with the chain, it starts the boot flashes REAL Fast “syntax error” then kicks to grub> prompt. So I am sure I missed a step…I even dos2unix 'ed the grub.cfg file.
Anyhow, I am guessing its all on my end now. I appreciate it very much. IF I get this working I will do a write up on what I am doing to help others. I did start with trying to get the http working but swapped to direct TFTP and followed your instructions. So I will grab another beverage and start again to see if I can make your magic work.

@george1421
Yes if you just burn the files I provided to USB, and install on a system that is EFI / UEFI only it will pull
/EFI/xenserver/grubx64.efi then /boot/vmlinuz then /install.img

I THINK the magic file is grubx65.efi OR /boot/efiboot.img that it pulls…

So by the system being in UEFI boot Only mode it will boot and load from that same USB…
In otherwords the files I provided burned to USB with rufus etc will boot EFI USB…

According to Citrix Xenserver people they insist the TFTP boot magic for UEFI boot is Here:
https://support.citrix.com/article/CTX217680 But I cannot get it to go with Fog…
I set my DHCP to provide grubx64.efi and can get a Grub menu from FOG but think I am barking up the wrong tree.

I placed a USB Image file ready to UEFI Boot in the same Shared Google Folder as before to try to make it easier.
“UEFIUSBINSTALLER.IMG”
I appreciate the effort.

@george1421

YES!
Here you go.
Let me know what else you need.
https://drive.google.com/drive/folders/1UqKsUVnkOIlsva54WOhpDAu4-1OTABe0

@george1421
Yes everything boots…I get the Fog Menu in EFI mode and I have the DHCP set such that it detects Bios-Legacy or EFI boot.
I can use Fog to EFI Load machines all day long.
As you indicated I can boot this XenServer and Load it via FOG in Legacy mode PERFECT, and its awesome using the http protocol of the version you suggested.

However if I switch to EFI boot, and use the same menu, I get IPXE Exec format error.
“http://fogiphere/boot/xen.gz …Ok”
“Could not select: Exec format error (http://ipxe.org/2e008081)”
See Pic.

@dangbird

Here is the USB version “grub-usb.cfg”

set default="0"

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
insmod part_gpt
insmod ext2

set timeout=5
search --file --set /install.img

menuentry "install" {
    multiboot2 /boot/xen.gz dom0_max_vcpus=1-16 dom0_mem=max:8192M com1=115200,8n1 console=com1,vga
    module2 /boot/vmlinuz xencons=hvc console=hvc0 console=tty0
    module2 /install.img
}

menuentry "no-serial" {
    multiboot2 /boot/xen.gz dom0_max_vcpus=1-16 dom0_mem=max:8192M console=vga
    module2 /boot/vmlinuz console=tty0
    module2 /install.img
}

menuentry "safe" {
    multiboot2 /boot/xen.gz dom0_max_vcpus=1-16 dom0_mem=max:8192M nosmp noreboot noirqbalance no-mce no-bootscrub no-numa no-hap no-mmcfg iommu=off max_cstate=0 nmi=ignore allow_unsafe com1=115200,8n1 console=com1,vga vga=keep
    module2 /boot/vmlinuz xencons=hvc console=hvc0 console=tty0
    module2 /install.img
}

menuentry "multipath" {
    multiboot2 /boot/xen.gz dom0_max_vcpus=1-16 dom0_mem=max:8192M com1=115200,8n1 console=com1,vga
    module2 /boot/vmlinuz xencons=hvc console=hvc0 console=tty0 device_mapper_multipath=enabled
    module2 /install.img
}

menuentry "shell" {
    multiboot2 /boot/xen.gz dom0_max_vcpus=1-16 dom0_mem=max:8192M com1=115200,8n1 console=com1,vga
    module2 /boot/vmlinuz xencons=hvc console=hvc0 console=tty0 bash-shell
    module2 /install.img
}

@george1421

Sorry about the delay, email notification did not hit me.
the Nonsensical entry is a clear display of my ignorance on the boot site of linux.

I found TWO grub configs, both under the EFI folder.
Here is “grub.cfg” - I will Post the Second Grub as an additional reply for clarity.

set default="0"

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
insmod part_gpt
insmod ext2

set timeout=5

menuentry "install" {
    multiboot2 /boot/xen.gz dom0_max_vcpus=1-16 dom0_mem=max:8192M com1=115200,8n1 console=com1,vga
    module2 /boot/vmlinuz xencons=hvc console=hvc0 console=tty0
    module2 /install.img
}

menuentry "no-serial" {
    multiboot2 /boot/xen.gz dom0_max_vcpus=1-16 dom0_mem=max:8192M console=vga
    module2 /boot/vmlinuz console=tty0
    module2 /install.img
}

menuentry "safe" {
    multiboot2 /boot/xen.gz dom0_max_vcpus=1-16 dom0_mem=max:8192M nosmp noreboot noirqbalance no-mce no-bootscrub no-numa no-hap no-mmcfg iommu=off max_cstate=0 nmi=ignore allow_unsafe com1=115200,8n1 console=com1,vga vga=keep
    module2 /boot/vmlinuz xencons=hvc console=hvc0 console=tty0
    module2 /install.img
}

menuentry "multipath" {
    multiboot2 /boot/xen.gz dom0_max_vcpus=1-16 dom0_mem=max:8192M com1=115200,8n1 console=com1,vga
    module2 /boot/vmlinuz xencons=hvc console=hvc0 console=tty0 device_mapper_multipath=enabled
    module2 /install.img
}

menuentry "shell" {
    multiboot2 /boot/xen.gz dom0_max_vcpus=1-16 dom0_mem=max:8192M com1=115200,8n1 console=com1,vga
    module2 /boot/vmlinuz xencons=hvc console=hvc0 console=tty0 bash-shell
    module2 /install.img
}

Hello All - Was wondering if someone can get me over the hill and get the Cigar lit.
Happy to share any files needed.
We use XenServer as a Hypervisor and deploy many servers each week. Bios mode works AMAZING with Fog.
Here is the Menu Entry we use where we call a Script with an Answer file to load over the network:

kernel http://${fog-ip}/iso/xen82/boot/xen dom0_max_vcpus=4 dom0_mem=1024M,max:1024M com1=115200,8n1 console=com1,vga
module http://${fog-ip}/iso/xen82/boot/vmlinuz xencons=hvc console=hvc0 console=tty0 answerfile=http://${fog-ip}/iso/xen82/scripts/answerfile-82 install
module http://${fog-ip}/iso/xen82/install.img
boot

I based the above off of the post here:
https://ipxe.org/appnote/xenserver

The new hardware we are receiving has NVMe drives and will only work with UEFI Loaded XenServer. From what I can tell the XenServer Uses grub64.efi as per this post under “Configuring your Server for TFTP Boot UEFI” https://docs.citrix.com/en-us/xenserver/7-1/install/network-boot.html

That said I have the DHCP Setup and working great, and Fog boots right into UEFI Menu, but I cannot figure out the correct Grub/Install file to use in the correct format due to my pure ignorance.

So, Anyone that has a suggestion I can try I would appreciate it much!

@george1421 That is VERY CLEAR, thank you very much. Will reference the link and see if I can get my head around it. I appreciate your time and knowledge.

Hello All - I am attempting to pass the Fog Server host IP ${fog-ip} to an answerfile / Bash Script, so I do not have to manually edit the Fog Server IP in the script of the installer each time the fog IP changes (Long story).

I tried passing as a variable using the kernel option such as at the end I put “thefogip=${fog-ip}” :
kernel http://${fog-ip}/iso/xen80/boot/xen dom0_max_vcpus=4 dom0_mem=max:4096M com1=115200,8n1 console=com1,vga thefogip=${fog-ip}

Then in my answer file (XML) I tried to reference it with :
<script stage=“filesystem-populated” type=“url”>http://$thefogip/iso/xen80/scripts/post-script.sh</script>

But the variable did not seem to populate…
I also looked at this Post, but I am likely too ignorant to follow it.
https://forums.fogproject.org/topic/11014/passing-host-variable-to-ipxe-menu/4

Thanks!

@george1421 So there is no GRUB or wim files, but based upon some looking there are some kernel.dat, kernel64.dat, and some efi files.
From their knowledge base, it is based upon a linux kernel. Thanks for your help!

Hello All - Looked at a few posts on how to boot ISO and got my Acronis to Boot great ISO using legacy PXE Boot.
I have a large number of Systems now that are only UEFI PXE by default. It would be very convienient to be able to load Acronis via FOG instead of USB/CD as I have many systems to take images and save/copy etc, where the FOG based Imaging is not practical in some situations.
Here is My Working Legacy /BIOS Boot:
initrd http://${fog-ip}/iso/acronis/AcronisBootableMedia.iso
chain memdisk iso raw || goto MENU
boot
Any ideas how I can get setup to UEFI Boot My acronis 2019?
I assume I need to copy the files from the ISO to a folder and specify some kernel params but am obviously ignorant.

Thanks in advance. If I get this working, I am happy to make a step by step with images.

@george1421 Did Option #1 and worked perfectly. Again I appreciate you responding and the effort put into this IT infrastructure tool.

@george1421 Ok your instructions from other post…WORKED FLAWLESS with the bzImage5618.
How do we get that kernel to be the “main” so I can just deploy image without having to register each NUCs MAC individually?
Can I build a PXE Menu Item that uses that special kernel?

BY THE WAY, have been trying to fix this for 2 months, and have 1000 NUCs to deploy, so you have changed my world.

@Sebastian-Roth Thank you, will take a crack at this if @george1421 option does not work. I can do it, but not the sharpest tool in the shed when going this far…

@george1421 Thank you will test this shortly for you.

I was attempting to build my own kernel but could not find the kitchen sink file referenced here: https://wiki.fogproject.org/wiki/index.php?title=Building_a_Custom_Kernel#Building_a_Custom_Kernel

The 10th GEN NUC indicates no driver found. I downloaded the Linux drivers from Intel, but needed to build custom kernel and got stuck here. Appreciate any direction given.