The commands used are:

#grub-bhyve -r cd0 -m ./vm/lin1/ -M 4096 lin1

where is:

#cat vm/lin1/

(hd0) ./vm/lin1/lin1.img

(cd0) ./vm/lin1/lin1.iso

Bhyve is started with:

#/usr/sbin/bhyve -c 1 -m 2048 -A -I -H -s 0,hostbridge -s
2,virtio-blk,./vm/lin1/lin1.img -s 3,virtio-net,tap1 -s
4,ahci-cd,./vm/lin1/lin1.iso -S 31,uart,stdio lin1

On Thu, Jan 23, 2014 at 11:37 AM, Aryeh Friedman

> On Thu, Jan 23, 2014 at 5:05 AM, Jonas Bülow <>wrote:
>> I do use the precanned bhyve-script "vm0" (if that is what you mean). It
>> explicitly mentions linux support. bhyveload can't be user for other images
>> than FreeBSD so I don't know how to use your script for a linux OS
> Since I have not used bhyve-grub personally yet I can not recommend what
> the correct loader command line but if bhyve-script is in anyway related to
> I would be highly suspicious of any command lines you manage to
> extract from it since they are often not the ones actual called.
>> I assume the image is file backed as I have not assigned a dedicated
>> partition to the vm (and I don't know how to do that).
> You can keep them anywhere no need for a special volume (mater of fact I
> was just reusing the name of one of the diretoriess that PC creates during
> install even without it being a different vol [just assumes any FS
> boundaries are the host OS's problem)... you can put the disk image any
> where (your home directory would be fine for example)
_______________________________________________ mailing list
To unsubscribe, send any mail to 

Reply via email to