# X86-64 Making a live image ( Scarthgap ) **URL:** \ **Category:** General Discussions\ **Tags:** yocto, amd64\ **Created:** [September 2, 2025, 9:28pm UTC](https://hub.mender.io/t/x86-64-making-a-live-image-scarthgap/7985 "2025-09-02T21:28:09Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![yassine-cherni](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/yassine-cherni/32/2559_2.png) [@yassine-cherni](https://hub.mender.io/u/yassine-cherni)\ **Post date:** [September 2, 2025, 9:28pm UTC](https://hub.mender.io/t/x86-64-making-a-live-image-scarthgap/7985/1 "2025-09-02T21:28:10Z")
Hello, In order to make the image live bootable into the USB Driver ( following this blog [Self-installing Yocto Image from a USB drive – The Good Penguin](https://www.thegoodpenguin.co.uk/blog/self-installing-yocto-image-from-a-usb-drive) ) for X86-64 i get some issues in the build, ( i followed the kickstart guide to specify the partition with EFI [8 OpenEmbedded Kickstart (.wks) Reference — The Yocto Project ® 5.0.11 documentation](https://docs.yoctoproject.org/5.0.11/ref-manual/kickstart.html) ) am using grub-efi and [common.conf](https://git.yoctoproject.org/meta-amd/tree/meta-amd-bsp/conf/machine/common.conf?h=scarthgap) In the image-mender.bb > **image-mender.bb** > > # WIC file for UEFI boot > > WKS\_FILE = “image-installer.wks.in” > WKS\_SEARCH\_PATH = “${LAYERDIR}/recipes-bsp/wic” > > # Initramfs > > INITRD\_IMAGE\_LIVE=“core-image-minimal-initramfs” > > # EFI provider > > EFI\_PROVIDER = “grub-efi” > > IMAGE\_EFI\_BOOT\_FILES:append = " > ${@bb.utils.contains(‘EFI\_PROVIDER’, ‘grub-efi’, ‘grub-efi-bootx64.efi;EFI/BOOT/bootx64.efi’, ‘’, d)} > ${@bb.utils.contains(‘EFI\_PROVIDER’, ‘grub-efi’, ‘${IMAGE\_ROOTFS}/boot/EFI/BOOT/grub.cfg;EFI/BOOT/grub.cfg’, ‘’, d)} > ${@bb.utils.contains(‘EFI\_PROVIDER’, ‘systemd-boot’, ‘systemd-bootx64.efi;EFI/BOOT/bootx64.efi’, ‘’, d)} > ${@bb.utils.contains(‘EFI\_PROVIDER’, ‘systemd-boot’, '${IMAGE\_ROOTFS}/boot/loader/loader.conf;loader/loader.conf ', ‘’, d)} > ${@bb.utils.contains(‘EFI\_PROVIDER’, ‘systemd-boot’, ‘${IMAGE\_ROOTFS}/boot/loader/entries/boot.conf;loader/entries/boot.conf’, ‘’, d)} > startup.nsh > " > > do\_image\_wic[depends] += “${INITRD\_IMAGE\_LIVE}:do\_image\_complete” > do\_rootfs[depends] += “virtual/kernel:do\_deploy” > do\_image\_wic[depends] += “grub-efi:do\_deploy” > do\_image\_wic[depends] += “grub-efi:do\_populate\_sysroot” and i keep getting this error : ERROR: Task do\_image\_wic in /home/yassine/yocto-amd/build/../layers/meta-morefine/recipes-core/images/morefine-ros2-image.bb depends upon non-existent task do\_bootimg in /home/yassine/yocto-amd/build/../layers/meta-morefine/recipes-core/images/morefine-ros2-image.bb ERROR: Command execution failed: 1 ---
**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\ **Post date:** [September 4, 2025, 9:22am UTC](https://hub.mender.io/t/x86-64-making-a-live-image-scarthgap/7985/2 "2025-09-04T09:22:35Z")
Hi @yassine-cherni, Thanks a lot for reaching out. The topic sounds quite like a duplicate from [Cannot add Mender to yocto intel-skylake-64 default image with installer](https://hub.mender.io/t/cannot-add-mender-to-yocto-intel-skylake-64-default-image-with-installer/7984), so maybe you can join forces with @hackenstein? Possibly I can also show an example `multiconfig` build next week which you can use as a base. Greetz, Josef ---
**Author:** ![yassine-cherni](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/yassine-cherni/32/2559_2.png) [@yassine-cherni](https://hub.mender.io/u/yassine-cherni)\ **Post date:** [September 4, 2025, 1:30pm UTC](https://hub.mender.io/t/x86-64-making-a-live-image-scarthgap/7985/3 "2025-09-04T13:30:22Z")
For now it compile and runs on qemu by adding :` # Boot files IMAGE\_BOOT\_FILES:append = " ${KERNEL\_IMAGETYPE} grub-efi-bootx64.efi;EFI/BOOT/bootx64.efi grub.cfg;EFI/BOOT/grub.cfg " # Auto-boot GRUB GRUB\_TIMEOUT = “0” # Build dependencies #do\_image\_wic[depends] += “${INITRD\_IMAGE\_LIVE}:do\_image\_complete” do\_rootfs[depends] += “virtual/kernel:do\_deploy” do\_image\_wic[depends] += “grub-efi:do\_deploy” do\_image\_wic[depends] += “grub-efi:do\_populate\_sysroot” ` ( Still dindn’t test it in the real harware but am thinking for the “initramfs” should i add it or the kernel will find the rootfs without it ) ---
**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\ **Post date:** [September 4, 2025, 2:29pm UTC](https://hub.mender.io/t/x86-64-making-a-live-image-scarthgap/7985/4 "2025-09-04T14:29:16Z")
Hi @yassine-cherni, Thanks for following up! Just for clarification, what does “runs on qemu” mean? Does the resulting ISO boot and successfully install? Or what functionality is known to work, what is known to fail? Greetz, Josef ---
**Author:** ![yassine-cherni](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/yassine-cherni/32/2559_2.png) [@yassine-cherni](https://hub.mender.io/u/yassine-cherni)\ **Post date:** [September 4, 2025, 3:19pm UTC](https://hub.mender.io/t/x86-64-making-a-live-image-scarthgap/7985/5 "2025-09-04T15:19:20Z")
By “runs on [QEMU](https://www.qemu.org),” I mean that with the current modifications to `IMAGE_BOOT_FILES` and GRUB (`grub-efi-bootx64.efi` + `grub.cfg`) the `.wic` image **boots in QEMU** , GRUB appears, and the kernel starts. I haven’t yet tested the full USB → NVMe install flow on real hardware. Regarding the initramfs: I **have included** `INITRD_IMAGE_LIVE = "core-image-minimal-initramfs"` in the recipe, so the kernel boots with the installer initramfs, which contains `init-install-efi.sh` and the tools needed to copy `rootfs.img` to the target NVMe. My current question is mainly about confirming the **installer workflow** on real hardware whether this setup will correctly wipe the NVMe and install the Yocto OS. At this stage, I’m mostly validating the USB boot and installer configuration before testing on the actual device. Thanks!