[Bug 2104572] Re: Booting the daily noble RISC-V installer image fails

[Heinrich Schuchardt]

https://code.launchpad.net/~adrianoco/ubuntu/+source/cd-boot-images-
riscv64/+git/cd-boot-images-riscv64/+merge/483536 provides part of the
solution.

We still need to replace /EFI/boot/bootriscv64.efi by a GRUB binary
containing an ISO9660 driver (gcdriscv64.efi).

** Also affects: u-boot (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Also affects: cd-boot-images-riscv64 (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: cd-boot-images-riscv64 (Ubuntu)
    Milestone: None => ubuntu-24.04.3

** Changed in: cd-boot-images-riscv64 (Ubuntu Noble)
    Milestone: None => ubuntu-24.04.3

** Changed in: cd-boot-images-riscv64 (Ubuntu Noble)
     Assignee: (unassigned) => Adriano Cordova Fedeli (adrianoco)

** Changed in: u-boot (Ubuntu)
       Status: Confirmed => Invalid

** Changed in: u-boot (Ubuntu Noble)
       Status: New => Invalid

** Changed in: cd-boot-images-riscv64 (Ubuntu)
     Assignee: (unassigned) => Adriano Cordova Fedeli (adrianoco)

** Changed in: u-boot (Ubuntu)
     Assignee: Adriano Cordova Fedeli (adrianoco) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to u-boot in Ubuntu.
https://bugs.launchpad.net/bugs/2104572

Title:
  Booting the daily noble RISC-V installer image fails

Status in cd-boot-images-riscv64 package in Ubuntu:
  New
Status in u-boot package in Ubuntu:
  Invalid
Status in cd-boot-images-riscv64 source package in Noble:
  New
Status in u-boot source package in Noble:
  Invalid

Bug description:
  I have downloaded
  https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/plucky-live-server-riscv64.iso
  https://cdimage.ubuntu.com/ubuntu-server/noble/daily-live/current/noble-live-server-riscv64.iso
  and tried to boot these on a Plucky system.

  Booting the noble image with

  qemu-system-riscv64 -machine virt -m 4G -smp cpus=2 -nographic \
      -kernel /usr/lib/u-boot/qemu-riscv64_smode/u-boot.bin \
      -netdev user,id=net0 \
      -device virtio-net-device,netdev=net0 \
      -drive file=noble-live-server-riscv64.iso,format=raw,if=virtio \
      -drive file=disk,format=raw,if=virtio \
      -device virtio-rng-pc

  ends up in the GRUB rescue console:

  grub> ls $root
  error: invalid file name `hd0,gpt2'.
  grub> ls ($root)/
  efi/ dtb/ ubootefi.var
  grub>

  Same problem with EDK II using

  qemu-system-riscv64 -machine virt -m 4G -smp cpus=2 -nographic \
      -drive if=pflash,format=raw,unit=0,file=/usr/share/qemu-efi-riscv64/RISCV_VIRT_CODE.fd,readonly=on \
      -drive if=pflash,format=raw,unit=1,file=RISCV_VIRT_VARS.fd \
      -netdev user,id=net0 \
      -device virtio-net-device,netdev=net0 \
      -drive file=disk,format=raw,if=virtio \
      -device virtio-blk,drive=ISO,bootindex=1 \
      -drive file=noble-live-server-riscv64.iso,if=none,id=ISO \
      -device virtio-rng-pci

  I don't experience any problem with the Plucky image.

  When I emulate a CD-ROM it works

  qemu-system-riscv64 -machine virt -m 4G -smp cpus=2 -nographic \
      -drive if=pflash,format=raw,unit=0,file=/usr/share/qemu-efi-riscv64/RISCV_VIRT_CODE.fd,readonly=on \
      -drive if=pflash,format=raw,unit=1,file=RISCV_VIRT_VARS.fd \
      -netdev user,id=net0 \
      -device virtio-net-device,netdev=net0 \
      -drive file=disk,format=raw,if=virtio \
      -device driver=virtio-scsi-pci,id=scsi0 \
      -drive if=none,file=noble-live-server-riscv64.iso,format=raw,readonly=on,id=CDROM \
      -device driver=scsi-cd,bus=scsi0.0,drive=CDROM,bootindex=1 \
      -device virtio-rng-pci

  So it seems our current Noble ISO is not properly set up to be used a
  disk image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cd-boot-images-riscv64/+bug/2104572/+subscriptions