On 06/07/2018 18:32, Rodney W. Grimes wrote: > Untested, but since memstick is actually a "disk" image and not > a "cdrom" image you should be able to do something like > vmrun.sh -c 2 -m 4096M -t tap0 -d memstick.img -d guest.img guestname > > Your memstick should show up as ada0, > and your guest.img should be ada1. Thanks for that, I'll try it next time I can. I got round it temporarily by mounting the memstick as /dev/md1p3 and pointing mkisofs at that. the -i -I thing of bhyve threw me. I thought I'd need it to point to bootable media. -- J.Received on Fri Jul 06 2018 - 18:37:37 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:16 UTC