Stuck at "SeaBIOS booting from hard disk" – Azure Windows Image Won’t Boot in OpenNebula

Product Support
1
  1. Has anyone successfully booted a Windows Azure .vhd image in OpenNebula?
  • If so, what format and settings were used?
  1. Is there a preferred method for converting Azure .vhd images to a compatible format for OpenNebula?
  • Should I be using qemu-img with specific options (like -o compat=0.10)?
  1. What’s the recommended disk bus type and NIC model for Windows VMs imported from Azure?
  • Is virtio-scsi or ide more stable for booting?
  1. Should I inject VirtIO drivers into the image manually before importing it into OpenNebula?
  • Any best practices for slipstreaming VirtIO drivers into Windows images?
  1. Is there any specific setting in the template (e.g., OS Boot type, disk target, hypervisor features) that helps with booting Azure-based Windows images?
  2. Could UEFI/OVMF be required for the image to boot properly?
  • If so, how do I enable UEFI/OVMF in OpenNebula?
  1. Is there any way to attach the image to a rescue ISO to troubleshoot inside the VM (like attaching a Windows ISO or recovery disk)?
  2. Does OpenNebula support secure boot or EFI partitions used in Azure-prepared images, or does it require conversion/migration to BIOS/MBR?

:white_check_mark: Things I’ve Already Tried:

  • Converted .vhd to .qcow2 and .raw using qemu-img.
  • Tried disk bus types: virtio, ide, scsi.
  • Enabled and disabled ACPI and APIC in the template.
  • Uploaded VirtIO driver ISO and attached it to the VM.
  • Switched between BIOS and attempted UEFI (though unclear how to enable properly).
  • Changed OS Boot type and OS attribute in the template (e.g., windows, windows10, etc.).