VMM: crashing BIOS "hangs" vmctl start -c / cu

Hi,

just a head's up / for the archives. Do more important things first :)

While testing my packer-vmm port "across the board", I just noticed that
bsd.rd older 5.7
will just hang in 'vmctl start -c' for.. forever?

Dec 9 12:24:12 ssfnhv011 vmd[48696]: myvm: started vm 1 successfully,
tty /dev/ttyp2
Dec 9 12:24:12 ssfnhv011 vmd[81215]: write_mem: failed - invalid memory
range dst = 0xffffffff80f00000, len = 0x1000: Invalid argument
Dec 9 12:24:12 ssfnhv011 vmd[81215]: myvm: failed to load kernel or
BIOS - exiting: Invalid argument

Apparently omitting -c will return to prompt directly - and 'myvm' being
gone (obviously).
With -c there's a "dangling" '/usr/bin/cu -l /dev/ttyp2 -s 115200'
around ..

Maybe something for CAVEATS in vmctl.8 or cu(1) needing kinda signal
that remote
end hung up?

ciao
--
pb