Skip to content

Release 2.4.2 - Release Notes (29 April 2021)

New Features

  1. Introduction of the automated update service, initially will be rolled out onto the SIM instances.
  2. Added a cache layer on the SIM platform, to considerably increase the performance.


  1. Added the ability to see the VNC console of VMs (PV and HVM) from the SIM.
  2. Added the ability to do multiple parallel snapshots from the SIM.
  3. Improved the HTTPS ability of the main UI reference to the SIM UI.
  4. Added a PCI device support on VM create via the SIM directly.
  5. Added a PCI device support on VM create via the SIM recipe framework.

Bug Fixes

  1. Updated our usage calculation algorithms.
  2. Updated the additional repository creation procedure.
  3. Validated the latest Ubuntu and Centos images.
  4. Updated our VLAN methodology, when VLAN is enabled on the management network (default VLAN).
  5. Updated our flavour creation procedure via the SIM recipe framework.

Supported Features

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

In Development - targeted for an upcoming release

  1. Striping of volumes across multiple physical NVMe drives, in order to enable larger volume capacity and enhanced single drive performance to more than 1 Million IOPs.
  2. Revisions of supported hardware are planned, in order to accommodate faster NIC performance.
  3. Multi-LUN aggregation support (creating super LUNs, consisting of many smaller LUNs that can span physical NVMe drives for increased capacity).
  4. Physical NVMe drive hotplug removal/addition.
  5. SIM enhancements towards added VM actions.
  6. Advanced recipe marketplace management with easier UI components.
  7. SIM ability to upgrade using the new Sunlight automated upgrade system.

Compatibility and Limits Matrix

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

Known Issues

  1. 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
  2. Occasional connection issues to PV guest console. Suggested mitigation solution is to reboot the VM.
  3. 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.
  4. Editing an existing VLAN network is not currently supported. In order to edit the VLAN, you must delete and recreate the network.
  5. It is not possible to edit the network configuration of a VM in the case the instance boots from an CD/ISO.
  6. 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.
  7. 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.
  8. Simultaneous resizing of multiple VM instances is not currently supported.
  9. During the upgrade phase, master and slave nodes will be required to be booted down. Currently, the upgrade is performed manually by the Sunlight support team.
  10. 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.
  11. 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.
  12. Instances that will be moved and/or backed up in the SIM dashboard should have only one root disk. The existence of extra disks is currently not supported in this case.
  13. The "Create snapshot" action currently does not support massive parallelism. We are currently testing to lift the limitations.
  14. 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.

Breaking Changes

  • N/A

Supported Versions

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

GPL Code Patches

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