+The DragonFly 3.0 release is here! This release was delayed from our regular schedule for tracking down [what appears to be a AMD CPU bug](http://gitweb.dragonflybsd.org/dragonfly.git/commit/8e32ecc0a77082f1e232a3e6d12e2f163f9667a4). As a pleasant side effect, the giant kernel lock has been removed from much of the system and this release performs significantly better on multi-core systems than previous DragonFly versions.

## Big-ticket items

-### HAMMER performance greatly increased

+### Major VM SMP work

+

+Previously the majority of the VM was under a single token, the vm_token; now vm_objects (mappable entities) are each under a private token, concurrent page faults in the same object can proceed, and VM SMP scalability overall is improved. Results for Postgres and MySQL, among others, are excellent.

-A new time domain multiplexing method has been added to balance storage operation types over long time periods. As a result, HAMMER performance increased by XX% under some typical scenarios (see benchmarks here, here, here) and HAMMER fairness and throughput under heavy storage loads is now better than all tested alternatives.

+Francois Tigeot [worked on benchmarks](http://leaf.dragonflybsd.org/mailarchive/kernel/2011-11/msg00004.html) comparing DragonFly 2.10 and DragonFly 2.13, among other operating systems. The resulting graphs show how well DragonFly responds to multiple CPUs on a 24-threads Xeon system. (2.13 is the development version of DragonFly that became 3.0.)

+A new [time domain multiplexing method](http://leaf.dragonflybsd.org/mailarchive/commits/2011-07/msg00086.html) has been added to balance storage operation types over long time periods. HAMMER fairness and throughput under heavy storage loads has significantly improved.

-HAMMER's behavior in very low memory configurations has also improved; it will no longer readily starve a system of kernel allocation space.

+HAMMER's behavior in very low memory configurations has also improved; it will no longer readily starve a system of kernel allocation space. HAMMER should work on systems with as little as 256MB of RAM.

### SMP kernel installed by default

ACPI + interrupt routing have been upgraded. A SMP kernel will work on all machines and is installed by default.

-### Major VM SMP work

-

-Previously the majority of the VM was under a single token, the vm_token; now vm_objects (mappable entities) are each under a private token, concurrent page faults in the same object can proceed, and VM SMP scalability overall improved. Results for Postgres and MySQL, among others, are excellent.

+DragonFly now has [tcplay(8)](http://leaf.dragonflybsd.org/cgi/web-man?command=tcplay&section=8), a tool for creating and managing encrypted disk volumes. It is 100% [TrueCrypt](http://www.truecrypt.org/) compatible and BSD licensed.

## Availability

-Three release options are now available for 32-bit as well as for 64-bit. 64-bit installations are recommended if you do not need the linux emulation layer.

+Four release options are now available for 32-bit as well as for 64-bit. 64-bit installations are recommended if you do not need the linux emulation layer.

+

+* An ISO, to be burned to a physical CD or used as an image to install a virtual machine.

+Note that the x86_64 GUI ISO image had booting problems that are now fixed.

-The release ISO images should be available on most of the [[mirrors|mirrors]]. If the ISO is not available on a certain mirror, please try another one or download it from the DragonFly master site. Each image is in the "Live CD" format, meaning that it boots into a running and fully functional DragonFly system, which can be used for testing or system recovery tasks as well as installation

+The release ISO images should be available on most of the [[mirrors|mirrors]]. If the ISO is not available on a certain mirror, please try another one or download it from the DragonFly master site. Each image is in the "Live CD" format, meaning that it boots into a running and fully functional DragonFly system, which can be used for testing or system recovery tasks as well as installation. Check the [hardware page](http://www.dragonflybsd.org/docs/supportedhardware/) or boot a Live CD to check for compatibility.

The GUI bootable USB image also contains the DragonFly git repo in /usr/src and the pkgsrc git repo in /usr/pkgsrc. The code can be trivially checked out using these repos and can be incrementally updated from master sites, post-install.

@@ -68,14+103,30 @@ We supply a Makefile in `/usr` to track the pkgsrc tree and we supply a Git mirr

**Virtual PC users** - Virtual PC does not supply serial numbers for the virtual disks. The system may need to be manually directed in the boot loader if the disk identifier changes. (Hit ? in the boot loader for a list of available volumes.)

+**Qemu users** - If you see a large number of error messages on the console when booting, you may need to boot DragonFly with ACPI disabled. This can be done in the menu presented at initial boot. If that doesn't help, try placing hw.ioapic_enable=0 in /boot/loader.conf.

+

**Installer Crypt Options** - The installer can encrypt the root volume and the swap volume. It will not work properly for other volumes despite any additional check-boxes you might see. Installer and boot-time support works but is still a bit rough around the edges. Performance will be relatively high on multi-core machines.

**ISA driver removal** - A number of ISA hardware drivers have been removed. One of these drivers, ie(4), was in our GENERIC config. Another driver, aha(4), was in both our GENERIC and our X86_64_GENERIC kernel configuration files. If you are using a kernel config based on a previous release's GENERIC config file, you may need to remove these drivers in order to successfully compile the kernel.

+**PAM Changes** - The pam_krb5 and pam_ksu modules have been removed as part of a PAM update. If you were using these modules, the security/pam-krb5 package in pkgsrc is a suitable replacement.

+entries will need to be rebuilt in order to authenticate against the new hashing schemes.

+To convert existing databases to the new format, re-run passwd(1) on the desired accounts.

+

+**Remaining issues** - The DragonFly bug tracker mentions some issues still known but not fully diagnosed at time of release. Specifically, building world with more than 4 processes (-j 5) may cause issues on i386, and some users have seen issues with NFS. Check the [3.0 release ticket](http://bugs.dragonflybsd.org/issues/2286) for details.

-## DragonFly 3.0 Release Notes

+## DragonFly 3.0.2 Release Notes

-### Release Improvements

+>### Kernel Changes

+

+* Disable the I/O APIC when booting in a virtual environment by default; some VMs did not work well with DragonFly when this option was on.