You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
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.
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.
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?
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).
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
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
Activity
pythops commentedon Nov 8, 2026
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 ?
0xlne commentedon Nov 8, 2026
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.
pythops commentedon Nov 8, 2026
Can not reproduce it.
I picked up
DietPi_VM-UEFI-x86_64-Trixie.qcow2and usedLocal Fileand it boots.I am on x86_64 too
pythops commentedon Nov 8, 2026
Do you more precise instructions on how to reproduce it ?
0xlne commentedon Nov 8, 2026
These are the images I chose to provide with the local file option:
https://dietpi.com/downloads/images/DietPi_NativePC-BIOS-x86_64-Forky.img.xz
https://dietpi.com/downloads/images/DietPi_NativePC-UEFI-x86_64-Forky.img.xz
I decompressed xz images, of course.
https://dietpi.com/downloads/images/DietPi_NativePC-BIOS-x86_64-Forky_Installer.iso
https://dietpi.com/downloads/images/DietPi_NativePC-UEFI-x86_64-Forky_Installer.iso
pythops commentedon Nov 8, 2026
Just tired with
DietPi_NativePC-UEFI-x86_64-Forky_Installer.isoand it workspythops commentedon Nov 8, 2026
Closing the issue
0xlne commentedon Nov 8, 2026
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.
pythops commentedon Nov 8, 2026
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.jsonpythops commentedon Nov 8, 2026
Just tried with the bios version and it works too, so really something in your setup
0xlne commentedon Nov 8, 2026
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.
pythops commentedon Nov 9, 2026
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 you0xlne commentedon Nov 9, 2026
0xlne commentedon Nov 9, 2026
On the UEFI topic, I have the OVMF firmware in the following locations:
/usr/share/ovmf/bios.bin
0xlne commentedon Nov 9, 2026
My user is also part of the qemu & kvm groups & I also tried this from root.
0xlne commentedon Nov 9, 2026
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?
pythops commentedon Nov 9, 2026
Fix is on the way. It is not about the storage. Alpine is not supported and I am fixing it now
pythops commentedon Nov 9, 2026
Try this PR
#25
0xlne commentedon Nov 9, 2026
Thanks for looking into this; I'll test tomorrow & will revert with the results.
0xlne commentedon Nov 10, 2026
Is there a debug build artifact available? I can't find it the CI actions.
pythops commentedon Nov 10, 2026
Nope, you need to build it yourself
just run
0xlne commentedon Nov 10, 2026
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.
pythops commentedon Nov 10, 2026
About the first point. You mean booting with
netboot.isoand add some disks at the start ?Do you have any scanario to reproduce it ?
0xlne commentedon Nov 10, 2026
Issue with booting (stuck in PXE/network boot; kudu doesn't move to other devices for booting)
pythops commentedon Nov 10, 2026
Got it, this only happens with netboot with x86 with Bios. Fix is in the way
0xlne commentedon Nov 10, 2026
That's right, and thanks.
pythops commentedon Nov 10, 2026
basically if you choose the interface
ideinstead ofvirtiothat 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 toidewhenver the bios is choosen with local boot file.Thanks for raisin the issue in the first place