Project

General

Profile

Actions

action #129172

closed

PXEBOOT doesnt set bootindex on aarch64

Added by ybonatakis 11 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2023-05-12
Due date:
% Done:

0%

Estimated time:

Description

Digging into the qemu backend seems that the bits to boot a machine (aarch4) from network is missing.

the os-autoinst output looks like that

/usr/bin/qemu-system-aarch64 -device virtio-gpu-pci,edid=on,xres=1024,yres=768 -chardev ringbuf,id=serial0,logfile=serial0,logappend=on -serial chardev:serial0 -audiodev none,id=snd0 -device intel-hda -device hda-output,audiodev=snd0 -m 4096 -machine virt,usb=off,gic-version=3,its=off -cpu host -netdev tap,id=qanet0,ifname=tap2,script=no,downscript=no -device virtio-net,netdev=qanet0,mac=52:54:00:12:05:02 -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 -device nec-usb-xhci -device usb-tablet -device usb-kbd -smp 1 -enable-kvm -no-shutdown -vnc :93,share=force-shared -device virtio-serial -chardev pipe,id=virtio_console,path=virtio_console,logfile=virtio_console.log,logappend=on -device virtconsole,chardev=virtio_console,name=org.openqa.console.virtio_console -chardev pipe,id=virtio_console_user,path=virtio_console_user,logfile=virtio_console_user.log,logappend=on -device virtconsole,chardev=virtio_console_user,name=org.openqa.console.virtio_console_user -chardev socket,path=qmp_socket,server=on,wait=off,id=qmp_socket,logfile=qmp_socket.log,logappend=on -qmp chardev:qmp_socket -S -device virtio-scsi-pci,id=scsi0 -blockdev driver=file,node-name=hd0-file,filename=/var/lib/openqa/pool/3/raid/hd0,cache.no-flush=on -blockdev driver=qcow2,node-name=hd0,file=hd0-file,cache.no-flush=on,discard=unmap -device virtio-blk-device,id=hd0-device,drive=hd0,serial=hd0 -blockdev driver=file,node-name=cd0-overlay0-file,filename=/var/lib/openqa/pool/3/raid/cd0-overlay0,cache.no-flush=on -blockdev driver=qcow2,node-name=cd0-overlay0,file=cd0-overlay0-file,cache.no-flush=on,discard=unmap -device scsi-cd,id=cd0-device,drive=cd0-overlay0,serial=cd0 -drive id=pflash-code-overlay0,if=pflash,file=/var/lib/openqa/pool/3/raid/pflash-code-overlay0,unit=0,readonly=on -drive id=pflash-vars-overlay0,if=pflash,file=/var/lib/openqa/pool/3/raid/pflash-vars-overlay0,unit=1

where bootindex is missing

Actions #1

Updated by ybonatakis 11 months ago

  • Subject changed from PXEBOOT doesnt bootindex on aarch64 to PXEBOOT doesnt set bootindex on aarch64
Actions #2

Updated by okurz 11 months ago

  • Category set to Feature requests
  • Target version set to future
Actions #3

Updated by ybonatakis 11 months ago

there is a bug report[0] about the bootindex on aarch64. is this still valid? i couldnt test it

[0] https://bugzilla.suse.com/show_bug.cgi?id=1022064

Actions #4

Updated by livdywan 11 months ago

ybonatakis wrote:

there is a bug report[0] about the bootindex on aarch64. is this still valid? i couldnt test it

[0] https://bugzilla.suse.com/show_bug.cgi?id=1022064

Supposedly #19056 was an older ticket which was blocking on the bug until it was decided to work around the issue in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2824 by using handle_uefi_boot_disk_workaround.

So I would say the bug was never fixed and maybe you want the same work-around.

Actions #6

Updated by ybonatakis 11 months ago

cdywan wrote:

ybonatakis wrote:

there is a bug report[0] about the bootindex on aarch64. is this still valid? i couldnt test it

[0] https://bugzilla.suse.com/show_bug.cgi?id=1022064

Supposedly #19056 was an older ticket which was blocking on the bug until it was decided to work around the issue in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2824 by using handle_uefi_boot_disk_workaround.

So I would say the bug was never fixed and maybe you want the same work-around.

Thanks cdywan. i will check the links. in the meantime i have created a PR if you would like to take a look

Actions #7

Updated by ybonatakis 11 months ago

  • Category deleted (Feature requests)
  • Status changed from New to Feedback
  • Assignee set to ybonatakis
  • Target version deleted (future)
Actions #8

Updated by okurz 11 months ago

  • Category set to Feature requests
  • Target version set to future
Actions #9

Updated by ybonatakis 3 months ago

  • Status changed from Feedback to Resolved

nothing more to do at that point. reopen or fill a new one in case something is needed

Actions

Also available in: Atom PDF