Skip to content

Releases: firecracker-microvm/firecracker

Firecracker v0.18.1

09 Dec 13:16
Compare
Choose a tag to compare

Fixed (on top of v0.18.0):

  • Fixed a logical error in bounds checking performed on vsock virtio descriptors (CVE-2019-18960).

Firecracker v0.19.0

14 Oct 14:11
Compare
Choose a tag to compare

Added

  • New command-line parameter for firecracker, named --no-api, which
    will disable the API server thread. If set, the user won't be able to send
    any API requests, neither before, nor after the vm has booted. It must be
    paired with --config-file parameter. Also, when API server is disabled,
    MMDS is no longer available now.
  • New command-line parameter for firecracker, named --config-file, which
    represents the path to a file that contains a JSON which can be used for
    configuring and starting a microVM without sending any API requests.
  • The jailer adheres to the "end of command options" convention, meaning
    all parameters specified after -- are forwarded verbatim to Firecracker.
  • Added KVM_PTP support to the recommended guest kernel config.
  • Added entry in FAQ.md for Firecracker Guest timekeeping.

Changed

  • Vsock API call: PUT /vsocks/{id} changed to PUT /vsock and no longer
    appear to support multiple vsock devices. Any subsequent calls to this API
    endpoint will override the previous vsock device configuration.
  • Removed unused 'Halting' and 'Halted' instance states.

Fixed

  • Fixed serial console on aarch64 (GitHub issue #1147).
  • Upon panic, the terminal is now reset to canonical mode.
  • Explicit error upon failure of vsock device creation.
  • The failure message returned by an API call is flushed in the log FIFOs.
  • Insert virtio devices in the FDT in order of their addresses sorted from
    low to high.
  • Enforce the maximum length of the network interface name to be 16 chars as
    specified in the Linux Kernel.
  • Changed the vsock property id to vsock_id so that the API client can be
    successfully generated from the swagger definition.

Firecracker v0.18.0

04 Sep 14:38
Compare
Choose a tag to compare

Added

  • New device: virtio-vsock, backed by Unix domain sockets (GitHub issue #650).
    See docs/vsock.md.

Fixed

  • Updated the documentation for integration tests.
  • Fixed high CPU usage before guest network interface is brought up (GitHub
    issue #1049).
  • Fixed an issue that caused the wrong date (month) to appear in the log.
  • Fixed a bug that caused the seccomp filter to reject legit syscalls in some
    rare cases (GitHub issue #1206).
  • Docs: updated the production host setup guide.
  • Docs: updated the rootfs and kernel creation guide.

Removed

  • Removed experimental support for vhost-based vsock devices.

Firecracker v0.17.0

14 Jun 13:38
Compare
Choose a tag to compare

Added

  • New API call: PATCH /machine-config/, used to update VM configuration,
    before the microVM boots.
  • Added an experimental swagger definition that includes the specification for
    the vsock API call.
  • Added a signal handler for SIGBUS and SIGSEGV that immediately terminates
    the process upon intercepting the signal.
  • Added documentation for signal handling utilities.
  • Added [alpha] aarch64 support.
  • Added metrics for successful read and write operations of MMDS, Net and Block devices.

Changed

  • vcpu_count, mem_size_mib and ht_enabled have been changed to be mandatory
    for PUT requests on /machine-config/.
  • Disallow invalid seccomp levels by exiting with error.

Fixed

  • Incorrect handling of bind mounts within the jailed rootfs.
  • Corrected the guide for Alpine guest setup.

Firecracker v0.16.0

03 May 08:12
Compare
Choose a tag to compare

Added

  • Added [alpha] AMD support.
  • New devtool command: prepare_release. This updates the Firecracker
    version, crate dependencies and credits in preparation for a new release.
  • New devtool command: tag. This creates a new git tag for the specified
    release number, based on the changelog contents.
  • New doc section about building with glibc.

Changed

  • Dropped the JSON-formatted context command-line parameter from Firecracker
    in favor of individual classic command-line parameters.
  • When running with jailer the location of the API socket has changed to
    <jail-root-path>/api.socket (API socket was moved inside the jail).
  • PUT and PATCH requests on /mmds with data containing any value type other
    than String, Array, Object will return status code 400.
  • Improved multiple error messages.
  • Removed all kernel modules from the recommended kernel config.

Fixed

  • Corrected the seccomp filter when building with glibc.

Removed

  • Removed the seccomp.bad_syscalls metric.

Firecracker v0.15.2

09 Mar 00:53
Compare
Choose a tag to compare
Firecracker v0.15.2 Pre-release
Pre-release

Fixed

  • Corrected the conditional compilation of the seccomp rule for madvise.

Firecracker v0.15.1

07 Mar 22:22
Compare
Choose a tag to compare
Firecracker v0.15.1 Pre-release
Pre-release

Fixed

  • A madvise call issued by the musl allocator was added to the seccomp
    whitelist to prevent Firecracker from terminating abruptly when allocating
    memory in certain conditions.

Firecracker v0.15.0

22 Feb 17:45
Compare
Choose a tag to compare

Added

  • New API action: SendCtrlAltDel, used to initiate a graceful shutdown,
    if the guest has driver support for i8042 and AT Keyboard. See
    the docs for details.
  • New metric counting the number of egress packets with a spoofed MAC:
    net.tx_spoofed_mac_count.
  • New API call: PATCH /network-interfaces/, used to update the rate limiters
    on a network interface, after the start of a microVM.

Changed

  • Added missing vmm_version field to the InstanceInfo API swagger
    definition, and marked several other mandatory fields as such.
  • New default command line for guest kernel:
    reboot=k panic=1 pci=off nomodules 8250.nr_uarts=0 i8042.noaux i8042.nomux i8042.nopnp i8042.dumbkbd.

Fixed

  • virtio-blk: VIRTIO_BLK_T_FLUSH now working as expected.
  • Vsock devices can be attached when starting Firecracker using the jailer.
  • Vsock devices work properly when seccomp filtering is enabled.

Firecracker v0.14.0

22 Jan 17:25
Compare
Choose a tag to compare

Added

  • Documentation for development environment setup on AWS in dev-machine-setup.md.
  • Documentation for microVM networking setup in docs/network-setup.md.
  • Limit the maximum supported vCPUs to 32.

Changed

  • Log the app version when the Logger is initialized.
  • Pretty print panic information.
  • Firecracker terminates with exit code 148 when a non-whitelisted syscall is intercepted.

Fixed

  • Fixed build with the vsock feature.

Firecracker v0.13.0

08 Jan 16:36
Compare
Choose a tag to compare
Firecracker v0.13.0 Pre-release
Pre-release

Added

  • Documentation for Logger API Requests in docs/api_requests/logger.md.
  • Documentation for Actions API Requests in docs/api_requests/actions.md.
  • Documentation for MMDS in docs/mmds.md.
  • Flush metrics on request via a PUT /actions with the action_type
    field set to FlushMetrics.

Changed

  • Updated the swagger definition of the Logger to specify the required fields
    and provide default values for optional fields.
  • Default seccomp-level is 2 (was previously 0).
  • API Resource IDs can only contain alphanumeric characters and underscores.

Fixed

  • Seccomp filters are now applied to all Firecracker threads.
  • Enforce minimum length of 1 character for the jailer ID.
  • Exit with error code when starting the jailer process fails.

Removed

  • Removed InstanceHalt from the list of possible actions.