On Mon, Oct 27, 2014 at 6:17 AM, Daniel P. Berrange wrote:
> On Fri, Oct 24, 2014 at 04:28:14PM -0400, Conrad Meyer wrote:
>> docs/drvbhyve.html.in | 28 ++-
>> docs/formatdomain.html.in | 4 +-
>> po/libvirt.pot| 4 +
>> src/bhyve/bhyve_command.c | 204
>> ++
On Fri, Oct 24, 2014 at 04:28:14PM -0400, Conrad Meyer wrote:
> We still default to bhyveloader(1) if no explicit bootloader
> configuration is supplied in the domain.
>
> If the /domain/bootloader looks like grub-bhyve and the user doesn't
> supply /domain/bootloader_args, we make an intelligent
Conrad Meyer wrote:
> On Sun, Oct 26, 2014 at 7:00 AM, Roman Bogorodskiy
> wrote:
> > Conrad Meyer wrote:
> >
> >> I've tested the HDD boot and it seems to work.
> >
> > I've tried to boot from CD and had a problem with that. It generates a
> > command like that:
> >
> > /usr/local/sbin/grub-
On Sun, Oct 26, 2014 at 7:00 AM, Roman Bogorodskiy
wrote:
> Conrad Meyer wrote:
>
>> I've tested the HDD boot and it seems to work.
>
> I've tried to boot from CD and had a problem with that. It generates a
> command like that:
>
> /usr/local/sbin/grub-bhyve -v --root cd --device-map
> /usr/loca
Conrad Meyer wrote:
> We still default to bhyveloader(1) if no explicit bootloader
> configuration is supplied in the domain.
>
> If the /domain/bootloader looks like grub-bhyve and the user doesn't
> supply /domain/bootloader_args, we make an intelligent guess and try
> chainloading the first
We still default to bhyveloader(1) if no explicit bootloader
configuration is supplied in the domain.
If the /domain/bootloader looks like grub-bhyve and the user doesn't
supply /domain/bootloader_args, we make an intelligent guess and try
chainloading the first partition on the disk (or a CD if o
