+- iPXE discussion forum (https://forum.ipxe.org)
+-- Forum: iPXE user forums (/forumdisplay.php?fid=1)
+--- Forum: General (/forumdisplay.php?fid=2)
+--- Thread: specifying kickstart with sanboot (/showthread.php?tid=18624)
specifying kickstart with sanboot - sumtyagi - 2019-07-09 06:45
Hi All,
I am new to ipxe. I was trying to see if I can boot from an ISO without having to mount iso and refer to kernel and initramd. Tried memdisk and initramd but it was showing no space left on device (may be due to 3.5 gb size of iso)
I found sanboot option where I can specify the iso file directly (http server), and its working now. But I am not sure how to add kickstart file now to my installation. Is there any way I can pass ks="" somehow in sanboot? I do not want to edit the original iso although.
Thank you for your assistance.
Best Regards,
Sumit Tyagi
RE: specifying kickstart with sanboot - NiKiZe - 2019-07-09 13:59
As described in FAQ - memdisk does not really work well,
sanboot with http fals under the same category, it dosn't work.
You are refering to ks ... which is a kernel argument, which you then would have to inject into isolinux/grub/whatever boot loader the iso is using.
This is not going to work.
The correct way to handle this is to have extracted kernel, initramfs and possibly squash.
Instead of using bloated and invalid (for networkbooting purpuses) ISOs, the distributions should provide these files on their own, without the need to extract the isos.
RE: specifying kickstart with sanboot - sumtyagi - 2019-07-10 05:10
(2019-07-09 13:59)NiKiZe Wrote: As described in FAQ - memdisk does not really work well,
sanboot with http fals under the same category, it dosn't work.
You are refering to ks ... which is a kernel argument, which you then would have to inject into isolinux/grub/whatever boot loader the iso is using.
This is not going to work.
The correct way to handle this is to have extracted kernel, initramfs and possibly squash.
Instead of using bloated and invalid (for networkbooting purpuses) ISOs, the distributions should provide these files on their own, without the need to extract the isos.
Hi NikiZe,
Thanks for your reply. I am actually getting the boot menu for iso with sanboot with http. But it is failing in installation with Error "could not boot. /dev/root does not exist".
For initrd and chain commands, I am getting No Space left on device error (memdisk also didn't helped there). I am not sure what is the option left for me to boot from ISO (without extracting).
Best Regards,
Sumit Tyagi
RE: specifying kickstart with sanboot - NiKiZe - 2019-07-13 14:47
(2019-07-10 05:10)sumtyagi Wrote: Thanks for your reply. I am actually getting the boot menu for iso with sanboot with http. But it is failing in installation with Error "could not boot. /dev/root does not exist".
You get this because there is no iso available when the system (kernel) starts, This has been explained so many times before ...
(2019-07-09 13:59)NiKiZe Wrote: As described in FAQ - memdisk does not really work well,
sanboot with http fals under the same category, it dosn't work.
And I continue with...
(2019-07-09 13:59)NiKiZe Wrote: The correct way to handle this is to have extracted kernel, initramfs and possibly squash.
Instead of using bloated and invalid (for networkbooting purpuses) ISOs, the distributions should provide these files on their own, without the need to extract the isos.
There is no theoretical way that I can think of where it will work booting the ISO (unless the orignal ISO itself has a lot of magic in it, or you have some kind of hardware that supports this client side)
Normal PXE or iPXE will not work on it's own with the ISO without extracting it.