On Fri, Oct 24, 2014 at 03:28:33PM -0700, Craig Rodrigues wrote:
> On Fri, Oct 24, 2014 at 6:11 AM, Conrad Rad wrote:
>
> >
> > Any idea how soon? Months? A year? 5 years? I'm not comfortable
> > postponing improvements indefinitely for vaporware. In the wonderful
> > bhyve-UEFI future, we can ig
On Fri, Oct 24, 2014 at 6:11 AM, Conrad Rad wrote:
>
> Any idea how soon? Months? A year? 5 years? I'm not comfortable
> postponing improvements indefinitely for vaporware. In the wonderful
> bhyve-UEFI future, we can ignore/warn about .
>
>
Hi,
I have to agree with Conrad here. I hope that any
On Fri, Oct 24, 2014 at 12:58 AM, Roman Bogorodskiy
wrote:
> Conrad Meyer wrote:
> Hi Conrad.
>
> Thanks for the patch. As for the /tmp, probably storing it somewhere in
> BHYVE_STATE_DIR would be more clean.
Sure.
> However, I'm concerned about libvirt dealing with the grub-bhyve
> specifics
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.
Caveats:
-
