Skip to content



Released: 20 April 2011


  • Added resource settings notification to admin home if settings are incorrect.

  • IP addresses are now considered in the API auto node select.

  • Added upcp function to slave servers.


  • Limit on CPU cores has been raised from 16 to 128.

  • IP block list now displays correctly after deleting an ip block.

  • Slaves with Micro and Mini licenses now show correctly in virtual server build list.

  • Fixed issue where Xen HVM nodes were being ignored in API auto select.

  • Add node page now links correctly to extra settings.

  • Fixed issue where node selector was not showing correctly on add ip block page.



Released: 12 April 2011


  • Added option for KVM NIC card type. Either Realtek 8139 or Intel PRO/1000.

  • Added ability to lock a host node from vps creations.

  • Added admin API function to change a serial console password (vserver-consolepass).

  • Added admin API function to change a vnc password (vserver-vncpass).

  • Added admin API function to return the serial console connection information for a virtual server (vserver-console).

  • Added admin API function to return the vnc connection information for a virtual server (vserver-vnc).

  • Added admin API function to return virtual server information (vserver-state). Ideal for module building.

  • Added extra flags to vserver-create admin API function to specify custom memory, disk space, bandwidth and cpu units.

  • Added the ability to specify extra ip's to the vserver-create admin API function.

  • Added hard power off button in admin and client area for KVM virtual servers ( poweroff.tpl and control.tpl need to be updated for custom templatse).

  • Added better settings layout using tabs.

  • Added better control layout using tabs in admin area.

  • Admin log redesigned.

  • Added node groups. This allows better control over where virtual servers can be created using the API (billing modules). The API will now select a node to build a vps on, based on resources within a certain group of nodes.

  • Added a better layout for assigning ip blocks to nodes.

  • Added Max memory and Max diskpace settings for nodes. The API now needs these settings to provision correctly.


  • CTID/XenID/KVMID now shows correctly on vm delete.

  • Fixed issue with Xen PV root passwords not setting correctly on initial install of virtual server.

  • Fixed SMTP sending support for client lost password emails.

  • Hostnames now allow single characters between dots.

  • OpenVZ virtuals servers now update to the correct template name after rebuild from API.

  • KVM ISO's now sync correctly using the ISO sync feature.

  • Client last names now allow more than 1 word.

  • Fixed database error for resellers viewing virtual servers.

  • Fixed issue with auto FTP backup not deleting temp backups when using older versions of vzdump.

  • Fixed issue where central backup allowances were not updating on plan upgrades.


  • WHMCS module v3 has been released alongside this version of SolusVM.  Download

  • Please make sure you set the max limits for virtual servers, memory and diskspace for each node under nodes settings.


Released: 21 March 2011


  • Added KVM Support ( Installation is via our standard installer (Option 2 » Option 3).

  • Added PAE option for clients (Xen/KVM).

  • Added Daily Status Update for Virtual Servers.

  • Added link buttons to system information on admin home.

  • Added better support for root password salts/encryption for Xen PV. Defaults to standard functions if operating system is not supported.


  • Fixed issue where 1GB was showing as 1024MB in virtual server memory.

  • Fixed issue where virtual server list on admin home was not including Xen HVM.

  • Fixed issue where central backup icon would show in client area even if central backup was not enabled for the virtual server.

  • Fixed issue where quick backup icon would show in client area even if quick backup was not enabled for the virtual server.


There are lots of changes to the client area. If you use a custom template you will need to copy over the contents of the default template to your custom template and re-make your changes. If you fail to do this step, your clients would NOT beable to use KVM.

Back to top