Release Notes V-Cube & V-Cube+ 6.9.12
Collax V-Cube / Collax V-Cube+
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.9.0 Release Notes if the nodes have Version 6.8.28 or above and haven’t been updated yet. For updates below 6.8.22, it is necessary that both nodes are set in maintenance mode simultaneously.
- Click at High Availability within the Dashboard.
- Select the other (not the local) V-Cube+ node and change into the Start Maintenance dialog.
- 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.
- Close the dialog.
- In the list of nodes, select again the other node whose software is to be updated by right-clicking it.
- Change to System Update ….
- Click Check for Updates. The completion will be displayed as “100%”.
- 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%.
- A new kernel is going to be installed. The node will automatically be rebooted two minutes after the installation of the system update. This wll be indicated upon completion of the update procedure. Wait for the node to reboot.
- Close the dialog and set the node to active.
- Please repeat this procedure for the local node.
New in this version
Linux Kernel 4.9.334
This update installs the Linux kernel 4.9.334.
UEFI support for Windows update.
The KB5012170 security update for Windows Server 2019, Windows 2022 and Windows 10 has increased the boot system UEFI requirements. It requires a larger virtual memory (NVRAM) for the boot system because of the “Pre-Enrolled Keys”. This update provides a second UEFI image that meets the new requirements. If the Windows update is aborted with the error message 0x800f0922, the used UEFI image can be changed on the administration interface. When editing a VM, two options for UEFI are now available under “Boot system”. The previous one as “UEFI (legacy 2M Image)” with 2 MB NVRAM and the new “UEFI” with 4 MB NVRAM. The latter must be set so that the Windows update can be installed.
Monitoring of RAID status temperatures on Broadcom controllers
The monitoring system Nagios warns and alarms when RAID controller temperatures are too high. With this update the thresholds have been slightly increased, warning is now at 90° C instead of 85° C and alerting at 100° C instead of 95° C. Please note: Not all controllers have sensors for temperature.
Security vulnerabilities have been discovered in the source code of the hypervisor QEMU. These are closed with this software update. These are 36 previously unreleased security fixes from the Debian Buster qemu 3.1+dfsg-8+deb10u9 package.
Remote access program OpenSSH
Security vulnerabilities have been discovered in the source code of OpenSSH. These are closed with this software update. Version 9.0p1 is installed with this update.
With the optional Collax V-Transfer module, virtual machines can be completely transferred between the Collax V-Bien, Collax V-Cube or Collax V-Cube+ virtualization solutions with just a few mouse clicks. With this update, the module is pre-installed on all platforms so that it can be easily enabled for use on licensed systems if required.
Problems fixed in this version
Performance graphs of the measurement categories CPU
When displaying the statistics for the CPU utilization of a VM in the cluster, it was not scaled correctly. As a result, values were displayed that were too low. This has now been corrected.
Intel Microcode Update
Potential security vulnerabilities in some Intel® processors may allow information disclosure. Intel releases firmware updates to mitigate these potential vulnerabilities. This update updates the new microcode to microcode-20220809.
V-Cube+: Windows setup issues error message 0x80300001
If Windows Server 2008 R2 or later is installed on VirtIO hard disk using the VirtIO driver CD for Windows, Windows reports an error message after detecting the partitions and clicking the Next button, Windows reports error code 0x80300001. The message means that the Windows installation CD should be inserted again. should be inserted.
Changed partition scheme for new installation since version 6.9.0 / Important when replacing a node
If one of the nodes is defective, it can be simply exchanged over the dialog “Add new node”. simply exchanged. Because of a changed partition scheme a few things have to be considered. - Both nodes should have have nearly identical hardware equipment - Both nodes must have the same Both nodes must have the same version - An additional 10 GB of free memory must be available on the available on the storage volume “default”, if the version of the existing node was installation was older than 6.9.0. Check under “Virtual disks” and Click on “Storage Volumes”, then right click on the storage volume “default”. the free space specified under Size.
Collax V-Transfer target server check
Since release 6.9.12 a check of the target server takes place. The required version for this must be >= 6.9.12.