This provides a single, consistent way to configure boot method. the guest listing
now shows uefi and uefi-csm guests without having to fudge the uefi setting into loader column.
Makes some sense as we display "uefi" under "Loader" when listing guests and only one can be set.
Old uefi="" setting can still be set to "csm" to choose the csm firmware.
Windows guests (or at least all of them that I have run under bhyve) appear to want local time and not UTC time for their clocks. As this was the default before 1.2, nothing was needed, but now that the default has changed this is necessary to get the correct time at boot.
Adds passthru0="A/B/C=D:E" syntax, where A/B/C is the host device, and D:E
is the bhyve slot/function. We also add start_slot and install_slot configuration options
to allow users to control the slots used by our bhyve device string.
Dataset is only of use if running on ZFS, but in that case it is very
useful if the script wants to create snapshots/etc, and the path can
be retrieved from pwd/cwd if needed.
Most users are far better off installing this way if possible
Note I do suggest downloading a virtio-net driver and changing the network adapter once
it's up and running.
Alpine now uses "hardened" instead of "grsec".
Also the file layout on installation discs has changed slightly, the grsec kernel was removed.
Tested installation and starting with alpine-standard-3.6.2-x86_64.iso
CoreOS uses its own, modified version of GRUB to load the
appropriate vmlinuz image and mount the appropriate USR partition.
Not using it would leave you to change the boot command manually
everytime your installation performs an update.
On the other hand, CoreOS installation image is not EFI bootable
right now. So, if you want to install from the image, use GRUB
loader and revert back to using UEFI after installation is complete.
I think it's more consistent to have every guest use a UTC clock
by default. Apparently OpenBSD actually assumes a UTC clock. As long
as the guest is configured correctly it will show correct time (although
something like ntp should be used to keep accurate time)
Get rid of ahci_multi_device="yes" and replace with
ahci_device_limit="X", where X is between 2-32. This allows
users to control the number of devices that will be put on
a single controller. If set to 1 (the default), we use the
original bhyve syntax.
