Skip to content

[Q] No bootable device? #23

Closed
Closed

Description

@0xlne

I'd appreciate guidance on how to boot ISOs or existing disk images.
When creating a VM in advanced mode, I tried providing either an installation ISO, or a qcow2 disk image (local file).
In both cases, the VM boots to BIOS but cannot find a bootable device.
Am I missing something?

Activity

  1. pythops commented on Nov 8, 2026

    @pythops
    Owner

    which ISO or qcow2 file are you providing ? I want to know so I can try to reproduce it locally.
    what is your Arch and what Arch are you targeting ?

  2. 0xlne commented on Nov 8, 2026

    @0xlne
    Author

    I tried a bunch of isos & imgs.
    An example is DietPi from here: https://dietpi.com/downloads/images
    Tried both UEFI & BIOS, NativePC builds. These run fine in other qemu frontends or directly through qemu.
    Host & Target arch are both x86_64.
    The host system is Alpine Linux - I downloaded the kudu x86_64 musl release from github.

  3. pythops commented on Nov 8, 2026

    @pythops
    Owner

    Can not reproduce it.
    I picked up DietPi_VM-UEFI-x86_64-Trixie.qcow2 and used Local File and it boots.
    I am on x86_64 too

  4. pythops commented on Nov 8, 2026

    @pythops
    Owner

    Do you more precise instructions on how to reproduce it ?

  5. pythops commented on Nov 8, 2026

    @pythops
    Owner

    Just tired with DietPi_NativePC-UEFI-x86_64-Forky_Installer.iso and it works

    Image
  6. pythops commented on Nov 8, 2026

    @pythops
    Owner

    Closing the issue

  7. 0xlne commented on Nov 8, 2026

    @0xlne
    Author

    Just tried with both the Legacy BIOS & UEFI versions:
    n.b. where does kudu search for the ovmf file? I only get a choice of BIOS in the hardware/firmware section.

    Image
  8. pythops commented on Nov 8, 2026

    @pythops
    Owner

    You got only the choice of BIOS because the firmware package is not installed in your os. Check the readme for the package to install for your OS.

    Can you paste here the content of the file ~/.local/share/kudu/vms/<VM ID>/vm.json

  9. pythops commented on Nov 8, 2026

    @pythops
    Owner

    Just tried with the bios version and it works too, so really something in your setup

  10. 0xlne commented on Nov 8, 2026

    @0xlne
    Author

    Thx for the responses; I'll revert back tomorrow.
    n.b. I do have the OVMF firmware installed but the filename or location might not be recognized by kudu. Or it's an Alpine Linux issue.

  11. pythops commented on Nov 9, 2026

    @pythops
    Owner

    can you paste here the content of the file I asked, also the content of /etc/os-release ? I think I know why it does not work for you

  12. 0xlne commented on Nov 9, 2026

    @0xlne
    Author

    can you paste here the content of the file I asked, also the content of /etc/os-release ? I think I know why it does not work for you

    **cat .local/share/kudu/vms/302f9e68-4969-46a5-8b50-0e2ca6567cd4/vm.json** 
    {
      "id": "302f9e68-4969-46a5-8b50-0e2ca6567cd4",
      "name": "DietPi BIOS",
      "boot_option": "LocalFile",
      "firmware": "Bios",
      "arch": "X86_64",
      "vcpu": 4,
      "memory": 4096,
      "drives": [
        {
          "path": "/home/a/.local/share/kudu/vms/302f9e68-4969-46a5-8b50-0e2ca6567cd4/disk_0",
          "interface": "Virtio",
          "media": "Disk",
          "format": "Qcow2",
          "read_only": false,
          "unit": null,
          "size": 5368709120
        },
        {
          "path": "/tmp/DietPi_NativePC-BIOS-x86_64-Forky_Installer.iso",
          "interface": "Virtio",
          "media": "CdRom",
          "format": "Raw",
          "read_only": true,
          "unit": null,
          "size": 905969664
        }
      ],
      "networks": [
        {
          "id": "b96cc4ff",
          "backend": "Slirp",
          "nic": "Virtio",
          "mac": null,
          "port_mappings": []
        }
      ],
      "remote_access": {
        "Vnc": {
          "host": "127.0.0.1",
          "password": null
        }
      },
      "fs": [],
      "graphics": {
        "device": {
          "Std": {
            "vgamem": 16
          }
        },
        "display": "None"
      }
    
    **# cat /etc/os-release** 
    NAME="Alpine Linux"
    ID=alpine
    VERSION_ID=3.25.0_alpha20260805
    PRETTY_NAME="Alpine Linux edge"
    HOME_URL="https://alpinelinux.org/"
    BUG_REPORT_URL="https://gitlab.alpinelinux.org/alpine/aports/-/issues"
    
  13. 0xlne commented on Nov 9, 2026

    @0xlne
    Author

    On the UEFI topic, I have the OVMF firmware in the following locations:
    /usr/share/ovmf/bios.bin

    /usr/share/OVMF/
    -rw-r--r-- 1 root root 4194304 May 28 09:19 OVMF.fd
    -rw-r--r-- 1 root root 3653632 May 28 09:19 OVMF_CODE.fd
    -rw-r--r-- 1 root root  540672 May 28 09:19 OVMF_VARS.fd
    
  14. 0xlne commented on Nov 9, 2026

    @0xlne
    Author

    My user is also part of the qemu & kvm groups & I also tried this from root.

  15. 0xlne commented on Nov 9, 2026

    @0xlne
    Author

    I think I found the problem:
    The VM boots when creating it without disk storage.
    Which leads me to believe that it's an issue with kudu marking the boot device.

    When adding storage at the time of creation of the VM, it's positioned on top of the CD or whatever boot device.
    Kudu sets only that device as the boot device. In the case of network, it expects PXE to kick off.
    However, when adding a storage AFTER the initial creation of the VM via editing the entry, that storage is positioned below the CD, which allows kudu to boot the iso.

    Is there a way to manually mark the boot device in kudu? Or to treat all storage devices as potentially bootable in a chain?

  16. pythops commented on Nov 9, 2026

    @pythops
    Owner

    Fix is on the way. It is not about the storage. Alpine is not supported and I am fixing it now

  17. pythops commented on Nov 9, 2026

    @pythops
    Owner

    Try this PR
    #25

  18. reopened this on Nov 9, 2026
  19. 0xlne commented on Nov 9, 2026

    @0xlne
    Author

    Thanks for looking into this; I'll test tomorrow & will revert with the results.

  20. 0xlne commented on Nov 10, 2026

    @0xlne
    Author

    Is there a debug build artifact available? I can't find it the CI actions.

  21. pythops commented on Nov 10, 2026

    @pythops
    Owner

    Nope, you need to build it yourself

    just run

    cargo run
    
  22. 0xlne commented on Nov 10, 2026

    @0xlne
    Author

    1: kudu still stalls on booting from network when configuring additional storage during the initial provisioning of the VM
    Removing the storage or adding storage only after the initial provisioning works (this means that the cdrom device becomes the first bootable device).

    2: UEFI booting is now present & works - thanks.

  23. pythops commented on Nov 10, 2026

    @pythops
    Owner

    About the first point. You mean booting with netboot.iso and add some disks at the start ?
    Do you have any scanario to reproduce it ?

  24. 0xlne commented on Nov 10, 2026

    @0xlne
    Author

    Issue with booting (stuck in PXE/network boot; kudu doesn't move to other devices for booting)

    1: create a new VM
    2: choose "Advanced Options"
    3: Type a random vm name
    4: In "boot" - select "Local File" - provide any bootable Linux ISO in the "File Path"
    5: In "Hardware", choose the right UEFI or BIOS type of bootable media
    6: Storage - create additional storage. Default options used (qcow2/virtio) - I just provide an arbitrary size, like 5Gb
    7: create the VM```
    
    
    **Properly booting**
    Exclude step #6, or move step #6 after creating the VM
    
  25. pythops commented on Nov 10, 2026

    @pythops
    Owner

    Got it, this only happens with netboot with x86 with Bios. Fix is in the way

  26. 0xlne commented on Nov 10, 2026

    @0xlne
    Author

    That's right, and thanks.

  27. pythops commented on Nov 10, 2026

    @pythops
    Owner

    basically if you choose the interface ide instead of virtio that should work, that's because the legacy bios does not understand virtio. The issue here is that the interface is choosen before the firmware option. I will push a fix to override to ide whenver the bios is choosen with local boot file.
    Thanks for raisin the issue in the first place

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions