Release Notes V-Bien 6.5.14
Please read the following release notes carefully, before continuing. When installing this update on a Collax V-Bien cluster the following steps have to be performed:
/ Important information
Please have a look at the Collax V-Bien 6.5.28 Release Notes if the nodes have Version 6.5.26 or above and haven’t been updated yet. For this update, 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) 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%.
- Close the dialog and set the node to active.
- Please repeat this procedure for the local node.
New in this Version
Linux Kernel 3.12.58
This update installs a patched Linux kernel 3.12.58.
Issues Fixed in this Version
This updates is introducing improvements in the areas of backup and restore, UPS support, and snapshot as well as their administration via the user interface. A rare race condition, preventing VMs from proper operation after backup or snapshot, can no longer occur with this update. Please have a look at the Collax V-Bien 6.5.10 Release Notes if the nodes have Version 6.5.12 or above and haven’t been updated yet. For this update, it is necessary that both nodes are set in maintenance mode simultaneously. To do this, open the overview of the VMs and send each VM by right-clicking the shutdown-signal. Then click on the dashboard to the area “high availability” and set both nodes by right-clicking into the “maintenance mode”. If the maintenance mode of both nodes is reached, select successively for both nodes again by right-clicking “System update” and start the two update steps. After installation is complete, click on the button “Activate Nodes”. The nodes are restarted during the update process.
In the dialog UPS Devices, UPS (uninterruptible power supplies) devices can be configured. If the other node was shutdown and the button refresh USB-UPS was pressed, an error message was generated instead of the information that the other node in not reachable at the moment. With this update this is fixed.
A restored VM is no longer running on an alleged Snapshot
Once a virtual machine has been restored from backup, it seemed to be running on a snapshot. For instance, this prevented deleting the VM, because the snapshot has to be cleared before. The false assumption was triggered by remaining configuration files. With this update, these configuration files are no longer point to supposedly applied snapshot.
A previously deleted VM can be restored immediately
Restoring a virtual machine immediately after you deleted a VM, could fail. The recovery process has been terminated with the message “VM Running”. Only after a few minutes, the recovery was possible. This update assures that the restore is possible immediately.
V-Cube+: 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.