On 03/06/2015 18:53, John-Mark Gurney wrote:
> Andriy Gapon wrote this message on Wed, Jun 03, 2015 at 10:10 +0300:
>> On 03/06/2015 02:04, John-Mark Gurney wrote:
>>> Andriy Gapon wrote this message on Tue, Jun 02, 2015 at 21:15 +0300:
>>>> I guess you are running bhyve through the shell script vmrun.sh?
>>>> I am doing everything by hand.
>>> Correct:
>>> sh /usr/share/examples/bhyve/vmrun.sh -g 6444 -d mach10s.img -t tap0
>>> It's nice.. shutdown -r now and shutdown -p now both work exactly as
>>> you'd expect them to... :)
>> Yes, it's quite convenient.  The only drawback is that currently it can't 
>> pass
>> multiple -d options to bhyveload and I need that from time to time.
> Hmm... Looking at the script, it looks like you can (at least on HEAD):
>         d)
>                 eval "disk_dev${disk_total}=\"${OPTARG}\""
>                 disk_total=$(($disk_total + 1))

This was only half of the equation, please see this:

>> Probably not hard to change that.
> It'd also be nice to allow you to switch the default from virtio-blk
> to ahci when you're image doesn't support it..
> Hmm.. It wouldn't be hard to try to use environment vars for the defaults
> either...
> Maybe it's time to move vmrun.sh to bhyverun, install it and give
> it a proper man page?

JIMO, bhyveload(8) could be just merged into bhyve(8) and the latter should
behave like vmrun.sh does.  bhyve(8) should retain an option to run a preloaded
kernel, so that things like bhyve-grub keep working.

Andriy Gapon
freebsd-virtualization@freebsd.org mailing list
To unsubscribe, send any mail to 

Reply via email to