FreeBSD 14.0-BETA1 Now Available
posted by Roy Schestowitz on Sep 10, 2023
The first BETA build of the 14.0-RELEASE release cycle is now available.
Installation images are available for:
o 14.0-BETA1 amd64 GENERIC
o 14.0-BETA1 i386 GENERIC
o 14.0-BETA1 powerpc GENERIC
o 14.0-BETA1 powerpc64 GENERIC64
o 14.0-BETA1 powerpc64le GENERIC64LE
o 14.0-BETA1 powerpcspe MPC85XXSPE
o 14.0-BETA1 armv7 GENERICSD
o 14.0-BETA1 aarch64 GENERIC
o 14.0-BETA1 aarch64 RPI
o 14.0-BETA1 aarch64 PINE64
o 14.0-BETA1 aarch64 PINE64-LTS
o 14.0-BETA1 aarch64 PINEBOOK
o 14.0-BETA1 aarch64 ROCK64
o 14.0-BETA1 aarch64 ROCKPRO64
o 14.0-BETA1 riscv64 GENERIC
o 14.0-BETA1 riscv64 GENERICSD
Note regarding arm SD card images: For convenience for those without
console access to the system, a freebsd user with a password of
freebsd is available by default for ssh(1) access. Additionally,
the root user password is set to root. It is strongly recommended
to change the password for both users after gaining access to the
system.
Installer images and memory stick images are available here:
https://download.freebsd.org/releases/ISO-IMAGES/14.0/
The image checksums follow at the end of this e-mail.
If you notice problems you can report them through the Bugzilla PR
system or on the -stable mailing list.
If you would like to use Git to do a source based update of an existing
system, use the "releng/14.0" branch.
=== Virtual Machine Disk Images ===
VM disk images are available for the amd64, i386, aarch64, and riscv64
architectures. Disk images may be downloaded from the following URL
(or any of the FreeBSD download mirrors):
https://download.freebsd.org/releases/VM-IMAGES/14.0-BETA1/
BASIC-CI images can be found at:
https://download.freebsd.org/releases/CI-IMAGES/14.0-BETA1/
The partition layout is:
~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label)
~ 1 GB - freebsd-swap GPT partition type (swapfs GPT label)
~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label)
The disk images are available in QCOW2, VHD, VMDK, and raw disk image
formats. The image download size is approximately 135 MB and 165 MB
respectively (amd64/i386), decompressing to a 21 GB sparse image.
Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI
loader file is needed for qemu-system-aarch64 to be able to boot the
virtual machine images. See this page for more information:
https://wiki.freebsd.org/arm64/QEMU
To boot the VM image, run:
% qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt \
-bios QEMU_EFI.fd -serial telnet::4444,server -nographic \
-drive if=none,file=VMDISK,id=hd0 \
-device virtio-blk-device,drive=hd0 \
-device virtio-net-device,netdev=net0 \
-netdev user,id=net0
Be sure to replace "VMDISK" with the path to the virtual machine image.
=== Amazon EC2 AMI Images ===
FreeBSD/amd64 EC2 AMI IDs can be retrieved from the Systems Manager
Parameter Store in each region using the keys:
/aws/service/freebsd/amd64/base/ufs/14.0/BETA1
FreeBSD/arm64 EC2 AMIs are not available for BETA1, and the cause is
being investigated.
=== Vagrant Images ===
FreeBSD/amd64 images are not available for BETA1. The cause is being
investigated.
=== Upgrading ===
The freebsd-update(8) utility supports binary upgrades of amd64 and i386
systems running earlier FreeBSD releases. Note, aarch64 binary updates
are expected to be available starting with BETA2, due to a configuration
error. Systems running earlier FreeBSD releases can upgrade as follows:
# freebsd-update upgrade -r 14.0-BETA1
During this process, freebsd-update(8) may ask the user to help by
merging some configuration files or by confirming that the automatically
performed merging was done correctly.
# freebsd-update install
The system must be rebooted with the newly installed kernel before
continuing.
# shutdown -r now
After rebooting, freebsd-update needs to be run again to install the new
userland components:
# freebsd-update install
It is recommended to rebuild and install all applications if possible,
especially if upgrading from an earlier FreeBSD release, for example,
FreeBSD 12.x. Alternatively, the user can install misc/compat12x and
other compatibility libraries, afterwards the system must be rebooted
into the new userland:
# shutdown -r now
Finally, after rebooting, freebsd-update needs to be run again to remove
stale files:
# freebsd-update install
Read on
