I have had a hard time understanding why I cannot access any

img file I have attached to a qemu arm64 VM during boot (linux host).

Boot would simply return "device not configured" as an error. e.g


> cannot open sd0a:/etc/random.seed: Device not configured


Turns out there is an explicit check for a block size of 512 inside

of arm64/stand/efidev.c - I only managed to figure this out after a printf

debugging.


I have a couple of questions:

1) Is this block size a hard requirement?

2) If so, does anyone have a suggestion on how to improve error

messaging? I wondered if adding a sort of "disk status" command

to boot might help? or adding more verbose error messaging?


James.


Reply via email to