Date: Wed, 15 May 2019 12:18:32 +0000 From: "Wall, Stephen" <stephen.wall@redcom.com> To: "freebsd-security@freebsd.org" <freebsd-security@freebsd.org> Subject: RE: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-19:07.mds Message-ID: <cdf6982694db447985b15e9170256fe5@exch-02.redcom.com> In-Reply-To: <20190515000302.44CBB1AB79@freefall.freebsd.org> References: <20190515000302.44CBB1AB79@freefall.freebsd.org>
index | next in thread | previous in thread | raw e-mail
> New CPU microcode may be available in a BIOS update from your system vendor, > or by installing the devcpu-data package or sysutils/devcpu-data port. > Ensure that the BIOS update or devcpu-data package is dated after 2014-05-14. > > If using the package or port the microcode update can be applied at boot time > by adding the following lines to the system's /boot/loader.conf: > > cpu_microcode_load="YES" > cpu_microcode_name="/boot/firmware/intel-ucode.bin" Is this applicable in a virtualized environment, or only on bare metal? If not applicable in a VM, is it at least harmless? Thanks - Steve Wallhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cdf6982694db447985b15e9170256fe5>