Skip to content

Releases: nanovms/nanos

0.1.52

13 Aug 23:12
Compare
Choose a tag to compare
0.1.52 Pre-release
Pre-release

What's Changed

Full Changelog: 0.1.51...0.1.52

0.1.51

25 Jun 23:33
Compare
Choose a tag to compare
0.1.51 Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: 0.1.50...0.1.51

0.1.50

08 Apr 03:04
Compare
Choose a tag to compare
0.1.50 Pre-release
Pre-release

What's Changed

Full Changelog: 0.1.49...0.1.50

0.1.49

18 Jan 16:41
5371b48
Compare
Choose a tag to compare
0.1.49 Pre-release
Pre-release

0.1.49

0.1.48

28 Oct 03:48
a374595
Compare
Choose a tag to compare
0.1.48 Pre-release
Pre-release
bump mac dep (#1957)

Co-authored-by: Ian Eyberg <[email protected]>

0.1.47

24 Aug 17:11
Compare
Choose a tag to compare
0.1.47 Pre-release
Pre-release
stage2, uefi: allocate untyped buffers from tagged region

This addresses a long-standing bug in targets that use a rewind tag for
values (specifically the stage2 and uefi bootloaders), whereby an untyped
buffer allocation was being allocated without creating space for the tag
type. This could manifest in an incorrect tag type being read for a buffer. To
remedy this, an additional tagged region heap is created of type tag_unknown,
and untyped buffer values (currently only coming from decode_value() when
using an old TFS encoding for backward compatibility) are allocated from that
heap.

0.1.46

18 Jul 23:53
Compare
Choose a tag to compare
0.1.46 Pre-release
Pre-release
getsockopt(): add support for SO_DOMAIN

This socket option at the SOL_SOCKET level contains the socket
domain value (e.g. AF_INET or AF_INET6).

0.1.45

13 Jun 19:32
Compare
Choose a tag to compare
0.1.45 Pre-release
Pre-release
netlink RTM_GETADDR: add support for AF_INET6 and AF_UNSPEC

This adds netlink support for reporting IPv6 interface addresses via the
RTM_GETADDR request. It also handles the AF_UNSPEC address family by reporting
both IPv4 and IPv6 addresses.

0.1.44

20 Mar 03:15
Compare
Choose a tag to compare
0.1.44 Pre-release
Pre-release
ATA: honor maximum number of sectors in each I/O request

This commit adds a new function to the ATA disk driver to retrieve
the maxiumum number of sectors that can be submitted in a single
I/O request, which depends on whether LBA48 addressing is
supported. This new function is called by both the x86_64
bootloader and the kernel ATA PCI driver, which check the maximum
sector count value to split each I/O request so that it doesn't
exceed the limit.
This fixes booting on vsphere VMs with IDE disk emulation.

0.1.43

13 Dec 14:50
Compare
Choose a tag to compare
0.1.43 Pre-release
Pre-release
Klibs: AWS CloudWatch: add support for sending logs

This change implements a new console driver that sends log messages
to AWS CloudWatch when Nanos runs on an AWS instance.
This feature is enabled by loading the cloudwatch and tls klibs and
adding a "logging" tuple to the "cloudwatch" tuple in the root
tuple. The "logging" tuple may contain the following attributes:
- "log_group": specifies the CloudWatch log group to which log
messages should be sent; if not present, the log group is derived
from the image name (taken from the environment variables), or from
the name of the user program if no IMAGE_NAME environment variable
is present
- "log_stream": specifies the CloudWatch log stream to which log
messages should be sent; if not present, the log stream is derived
from an instance identifier (e.g.
'ip-172-31-23-224.us-west-1.compute.internal')
The log group and the log stream are automatically created if not
existing.

In order for the cloudwatch klib to retrieve the appropriate
credentials needed to communicate with the CloudWatch Logs server,
the AWS instance on which it runs must be associated to an IAM role
with the CloudWatchAgentServerPolicy, which must grant permissions
for the logs:PutLogEvents, logs:CreateLogGroup, and
logs:CreateLogStream actions, as described in
https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/iam-access-control-overview-cwl.html

Example contents of Ops configuration file:
```
"ManifestPassthrough": {
  "cloudwatch": {
    "logging": {"log_group":"my_log_group","log_stream":"my_log_stream"}
  }
}
```