Release Notes V-Cube & V-Cube+ 6.8.14

Collax V-Cube / Collax V-Cube+

Installation Notes

Install Update within Cluster

Please read the following release notes carefully, before continuing. When installing this update on a Collax V-Cube+ cluster the following steps have to be performed:

/ Important information

Please have a look at the Collax V-Cube 6.8.22 Release Notes if the nodes have Version 6.8.20 or above and haven’t been updated yet. For this update, it is necessary that both nodes are set in maintenance mode simultaneously.


  1. Click at High Availability within the Dashboard.
  2. Select the other (not the local) V-Cube+ node and change into the Start Maintenance dialog.
  3. Now, put this other node into maintenance mode by confirming the query in the dialog. Wait until the maintenance mode is reached. Depending on the number of virtual machines and hard disk, this can take some time. Virtual machines will be migrated live, which can take a few minutes depending on the size of the RAM. The progress will be displayed in the list of background activities.
  4. Close the dialog.
  5. In the list of nodes, select again the other node whose software is to be updated by right-clicking it.
  6. Change to System Update ….
  7. Click Check for Updates. The completion will be displayed as “100%”.
  8. Click Download and Install. This function will download the latest software packages from the update server and install them. The completion will be displayed as Install - 100%.
  9. Close the dialog and set the node to active.
  10. Please repeat this procedure for the local node.

Install Update on a Collax V-Cube

To install this update on a Collax V-Cube without a Cluster interconnection please follow these steps:


  1. Please read this document before proceeding to the next step.
  2. Please have a look at the Collax V-Cube 6.8.14 Release Notes if the nodes have Version 6.8.12 or above and haven’t been updated yet.
  3. Please shut down all virtual machines before continuing with the following steps.
  4. In the administration interface go to Menu → Status/Maintenance → Software → System Update and then click Get Package List. This will then download the listed update packages. The successful update of the package list is indicated by the message “Done!”.
  5. Click Get Packages to download the software packages.
  6. Click Install. This action installs the update. The end of this process is indicated by the message Done!.
  7. A new kernel is going to be installed. The system will be rebooted automatically after installing the update. An appropriate note will be shown once the update process is completed.
  8. If the server is updated and booted the virtual machines can be started again.

New in this Version

Virtualization: Extended virtual hard disc without reboot of vm

The dialog “Virtual Hard Disk” lists all drives that are available for use in virtual machines in the cluster. If a virtual hard disk provides too little space for the application, the hard disk can be enlarged. For the virtual machine to be able to use the enlarged hard-disk space, since now the VM had to be shut down and rebooted. Thereafter, the file system of the VM must be resized if this does not take place automatically. Within this release this is not longer necessary any more. If the hard disk is of the type “Virtio”, it may be sufficient to re-read the volume within the VM, depending of the operating system of the VM.

Virtualization: New Windows Virtio Driver for virtual Machines

The Virtio drivers for Windows will be renewed with this update. From this update on virtio driver version virtio-win-0.1.126 are available.

Changelog / Windows Virtio Drivers

Virtualization: QEMU Guest Support

With this update you can use a virtio serial device to communicate between the virtual machine and the hyperviros. There are virtioserial drivers and guest-agent tools on the Virtio Driver CD which have to be installed therefore. Systems with running QEMU guest-agent service now support shutdown/reboot via guest-agent per default. Fall back to the usage of ACPI when necessary.


Virtualization: Kernel configuration item CPUFreq governor

Within this release the Linux kernel configuration item CONFIG_CPU_FREQ_DEFAULT_GOV use “performance” as default resulting in lower latency and higher performance.

Virtualization: different timeoption enabled by default for all virtual machines

Due to changed default settings for virtual machines the time drift is lower than before. Within this update these settings apply to all virtual maschines per default.

V-Cube+: Embedded SAN (DRBD)

Within this release, the replicating block device driver and tools drbd version 8.4 are going to be installed.

GUI: Extended desciption field of a vm

The “comment” field for VMs is beeing extended within this release to a multi-line input field and the complete description can be shown in the tooltip.

GUI: Configuration Management Details

Changes in the Web interface are not adopted directly in the system. Rather, a configuration must be “activated” explicitly. The performed changes are listed more detailled within this release. In the pop-up under Details, you can see which settings have been changed.

GUI: RDP Access to VM Consoles

With this update a GUI-button was added to the dialog of the virtual machine management to directly establish a connection via the protocols RDP (Remote Desktop Protocol) to the VM Consoles.

System Management: Mail Server Port adjustable

In this version a port for the mail server can be specified. The adjustment of another mail server port may be needed if the relay-server does not accept E-mails on standard port 25.

System Management: Boot System UEFI

In this version you can choose the UEFI mode over the default legacy BIOS for virtual machines. The dialogue is located under the extended settings of the virtual machine.

System Management: VESA and QXL graphics card

In this version VESA is used as default graphics card for nely created virtual machines. The dialogue is located under the extended settings of the virtual machine.

Hardware: Additional hardware support

This update brings support for additional network interface cards based on the Intel xgbe driver v5.1.3 and i40e driver 2.0.26 for the Intel platform. These are X552, X553, X540, X722 und XXV710 (25 Gbps Ethernet) to number a few.

Hardware: Fujitsu ServerView RAID Manager netservice

This update adds the netservice “Fujitsu ServerView” (port tcp/3173) to the list of services.

Issues Fixed in this Version

Security: Stack Clash Attack

A security advisory researched various security flaws. These holes have been published as the “Stack Clash” and are going to be fixed within this release. Various patches for the kernel and the C-library glibc are included with this software update. See here .

Assigned Common Vulnerabilities and Exposures (CVE) numbers:

CVE-2017-1000364 CVE-2017-1000365 CVE-2017-1000366 CVE-2017-1000367 CVE-2017-6891

Security: patched Kernel 4.4.70

Several flaws regarding “The Stack Clash” were detected in the kernel. This update installs a patched kernel 4.4.70 where these flaws are fixed.

Security: Bug in Intel Skylake/Kaby Lake processors

Systems with the Intel processors code-named “Skylake” and “Kaby Lake” could, in some situations, dangerously misbehave. The microcode Update microcode-20170511 fixed this issue with this update for Intel Skylake processors. When using Kaby Lake processors, it’s recommended to disable Hyper-Threading in the BIOS. Also see here :

V-Cube+: Preferred Node and Shut Off VM

To achieve optimum utilization of the cluster nodes, you may want to migrate a virtual machine to another cluster node. Due to an erroneous in the programm code, the location constraint was not right in all cases. If the VM is inactive and a preference is set, the VM will be started on the specified node the next time it is started.

V-Cube+: Proactive HA: Failure of LAN interfaces

The Proactive HA ensures that a node that loses a connection to the LAN is evacuated. This behavior has been adjusted. If several LAN connections exist and one LAN connection has failed, the node will not evacuated. Only when all LAN connections have failed, an evacuation occurs.

V-Cube+: Invalid name of local UPS crashes dcsyncd Process

If a UPS name within the cluster was defined with a minus sign, the process dcsyncd could crash. With this update an extended check is implemented to convert names of UPS-devices with that name.

V-Cube+: Error adding virtual harddiscs

If a virtual hard disc in the cluster was being deleted and added again without activating the config, this could lead to a failure. Within this update, this is being fixed. The config needs to be activated before.

GUI: Administrative Roles

You can define administrative roles under Usage Policy -> Environment -> Administrative Roles. This dialog serves the display or individual definition of administrative roles for users. Administrative roles are access permissions of selected users for the respective dialogs of the Collax administration interface. They can be defined in a flexible way, allowing access to one or several dialogs. Due to an error, it was possible that an empty page was displayed after logging in with a selected users. This is going to be fixed within this update.


V-Cube+: Online Snapshots and backups

You can create an online snapshot or an offline snapshot. Apart from creating a separate snapshot disk, an online snapshot stores the current memory state of the machine during operation. You should commit all snapshots before updating to Collax V-Cube+ 6.8.8. Existing online snapshots can be started after the update but their current memeory state will be lost. Same for backups depending on online snapshots.

V-Cube+: Restore virtual harddiscs

From Collax V-Bien version 6.8.15 on the internal path for virtual harddiscs changes and a restore from previous backups isn’t possible anymore without manual intervention. In case of a baremetal resore please use the previous verion or don’t hesitate to contact support.

Misc: Windows Setup notes Error Message 0x80300001

If Windows Server 2008 R2 and above is to be installed on Virtio hard disks using the Virtio driver CD for Windows, Windows reports the error code 0x80300001. The error message occurs if the partitions are recognized and the user clicks the button Next. The message means, that the installation CD of Windows needs to be inserted again.

Misc: Install Collax-Server from template

When installing a Collax Server from a template only Collax Servers from version 7.x and later are supported. The installation of version 5.x is no longer supported.