Skip to content

Release 4.8.0 - Release Notes (21 June 2023) - Extra patches included


This is our newest release (release 4.8.0) with major changes. You need to have at least version 4.2.0 to be able to upgrade to this latest release.

Additional instructions would be published as far as the upgrade procedure is concerned.

Extra patch V2 include - 08 Aug 2023

We have rectified a slight irregularity in the platform installer and updated the method to recognize the management networks.

Extra patch V3 include - 11 Aug 2023

We have rectified a new timing bug in the interface discovery procedure.

Extra patch V4 include - 23 Aug 2023

We new present all NICs for selection and assignment to the controller. We also have made the 1Gbit network interface to be enabled by default. Minor bug fixes relating to the presentation

of all NICS

New Features

  • Added support for Debian 11.
  • Enabled GPU support for ARM64 nodes.
  • Implemented platform health status reporting.
  • Implemented an interactive and user-friendly cluster location map feature.
  • Migrated node actions from the VirtupianAPI to the NexCenterAPI.
  • Introduced a new action to forcefully update the recipe templates.
  • Implemented recipe lifecycle management, allowing the re-execution of recipe templates.
  • Implemented a key/value store specifically designed for Ansible scripts, facilitating data exchange between different Playbooks.


  • Improved storing of Recipe templates on the filesystem instead of the DB.
  • Renamed Marketplace page to AppLibrary.
  • Renamed Template page to Backup.
  • Renamed About page to Updates.
  • Improved RAM consumption of Controller VM. Decreasing the consumption of the API service.
  • Improved new snapshot creation process, with better error handling and progress reporting.
  • Renamed the SIM UI to NexCenter and the Virtupian UI to Edge Stack Console UI.

Bug Fixes

  • Fixed the issue related to the initialization process on uninitialized storage drives.
  • Resolved the issue regarding networking static IP assignment for internal networks.
  • Resolved the bug related to inventory input variables.

AWS product updates

  • The same updates and fixes mentioned for the main product have been applied to this component as well.

In Development - targeted for an upcoming release

  • Simple Resource group initialization for new connected cluster.
  • Clustering function, merging/unmerging two different cluster into a single one.
  • Reduce the size of the installation image.
  • New factory installation process - Allowing answers injected into the process.

Supported Features

For additional information on supported features, please visit the following link : Supported Features for version 4.8.0.

Compatibility and Limits Matrix

Please visit the following link for further information on compatibility and limits: Compatibility and Limits Matrix for version 4.8.0

Current list of supported Network Adapters

Please visit the following link for further information on supported Nics: supported Network adapters

Known Issues

  • In order for the GPU device to be assigned to a different VM, the persistence mode should be disabled. For more information, please refer to the section "Disable NVIDIA GPU Persistence mode" in the following document: Disable NVIDIA GPU Persistence mode
  • Occasional connection issues to PV guest console. Suggested mitigation solution is to reboot the VM.
  • The automated installation of PV drivers for MS Windows ISO images is not currently supported. An end-to-end functional solution is currently in the development process.
  • Editing an existing VLAN network is not currently supported. In order to edit the VLAN, you must delete and recreate the network.
  • It is not possible to edit the network configuration of a VM in the case the instance boots from an CD/ISO.
  • For a VM instance that is booted from CD/ISO, Sunlight does not initialize the cloud init logic. Network configuration must be applied on the VM by the user.
  • The maximum supported virtual disk size which is currently tested in the system is up to 2TB. Larger size vdisk deployments are currently under test.
  • NexCenter simultaneous resizing of multiple VM instances is not currently supported.
  • During the upgrade phase, primary and secondary nodes will be required to be booted down. Currently, the upgrade is performed manually by the Sunlight support team.
  • It is recommended that the maximum number of instances created in a cluster (all at once) should be limited to less or equal than 8.
  • Please use “SHIFT”, instead of the “CAPS LOCK” button, for capital letters, when typing the login/password of an instance through the VNC console. Using the “CAPS LOCK” button currently results in misspelled username/password.
  • Instances that will be moved and/or backed up in the NexCenter dashboard should have only one root disk. The existence of extra disks is currently not supported in this case.
  • The "Create snapshot" action currently does not support massive parallelism. We are currently testing to lift the limitations.
  • There is a caveat in using all physical NICs on an AWS cluster. Physical NICs 0,2,3 should be used only for private networks. Physical NIC 1 should not be used at all. The rest of the physical NICs, 4 to 15 should be used only for public access networks. In future releases this will be handled automatically via the virtupian UI.
  • Currently we do not support VMs using the UEFI bootloader.
  • We have noticed an issue when using large NVMe drives, larger than 2TB, during the installation process. We suggest that the NVMes are completely zeroe'd out before starting the installation.

PV images

PV images are deprecated - Our suggestion is to use a new template repo that does not include PV images, Please use HVM.

Supported Versions

You can visit the Release notes of the previous versions in the archive section. Please be reminded, versions prior to 4.2.0 are not supported.

We are planning to limit the scope of the minimum supported version to 4.6.4.

Relevant upgrade procedures will be published, please issue a request with out support team.

GPL Code Patches

The modified GPL code patches used in this release are available at: GPL Code Patches Release 4.8.0