Weekly news #369

LXD News
,
1

Weekly status for the week of 21st October to 27th October.

Introduction

The past week, LXD received several bug fixes, and a new feature that makes virtual machine CPU auto pinning optional instead of applying it by default.

Disabling auto CPU pinning by default

LXD introduced a new setting limits.cpu.pin_strategy for virtual machines. Prior to that, LXD enabled CPU pinning by default, which meant that each instance was pinned to a specific set of cores when started (auto). The new default behavior only defines the number of cores the virtual machine gets, but any core may be used at any given time (none).

To (re)enable automatic CPU pinning, you can set limits.cpu.pin_strategy for the desired VM to auto:

lxc config set v1 limits.cpu.pin_strategy=auto

Documentation: Instance options - Resource limits

Bugfixes

  • Fixed an issue where cluster group creation would fail if multiple nodes are present in the request.

  • Improved profile and instance listing by introducing caching of certain data on entities to reduce database queries (from Incus). Instance listing has been further improved by querying database only for the relevant instances, instead of filtering them afterwards.

  • Fixed an issue where instance evacuation and healing process did not respect the project restricted groups, causing an instance to potentially end up on cluster members that are outside project restrictions.

  • Fixed an issue where LXD reapplied old core.https_address and cluster.https_address addresses when a node is added to the cluster again. Now, LXD attempts to apply the core.https_address to cluster.https_address, but if the value is wildcard, the server address is used instead.

  • Fixed a issue where console would not start if the instance is started on the server.

  • Fixed an issue where NVIDIA CDI drivers were searched on the host filesystem in Ubuntu Core environments. Since Ubuntu Core is snapped, the drivers are now searched in core24 snap instead.

All changes

The items listed below is all of the work which happened over the past week and which will be included in the next release.

LXD

LXD UI

LXD Charm

  • Nothing to report this week

LXD Terraform provider

PyLXD

Distribution work

This section is used to track the work done in downstream Linux distributions to ship the latest LXD as well as work to get various software to work properly inside containers.

Ubuntu

  • Nothing to report this week.

LXD snap

3 Likes