Martijn van Duren <openbsd+m...@list.imperialat.at> wrote: > (…) > I worked around this by bootstrapping the disk via the qemu port and > booting the disk from vmm once it's finally done. Qemu is significantly > slower than vmm, so do get another cup of $BEVERAGE. > (…)
Another option is to grab https://cdimage.debian.org/cdimage/openstack/current/debian-9.5.2-20180809-openstack-amd64.raw It does not have a premade account so you need to add your ssh public key where it belongs. Boot it via vmd, let the autosetup thing die from timeout. Connect via ssh, uninstall all software related to the autosetup thing (I do not remember the name, but if you watch the first boot, you will have some clue) Reboot the vm. To add a ssh key, I did not succeed in mounting the file via vnconfig, not sure whether it is doable or not so I used a Debian system I had access to. On the linux host: # losetup /dev/loop0 debian-9.5.2-20180809-openstack-amd64.raw # kpartx -a /dev/loop0 # mount /dev/mapper/loop0p1 /tmp/vmdisk/ ### the moment you add your ssh public key. # umount /dev/mapper/loop0p1 # kpartx -d /dev/loop0 # losetup -d /dev/loop0 Hope it helps as well.
