Colin Percival b9f767ebd2 Set use_nvd=0 in EC2 AMIs. ... FreeBSD is in the process of switching from nvd(4) to nda(4) as the disk device front-end to NVMe. Changing the default in the kernel is tricky since existing systems may have /dev/nvd* hard-coded e.g. in /etc/fstab; however, there's no reason to not change the default in HEAD for *new* systems. At present I have no intention of MFCing this to stable branches, since someone might reasonably expect scripts they use for launching and configuring FreeBSD 12.1 instances to work with FreeBSD 12.2 AMIs, for example. Reviewed by: gjb, imp Relnotes: NVMe disks in EC2 instances launched from 13.0 and later now show up as nda(4) devices. Differential Revision: https://reviews.freebsd.org/D24583		2020-04-27 21:44:02 +00:00
..
arm.subr	Add support for generating release images using GPT for ARM	2020-04-24 16:31:27 +00:00
azure.conf	Chase r284656 and r284658:	2015-06-21 04:34:57 +00:00
ec2.conf	Set use_nvd=0 in EC2 AMIs.	2020-04-27 21:44:02 +00:00
gce.conf	Revert r348438.	2019-05-31 18:40:19 +00:00
openstack.conf	multi-boot for openstack/qcow images	2020-01-27 22:40:03 +00:00
vagrant-virtualbox.conf	Remove /etc/resolv.conf from virtual machine images, which is	2017-11-21 18:02:18 +00:00
vagrant-vmware.conf	Remove /etc/resolv.conf from virtual machine images, which is	2017-11-21 18:02:18 +00:00
vagrant.conf	Increase the size of the Vagrant default image size, as the 3GB	2019-05-30 17:00:57 +00:00
vmimage.subr	Revert r348438.	2019-05-31 18:40:19 +00:00