Tags: aleph-im/aleph-vm
Tags
Implemented GPU compatibility system (#747) * Feature: Added options to get GPU compatibilities from a settings aggregate. * Fix: Refactored to also return the model name from the aggregate and use the same device_id format. * Fix: Include GPU list and move the VM egress IPv6 check on the connectivity check to start notifying the users about the next requirement. * Fix: Solved code quality issues. * Fix: Put definitive settings aggregate address * Fix: Solved issue with type casting and moved the aggregate check. * Check community payment flow (#751) * Implement community payment check WIP * isort * Check community flow at allocation * Community flow : fix after testing * mod Use singleton for the Setting Aggregate * fix test * Implement community wallet start time --------- Co-authored-by: Olivier Le Thanh Duong <olivier@lethanh.be>
Fix: Runtime emitted wrong reboot signal (#741) The runtime init `init1.py` emitted the signal `0x4321fedc` to the Linux kernel when shutting down. The correct procedure [according to the Firecracker docs] (https://github.com/firecracker-microvm/firecracker/blob/dfb45dc4213bcb1c9704435457e233d3a210dce2/docs/getting-started.md?plain=1#L298) is to issue a `reboot`. The syscall number for a reboot on Linux is `0x1234567`. Tested using Firecracker independently of `aleph-vm`.
Implement new EVM chains (#717) * Feature: Implement new EVM chains. * FIX: Update Makefile with new dependency. * Fix: Updated to proper released package version of aleph_message dependency. --------- Co-authored-by: Andres D. Molins <nesitor@gmail.com>
Fix: Error fetching message from vm-connector for start_watch_for_mes… …sages_task Jira ticket : ALEPH-111 Problem: When aleph-vm was starting if the vm-connector couldn't connect to the pyaleph API , the startup crashed and systemd restarted it in a loop. Solution: Stop registering the sample program at startup, so the pyaleph api don't need to be reached at startup. This code was left as a demo but it didn't really do anything at the moment. We have just commented the code if we want to reuse it in the future. Note: A more complete and long analysis of the problem, along with propsed solution is on the JIRA ticket https://aleph-im.atlassian.net/browse/ALEPH-111?focusedCommentId=10008