1.6.0

We are excited to announce our release for aleph-vm in version 1.6.0!

This update brings significant new networking capabilities like IPv4 port forwarding, new API endpoints, and a host of important bug fixes to improve stability and reliability.

✨ New Features & Enhancements

• IPv4 Port Forwarding: The VM now supports IPv4 port forwarding (#806).
• Hardware Capability Endpoint: A new API endpoint has been added to provide detailed CPU (model, vendor, frequency) and memory (clock, size, type) information (#801).
• New Execution List Endpoint: A new endpoint for listing executions has been added, along with logic to retry instances that are not running (#793).

🐞 Bug Fixes

• Networking & Firewall:
  • Fixed an issue with incorrect port directions (#810).
  • Resolved a problem causing duplicate nftables firewall rules (#812).
  • Addressed and solved firewall redirect issues (#813).
• System & Stability:
  • The Grub root device path has been corrected to ensure proper booting (#805).
  • The program warmup timeout has been increased from 1s to 5s to prevent startup issues (#814).
  • A DBUS error that occurred when enabling the controller has been fixed (#815).
• API:
  • API error responses are now guaranteed to be in JSON format (#804).

🛠️ Other Improvements

• The CI/CD pipeline has been fixed (#808).
• The aleph-message dependency has been updated to the latest version (#809).
• The README.md has been updated (#817).

What's Changed

• fix: Grub root device must be placed in a proper location to avoid bo… by @aliel in #805
• ALEPH-512 ensure we always return json for error by @olethanh in #804
• Retry instances not running add new Execution list endpoint by @olethanh in #793
• New capability endpoint to add CPU information (model, vendor, frequency) and memory details (clock, size, type) to API by @olethanh in #801
• Solve CI/CD issue by @nesitor in #808
• ALEPH-551 Implement ipv4 port forwarding by @olethanh in #806
• Use last aleph-message version by @nesitor in #809
• Fix issue on port directions by @olethanh in #810
• Aleph 446 duplicate nftables rule by @olethanh in #812
• Solve firewall redirect issues by @olethanh in #813
• fix: Increase program warmup timeout from 1s to 5s by @aliel in #814
• ALEPH-435 Fix DBUS error when enabling controller by @olethanh in #815
• Update README.md by @clementfrmd in #817

New Contributors

• @clementfrmd made their first contribution in #817

Full Changelog: 1.5.1...1.6.0

How to upgrade

1. Upgrade the packages

This part did not change, download and install the new package as usual.

On Debian 12 (Bookworm):

rm -f /opt/aleph-vm.debian-12.deb
wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/1.6.0/aleph-vm.debian-12.deb
apt install /opt/aleph-vm.debian-12.deb

On Ubuntu 22.04 (Jammy Jellyfish):

sudo rm -f /opt/aleph-vm.ubuntu-22.04.deb
sudo wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/1.6.0/aleph-vm.ubuntu-22.04.deb
sudo apt install /opt/aleph-vm.ubuntu-22.04.deb

On Ubuntu 24.04 (Noble Numbat):

sudo rm -f /opt/aleph-vm.ubuntu-24.04.deb
sudo wget -P /opt https://github.com/aleph-im/aleph-vm/releases/download/1.6.0/aleph-vm.ubuntu-24.04.deb
sudo apt install /opt/aleph-vm.ubuntu-24.04.deb

2. Enable GPU support (optional)

In order to enable GPU support on your Compute Resource Node, you must:

1. Ensure that your system have a compatible GPU card.
2. Detach GPU cards from the kernel module drivers and attach it to QEMU vfio drivers.
3. Enable GPU support in the aleph-vm configuration.

Please follow these instructions

Enable GPU in the configuration of aleph-vm, by default in /etc/aleph-vm/supervisor.env. This is not the default yet.

ALEPH_VM_ENABLE_GPU_SUPPORT=True

After launching the server you can check the endpoint
http://localhost:4020/status/config or https://<your-node-domain>/status/config and verify that ENABLE_GPU_SUPPORT has the value true.