Re: NetBSD/arm64 on QEMU

[Andreas Gustafsson <gson%gson.org@localhost>]

Jared McNeill wrote:
> I've just committed a fix for this. If you cvs update and build a new 
> arm64.img, it will now DTRT.

Thank you, it now boots successfully.

I'd like to configure a second virtio block device to store ATF
test results on, but if I add a second pair of -drive and -device
options, like this:

    -drive file=/bracket/evbarm-aarch64/test/2018.10.07.05.28.51/anita/wd0.img,format=raw,media=disk,snapshot=on,if=none,id=hd0 \
    -device virtio-blk-device,drive=hd0 \
    -drive file=/bracket/evbarm-aarch64/test/2018.10.07.05.28.51/anita/tests-results.img,format=raw,media=disk,snapshot=off,if=none,id=hd1 \
    -device virtio-blk-device,drive=hd1 \

the new device (hd1) ends up numbered as ld4 and the system disk (hd0) as ld5:

  [   1.0000130] ld4 at virtio30: Features: 0x10000a54<INDIRECT_DESC,CONFIG_WCE,FLUSH,BLK_SIZE,GEOMETRY,SEG_MAX>
  [   1.0000130] virtio30: interrupting on GIC irq 78
  [   1.0000130] ld4: 100 MB, 203 cyl, 16 head, 63 sec, 512 bytes/sect x 204800 sectors
  [   1.0000130] virtio31 at simplebus0
  [   1.0000130] ld5 at virtio31: Features: 0x10000a54<INDIRECT_DESC,CONFIG_WCE,FLUSH,BLK_SIZE,GEOMETRY,SEG_MAX>
  [   1.0000130] virtio31: interrupting on GIC irq 79
  [   1.0000130] ld5: 2048 MB, 4161 cyl, 16 head, 63 sec, 512 bytes/sect x 4194304 sectors

and NetBSD tries to boot from the wrong one.

Is there a way to control the mapping of virtio-blk-device options to
virtio device numbers?  Or any documentation on virtio-blk-device, for
that matter?
-- 
Andreas Gustafsson, gson%gson.org@localhost