Date: Fri, 6 Jul 2018 21:37:34 +0100 From: tech-lists <tech-lists@zyxst.net> To: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> Cc: freebsd-virtualization@freebsd.org, freebsd-current@freebsd.org Subject: Re: bhyve and freebsd memstick installer Message-ID: <7cffa475-4d43-987c-f380-2384f4834ce1@zyxst.net> In-Reply-To: <201807061732.w66HWgJF053394@pdx.rh.CN85.dnsmgr.net> References: <201807061732.w66HWgJF053394@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7cffa475-4d43-987c-f380-2384f4834ce1>