Skip to content




  • feature | PHP 8.1 support by WHMCS billing module solusvmpro. (SVM-3619)
  • bugfix | Fixed the issue when IPv6 subnet was not automatically selected on virtual server creation screen if subnet is included in plan. (SVM-3415)
  • bugfix | Fixed the issue when parameter deleteclient of API function vserver-terminate did not work. (SVM-1023)


  1. Behavior of the WHMCS module solusvmpro is changed by SVM-3623.

    Old behavior: if a client has a single virtual server and the server is removed from WHMCS, the client is not removed from SolusVM.

    New behavior: if a client has a single virtual server and the server is removed from WHMCS - the client is also removed from SolusVM. If later new virtual server is created in WHMCS, the client is re-created in SolusVM.




  1. New API function supports only KVM migration initially.



  • bugfix | Fixed the issue when reverse DNS zone on PowerDNS server could not be created if TLD of hostmaster email is longer than 3 symbols. (SVM-3609)



  • feature | New field storage_type has been added to the output of API function get-all-nodes-statistics. (SVM-3594)
  • improvement | A significant amount of source code is being prepared for PHP upgrade to version 8.1. (SVM-3556)


  1. New field storage_type is filled for KVM nodes only.

  2. Additionally, data type of parameter node_error has changed from string to array of string elements.



  • bugfix | Fixed the issue when reverse DNS (PTR) record was not removed on PowerDNS server after VPS removing in SolusVM. (SVM-3561)



  • feature | PHP has been upgraded to version 7.4.32. (SVM-3585)



  • feature | Support of disk driver scsi for KVM VMs. (SVM-2986)


  1. Disk driver scsi can now be selected on OS template adding/editing screen and on KVM VM management screens in admin UI/client UI.

  2. When scsi driver is selected, attribute discard with value unmap is added to element driver of disk devices in XML configuration file of the KVM VM.

  3. Prefix of the disk device name inside the VM depends on the selected driver: ide/virtio - vd (e.g., /dev/vda), scsi - sd (e.g., /dev/sda). This is the libvirt behavior. Careless changing of the disk driver can lead to inability of KVM VMs to boot. Corresponding notifications have been added in UI.

  4. If some files inside the existing OS template refer to the disk name (e.g., in /etc/fstab), it can be required to edit the template before using driver scsi with this OS template.

  5. Downgrade from version 1.27.15 Mainline to 1.27.09 Stable is not recommended in case if SolusVM has KVM VMs. Such downgrade can lead to inability of KVM VMs with scsi disk drivers to boot.



  • feature | Set netmask from IP block for OpenVZ containers. (SVM-3566)


  1. In older versions default netmask /24 was used for OpenVZ containers on EZ templates and /32 for containers on legacy templates.
  2. Now netmask from corresponding IP block is used.



  • feature | Added rockylinux as a supported prefix for KVM OS templates. (SVM-3571)
  • bugfix | Fixed the issue when migration status bar could get frozen during bulk migration of OpenVZ containers although actual migration finished successfully. (SVM-3564)




  1. Output format is JSON only.
  2. Output field names are inherited from API function node-statistics besides new field node_error.



  • bugfix | Fixed the issue when API vserver-rebuild did not reinstall a VM from legacy to EZ template and vice versa. (SVM-3450)
  • bugfix | Fixed the issue when KVM VM migration gets stuck if real disk size mismatches value in SolusVM DB. (SVM-3549)


  1. Before starting KVM migration SolusVM compares disk size in the DB and on the Node and displays warning if the size is different.
  2. Admin user can continue with the migration ignoring the warning.
  3. Corresponding information is logged in Admin UI > Log > System messages.



  • feature | New system setting Block direct access to VNC is introduced to increase security. (SVM-3444)
  • bugfix | Fixed the issue when SolusVM incorrectly counts the number of extra IPs assigned to a VPS when upgrading a service in WHMCS via configurable options. Fixed in version 4.1.8 of solusvmpro. (SVM-3482)


Setting Block direct access to VNC is disabled by default. It can be enabled in Admin UI > Configuration > Settings, tab Other.

When it is enabled:

  1. Direct access to VNC TCP ports is closed in iptables on KVM and Xen nodes. Access to VNC console works only from SolusVM UI.
  2. Default range of TCP ports that is closed on SN is 5901-6000. It can be extended up to 5901-7000 in system settings.
  3. API function vserver-vnc hides values of vncip, vncport, vncpassword.
  4. VNC settings Address, Port, Password and tab VNC Password are hidden in SolusVM client UI.
  5. Outdated Java VNC console in WHMCS does not work. Use HTML5 console instead.



  • bugfix | Fixed the issue when ACL privilege Reinstall did not work for KVM VMs. (SVM-3545)



  • feature | New privilege Migrate has been added to section Virtual Server of administrator ACLs. (SVM-3479)


During this update installation new privilege Migrate will be enabled in all existing Administrator ACLs where privilege Manage is enabled.



  • bugfix | Fixed the issue when admin user could start multiple concurrent re-installations of the KVM VM in admin UI. (SVM-3483)
  • bugfix | Fixed the issue when multiple popup windows were shown on space button click in admin UI. (SVM-3507)



  • feature | Show free diskspace in /vz partition in the output of API node-statistics for OpenVZ node. (SVM-3528)
  • bugfix | Fixed the issue when character < makes the backup.log file unavailable to view in SolusVM UI. (SVM-3512)



  • bugfix | Fixed the issue when nice and ionice settings are not fully applied to backup process. (SVM-3175)
  • bugfix | Fixed the issue when login to SolusVM is slow if DNS on the Master Node malfunctions. (SVM-3207)
  • bugfix | Fixed security issue. (SVM-3510)



  • feature | PHP has been upgraded to version 7.4.30. (SVM-3505)
  • bugfix | Fixed the issue when incorrect data migration speed units are shown on KVM VM migration screen. (SVM-3460)



  • feature | Ability to install SolusVM in OpenVZ container with Almalinux 8. (SVM-3469)
  • bugfix | Fixed the issue when bandwidth statistics is not collected on new Almalinux 8/Centos 8 Stream nodes. (SVM-3485)
  • bugfix | Fixed the issue when script /scripts/websocket-stop is not working on SolusVM Master Node. (SVM-3500)



  • feature | Nginx has been upgraded to version 1.22.0. (SVM-3498)
  • bugfix | Fixed the issue when KVM VM failed to start due to libvirt 8 VNC password length restriction if the password length exceeds 8 characters. (SVM-3488)
  • bugfix | Fixed the issue when the First Available Node for a VPS creation via API was chosen incorrectly due to the wrong Nodes order. (SVM-3467)
  • bugfix | Fixed the issue when the OS name was always CentOS for every OS in Admin UI > Nodes > Check version. (SVM-3448)
  • bugfix | Fixed the issue when CentOS 7 KVM/Xen installation contained broken documentation links. (SVM-3475)
  • bugfix | Fixed the issue when there was an incorrect copyrights date in all encrypted files. (SVM-3490)


  1. API functions vserver-create and vserver-vncpass now allow only 8 characters long VNC passwords for KVM.
  2. On changing VNC password in admin UI or client UI the password length cannot exceed 8 characters now.
  3. Now API vserver-console cannot be launched for KVM since it configures serial console but KVM VMs are accessed via VNC console.
  4. If WHMCS module solusvmpro is in use it is recommended to update the module to the latest version 4.1.7




  1. New KVM Storage Manager and Tags Mechanism are the key components of the new KVM storage management flow.
  2. Downgrade from version 1.27.01 Mainline to 1.26.13 Stable is not recommended in case if SolusVM has KVM VMs. Such downgrade can lead to unexpected stop of existing KVM VMs and damage to their XML configs.
  3. We recommend performing update from older versions to version 1.27.01 out of business hours or in time with minimal load to the system because of the possibility of a short service downtime during this update installation.
  4. Update to version 1.27.01 must not intersect with AutoFTP backups creation process.
  5. Note: It is recommended to carefully read the list of known issues and limitations.
Back to top