Why won't this custom ISO boot into Fedora?
by sreyan32 from LinuxQuestions.org on (#51TKC)
I am unable to boot the generated Fedora Live ISO using the following command:
Code:genisoimage -U -r -v -T -J -joliet-long -V "Fedora-WS-Live-31-1-9" -volset "Fedora-WS-Live-31-1-9" -A "CDLABEL=Fedora-WS-Live-31-1-9" -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -eltorito-alt-boot -e images/efiboot.img -no-emul-boot -o ../Fedora_Custom.iso .This the directory structure of my directory where I have the uncompressed ISO:
Code:[sreyan@localhost Fedora_ISO]$ tree .
.
a"a"a" anaconda-ks.cfg
a"a"a" EFI
a" a""a"a" BOOT
a" a"a"a" BOOT.conf
a" a"a"a" BOOTIA32.EFI
a" a"a"a" BOOTX64.EFI
a" a"a"a" fonts
a" a" a""a"a" unicode.pf2
a" a"a"a" grub.cfg
a" a"a"a" grubia32.efi
a" a"a"a" grubx64.efi
a" a"a"a" mmia32.efi
a" a""a"a" mmx64.efi
a"a"a" images
a" a"a"a" efiboot.img
a" a"a"a" macboot.img
a" a""a"a" pxeboot
a" a"a"a" initrd.img
a" a""a"a" vmlinuz
a"a"a" isolinux
a" a"a"a" boot.cat
a" a"a"a" boot.msg
a" a"a"a" grub.conf
a" a"a"a" initrd.img
a" a"a"a" isolinux.bin
a" a"a"a" isolinux.cfg
a" a"a"a" ldlinux.c32
a" a"a"a" libcom32.c32
a" a"a"a" libutil.c32
a" a"a"a" memtest
a" a"a"a" splash.png
a" a"a"a" vesamenu.c32
a" a""a"a" vmlinuz
a""a"a" LiveOS
a""a"a" squashfs.img
7 directories, 28 filesThis has virtually no difference from the actual ISO image:
Code:[sreyan@localhost Fedora-WS-Live-31-1-9]$ tree .
.
a"a"a" EFI
a" a""a"a" BOOT
a" a"a"a" BOOT.conf
a" a"a"a" BOOTIA32.EFI
a" a"a"a" BOOTX64.EFI
a" a"a"a" fonts
a" a" a""a"a" unicode.pf2
a" a"a"a" grub.cfg
a" a"a"a" grubia32.efi
a" a"a"a" grubx64.efi
a" a"a"a" mmia32.efi
a" a""a"a" mmx64.efi
a"a"a" images
a" a"a"a" efiboot.img
a" a"a"a" macboot.img
a" a""a"a" pxeboot
a" a"a"a" initrd.img
a" a""a"a" vmlinuz
a"a"a" isolinux
a" a"a"a" boot.cat
a" a"a"a" boot.msg
a" a"a"a" grub.conf
a" a"a"a" initrd.img
a" a"a"a" isolinux.bin
a" a"a"a" isolinux.cfg
a" a"a"a" ldlinux.c32
a" a"a"a" libcom32.c32
a" a"a"a" libutil.c32
a" a"a"a" memtest
a" a"a"a" splash.png
a" a"a"a" vesamenu.c32
a" a""a"a" vmlinuz
a""a"a" LiveOS
a""a"a" squashfs.img
7 directories, 27 filesThe only difference is the anaconda-ks.cfg which I am not even using. This is the output of [ICODE]isolinux.cfg[/ICODE] from my custom ISO:
Code:default vesamenu.c32
timeout 600
display boot.msg
# Clear the screen when exiting the menu, instead of leaving the menu displayed.
# For vesamenu, this means the graphical background is still displayed without
# the menu itself for as long as the screen remains in graphics mode.
menu clear
menu background splash.png
menu title Fedora-Workstation-Live 31
menu vshift 8
menu rows 18
menu margin 8
#menu hidden
menu helpmsgrow 15
menu tabmsgrow 13
# Border Area
menu color border * #00000000 #00000000 none
# Selected item
menu color sel 0 #ffffffff #00000000 none
# Title bar
menu color title 0 #ff7ba3d0 #00000000 none
# Press [Tab] message
menu color tabmsg 0 #ff3a6496 #00000000 none
# Unselected menu item
menu color unsel 0 #84b8ffff #00000000 none
# Selected hotkey
menu color hotsel 0 #84b8ffff #00000000 none
# Unselected hotkey
menu color hotkey 0 #ffffffff #00000000 none
# Help text
menu color help 0 #ffffffff #00000000 none
# A scrollbar of some type? Not sure.
menu color scrollbar 0 #ffffffff #ff355594 none
# Timeout msg
menu color timeout 0 #ffffffff #00000000 none
menu color timeout_msg 0 #ffffffff #00000000 none
# Command prompt text
menu color cmdmark 0 #84b8ffff #00000000 none
menu color cmdline 0 #ffffffff #00000000 none
# Do not display the actual menu unless the user presses a key. All that is displayed is a timeout message.
menu tabmsg Press Tab for full configuration options on menu items.
menu separator # insert an empty line
menu separator # insert an empty line
label linux
menu label ^Start Fedora-Workstation-Live 31
kernel vmlinuz
append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-31-1-9 rd.live.image quiet
label check
menu label Test this ^media & start Fedora-Workstation-Live 31
menu default
kernel vmlinuz
append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-31-1-9 rd.live.image rd.live.check quiet
menu separator # insert an empty line
# utilities submenu
menu begin ^Troubleshooting
menu title Troubleshooting
label vesa
menu indent count 5
menu label Start Fedora-Workstation-Live 31 in ^basic graphics mode
text help
Try this option out if you're having trouble starting
Fedora-Workstation-Live 31.
endtext
kernel vmlinuz
append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-31-1-9 rd.live.image nomodeset quiet
label memtest
menu label Run a ^memory test
text help
If your system is having issues, a problem with your
system's memory may be the cause. Use this utility to
see if the memory is working correctly.
endtext
kernel memtest
menu separator # insert an empty line
label local
menu label Boot from ^local drive
localboot 0xffff
menu separator # insert an empty line
menu separator # insert an empty line
label returntomain
menu label Return to ^main menu
menu exit
menu endThere is absolutely no difference between the actual ISO and my custom ISO.
Yet the actual ISO boots into the live environment and mine does not. Mine, is just stuck at the boot menu.
I have verified that the kernel command lines are also same. Here are the screenshots:
Here is mine:
Here is the actual:
There is no difference.
Then why does mine fail ?
I am trying to boot in Oracle Virtualbox.
Let me know if any other info is required.


Code:genisoimage -U -r -v -T -J -joliet-long -V "Fedora-WS-Live-31-1-9" -volset "Fedora-WS-Live-31-1-9" -A "CDLABEL=Fedora-WS-Live-31-1-9" -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -eltorito-alt-boot -e images/efiboot.img -no-emul-boot -o ../Fedora_Custom.iso .This the directory structure of my directory where I have the uncompressed ISO:
Code:[sreyan@localhost Fedora_ISO]$ tree .
.
a"a"a" anaconda-ks.cfg
a"a"a" EFI
a" a""a"a" BOOT
a" a"a"a" BOOT.conf
a" a"a"a" BOOTIA32.EFI
a" a"a"a" BOOTX64.EFI
a" a"a"a" fonts
a" a" a""a"a" unicode.pf2
a" a"a"a" grub.cfg
a" a"a"a" grubia32.efi
a" a"a"a" grubx64.efi
a" a"a"a" mmia32.efi
a" a""a"a" mmx64.efi
a"a"a" images
a" a"a"a" efiboot.img
a" a"a"a" macboot.img
a" a""a"a" pxeboot
a" a"a"a" initrd.img
a" a""a"a" vmlinuz
a"a"a" isolinux
a" a"a"a" boot.cat
a" a"a"a" boot.msg
a" a"a"a" grub.conf
a" a"a"a" initrd.img
a" a"a"a" isolinux.bin
a" a"a"a" isolinux.cfg
a" a"a"a" ldlinux.c32
a" a"a"a" libcom32.c32
a" a"a"a" libutil.c32
a" a"a"a" memtest
a" a"a"a" splash.png
a" a"a"a" vesamenu.c32
a" a""a"a" vmlinuz
a""a"a" LiveOS
a""a"a" squashfs.img
7 directories, 28 filesThis has virtually no difference from the actual ISO image:
Code:[sreyan@localhost Fedora-WS-Live-31-1-9]$ tree .
.
a"a"a" EFI
a" a""a"a" BOOT
a" a"a"a" BOOT.conf
a" a"a"a" BOOTIA32.EFI
a" a"a"a" BOOTX64.EFI
a" a"a"a" fonts
a" a" a""a"a" unicode.pf2
a" a"a"a" grub.cfg
a" a"a"a" grubia32.efi
a" a"a"a" grubx64.efi
a" a"a"a" mmia32.efi
a" a""a"a" mmx64.efi
a"a"a" images
a" a"a"a" efiboot.img
a" a"a"a" macboot.img
a" a""a"a" pxeboot
a" a"a"a" initrd.img
a" a""a"a" vmlinuz
a"a"a" isolinux
a" a"a"a" boot.cat
a" a"a"a" boot.msg
a" a"a"a" grub.conf
a" a"a"a" initrd.img
a" a"a"a" isolinux.bin
a" a"a"a" isolinux.cfg
a" a"a"a" ldlinux.c32
a" a"a"a" libcom32.c32
a" a"a"a" libutil.c32
a" a"a"a" memtest
a" a"a"a" splash.png
a" a"a"a" vesamenu.c32
a" a""a"a" vmlinuz
a""a"a" LiveOS
a""a"a" squashfs.img
7 directories, 27 filesThe only difference is the anaconda-ks.cfg which I am not even using. This is the output of [ICODE]isolinux.cfg[/ICODE] from my custom ISO:
Code:default vesamenu.c32
timeout 600
display boot.msg
# Clear the screen when exiting the menu, instead of leaving the menu displayed.
# For vesamenu, this means the graphical background is still displayed without
# the menu itself for as long as the screen remains in graphics mode.
menu clear
menu background splash.png
menu title Fedora-Workstation-Live 31
menu vshift 8
menu rows 18
menu margin 8
#menu hidden
menu helpmsgrow 15
menu tabmsgrow 13
# Border Area
menu color border * #00000000 #00000000 none
# Selected item
menu color sel 0 #ffffffff #00000000 none
# Title bar
menu color title 0 #ff7ba3d0 #00000000 none
# Press [Tab] message
menu color tabmsg 0 #ff3a6496 #00000000 none
# Unselected menu item
menu color unsel 0 #84b8ffff #00000000 none
# Selected hotkey
menu color hotsel 0 #84b8ffff #00000000 none
# Unselected hotkey
menu color hotkey 0 #ffffffff #00000000 none
# Help text
menu color help 0 #ffffffff #00000000 none
# A scrollbar of some type? Not sure.
menu color scrollbar 0 #ffffffff #ff355594 none
# Timeout msg
menu color timeout 0 #ffffffff #00000000 none
menu color timeout_msg 0 #ffffffff #00000000 none
# Command prompt text
menu color cmdmark 0 #84b8ffff #00000000 none
menu color cmdline 0 #ffffffff #00000000 none
# Do not display the actual menu unless the user presses a key. All that is displayed is a timeout message.
menu tabmsg Press Tab for full configuration options on menu items.
menu separator # insert an empty line
menu separator # insert an empty line
label linux
menu label ^Start Fedora-Workstation-Live 31
kernel vmlinuz
append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-31-1-9 rd.live.image quiet
label check
menu label Test this ^media & start Fedora-Workstation-Live 31
menu default
kernel vmlinuz
append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-31-1-9 rd.live.image rd.live.check quiet
menu separator # insert an empty line
# utilities submenu
menu begin ^Troubleshooting
menu title Troubleshooting
label vesa
menu indent count 5
menu label Start Fedora-Workstation-Live 31 in ^basic graphics mode
text help
Try this option out if you're having trouble starting
Fedora-Workstation-Live 31.
endtext
kernel vmlinuz
append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-31-1-9 rd.live.image nomodeset quiet
label memtest
menu label Run a ^memory test
text help
If your system is having issues, a problem with your
system's memory may be the cause. Use this utility to
see if the memory is working correctly.
endtext
kernel memtest
menu separator # insert an empty line
label local
menu label Boot from ^local drive
localboot 0xffff
menu separator # insert an empty line
menu separator # insert an empty line
label returntomain
menu label Return to ^main menu
menu exit
menu endThere is absolutely no difference between the actual ISO and my custom ISO.
Yet the actual ISO boots into the live environment and mine does not. Mine, is just stuck at the boot menu.
I have verified that the kernel command lines are also same. Here are the screenshots:
Here is mine:
Here is the actual:
There is no difference.
Then why does mine fail ?
I am trying to boot in Oracle Virtualbox.
Let me know if any other info is required.