Date: Sun, 26 Aug 2018 16:07:41 -0400 From: Allan Jude <allanjude@freebsd.org> To: Paul Vixie <vixie@fsi.io>, freebsd-virtualization@freebsd.org Subject: Re: Query regarding tutorials (Please have a quick read of me!) Message-ID: <f3256f6a-0cc6-89c7-c5f5-1521f6262438@freebsd.org> In-Reply-To: <5449454.ijkHvH96lN@linux-9daj> References: <CADdqeiO0mGtGuao6t4Nq_Ts4qG6Xqs54C=NzpVKuyyZqPSBAuw@mail.gmail.com> <6699362.kGnQbBhLUH@linux-9daj> <fc5c9bf6-12e7-a01d-6cb2-83aace585a64@freebsd.org> <5449454.ijkHvH96lN@linux-9daj>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--42QrO9LWLikv5vVJkGxXtlwTlp6W7702Y
Content-Type: multipart/mixed; boundary="WTXQXkvVpefn85VKCMaTMdudzA9uDha6R";
protected-headers="v1"
From: Allan Jude <allanjude@freebsd.org>
To: Paul Vixie <vixie@fsi.io>, freebsd-virtualization@freebsd.org
Message-ID: <f3256f6a-0cc6-89c7-c5f5-1521f6262438@freebsd.org>
Subject: Re: Query regarding tutorials (Please have a quick read of me!)
References: <CADdqeiO0mGtGuao6t4Nq_Ts4qG6Xqs54C=NzpVKuyyZqPSBAuw@mail.gmail.com>
<6699362.kGnQbBhLUH@linux-9daj>
<fc5c9bf6-12e7-a01d-6cb2-83aace585a64@freebsd.org>
<5449454.ijkHvH96lN@linux-9daj>
In-Reply-To: <5449454.ijkHvH96lN@linux-9daj>
--WTXQXkvVpefn85VKCMaTMdudzA9uDha6R
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
On 2018-08-26 01:54, Paul Vixie wrote:
> On Sunday, August 26, 2018 2:46:42 AM UTC Allan Jude wrote:
>> On 2018-08-25 13:45, Paul Vixie wrote:
>>> ... i remain
>>> mystified by the behaviour of grub-bhyve, which usually fails (no
>>> meaningful error message) and seems like won't run from /etc/rc.local=
>>> (must be run from a shell.) so, one of my bhyve servers can't restart=
>>> automatically, and i don't know why. ...
>=20
>> What does the invocation look like?
>=20
> grub-bhyve -r $defdev -m $vm.map -M $pm -c /dev/$sc $vm \
> > ${vm}.output 2>&1 \
> || {
> echo "grub-bhyve failed" >&2;
> exit 1;
> }
>=20
>> Does this work:
>> printf "\n" | grub-bhyve ...your-stuff-here...
>=20
> i'll give it a try. testing this particular path requires a reboot, and=
the=20
> system is otherwise running in production... so give me a day or two.
>=20
>>
>> As an alternative, you can now use the UEFI_CSM firmware for bhyve, an=
d
>> it'll boot from the boot blocks inside the VM, like xen/kvm/qemu/virtu=
albox
>=20
> this sounds far preferable! is there an example or other documentation?=
>=20
first, get the firmware images:
pkg install bhyve-firmware
Then, instead of invoking grub-bhyve, add this extra flag to your bhyve
invokation:
-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd
Or if you want old style BIOS booting:
-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI_CSM.fd
--=20
Allan Jude
--WTXQXkvVpefn85VKCMaTMdudzA9uDha6R--
--42QrO9LWLikv5vVJkGxXtlwTlp6W7702Y
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
iQIcBAEBAgAGBQJbgwiQAAoJEBmVNT4SmAt+tCEP/0Glym6xvk0Igrqb4iULkXkL
YRjH5j0PaZD4qMPKyFKdKdUSpbmSHhFf3crnAtfpG9p5BoKc+NbLOP3ImwT4RgSF
KjJrwIqDd50OjPqXra3kk701nM14hE+PYL4yA94FD4SijNACboIneS1vbf9S9O4i
FFOh0W9bfHyFCCypFJ1v2DaWQtr13sBvcZ3f1UHOD9L4d7LuvP7mNewcusOtb5S1
qgDOEWDRSn1ILzq3eM6odFIzQ3nIrJ6836IHfxgpMWf02B/hrrjir1Byd213WxyR
GeT150bPt/02WSLKTDhqIixv48ViDbrPVJfEEgtp9y4RMb0D0A2UaLWSMzk9IfrJ
OjZ4JoH84H2/VnlwDsrxg/tydx4nAWUfGVQfivtyMwpckmJ/Q/DW+UiswyTzhnI+
1PCkbQxiqjRNhu+7rsneAQcp3XhhPLJg4FZWxf+kc5gG0IaZhUTTCn90wguUYGa/
V+5wFxgvUVwqkDvvXkLDTXa6kSiIiHj28cGQD6RkH3dtU6vA9XKTv6x8xSfxNtLw
/EwofFBr3upkPKt2HQijjUWcbXmex0nnngg2CEep8xUfpUOcsc/7e0sfoAF/qDSK
W/Z9T2j1tzamqozHJbFvN4Lnm0StMNxK3Q7qlroa6TjFh4FdDaJzkHOUOyM/8nJx
RfKkRW1+CPbB9BNLMcB/
=Wbl+
-----END PGP SIGNATURE-----
--42QrO9LWLikv5vVJkGxXtlwTlp6W7702Y--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f3256f6a-0cc6-89c7-c5f5-1521f6262438>