flexVDI Blog

Changes since 3.1.6

• Fixed bug: under some circunstances, rebalancing resources, failed to re-reserve resources that in fact where available, due to a race condition. This could cause flexVDI Manager to abruptly stop guests without need.
• Fixed bug: when a volume is not accessible by all the hosts that should have access (due to hardware problems or manteinance), make requests only to the hosts that con access the volume.
• Give a proper error message when ldap server is down when authenticating a user.
• Improve some log messages.

flexVDI manager is available for update running flexvdi-config command on the host where the current manager is running. Instructions are available here. Also it can be manually downloaded from portal.flexvdi.com, for servers not connected to the internet.

flexvdi-config now starts chronyd as the NTP daemon, instead of ntpd in systems that have none of them enabled.

Until now flexvdi-config enabled ntpd if it was not enabled in the flexVDI Host, as part of the setup. Since 3.1.5, it enables chronyd instead, but only if neither chronyd nor ntpd are enabled and running in the system.

flexVDI Hosts that are currently running ntpd, will not be modified by flexvdi-config.

The new release can be updated executing in the flexVDI hosts:

# yum -y update flexvdi-config

• flexVDI Manager hardware clock and timezone will be the same used by the host. This release copies the timezone used by the flexVDI Host to the flexVDI Manager when installing or updating it. Needs flexVDI-agent >= 3.1.7 to keep the clock right after restarting flexVDI manager.
• Show more details when flexvdi portal can’t be reached
• Fix message to user about how to unregister a Host when reinstalling flexVDI Manager

The timezone in flexVDI Manager will be set with the right value the next time flexVDI manager is updated using flexvdi-config >= 3.1.4.

The new release can be updated executing in the flexVDI hosts:

# yum -y update flexvdi-config

• Bugfix: exporting several guests at the same time failed sometimes.
• Some more information logged about the connection between flexvdi-agent and qemu process.

The new release can be updated executing in the flexVDI hosts:

# yum -y update flexvdi-agent

– Improvement: sysprep/unattend template file for Desktop Policies is now searched in the image_storage/volume where the volatile guests are created, before searching the old /var/lib/flexvdi/local location. This way, system administrators only need to maintain one copy of the file.
– Bugfix: flexVDI agent does not restart itself when a mounted CIFS volume stops responding; improved CIFS error handling.
– Bugfix: volatile desktops created from a desktop policy with a sysprep/unattend file failed to be migrated.
– Small improvement: remove spaces after the “|” character in syspre file name if present.
– Add information in log messages, about sysprep files, and disk images.
– Reclassify some log messages.

The new release can be updated executing in the flexVDI hosts:

# yum -y update flexvdi-agent

Supports OCFS2 file system in servers with the latest Red Hat / CentOS 7 kernel: 3.10.0-1160.6.1.el7.x86_64

To install it, just run:

yum install kmod-ocfs2-flexvdi-k1160.x86_64

This command will also install the new kernel if needed, which will be used after the next reboot of the server.

Changes since 3.1.0

• Fixed bug: A race condition caused flexvdi-gateway to crash sometimes, closing all user sessions it was serving, and restarting immediatelly.

To update your servers, log in to your flexVDI Hosts with ssh and run:

yum update flexvdi-gateway

You can do this at any time, as it will not cause any service disruption.

Afterwards, you will have to start the new version of the gateway with:

systemctl restart flexvdi-gateway

This second step will not stop any virtual machine, but it will close established connections that are going through the restarted gateway. All end users that are connected through the restarted flexvdi-gateway will see their connection closed and will have to login with flexvdi-client again.

Changes since 3.1.5

• Fixed bug: all timestamps in flexVDI manager log lines are now shown in local time. This is effective for new installations. If you want to fix the configuration of a flexVDI manager installed with a release of flexVDI Manager before 3.1.6 see “problems with flexVDI Manager”
• Fixed bug: volatile desktops lost their disk contents when they where modified in flexVDI Dashboard and then restarted or migrated.
• Many CentOS packages, including kernel and mongodb have been updated in the flexVDI Manager appliance.
• Privacy improvement: error messages returned when authenticating against an LDAP server are now not written to the log file file by default. Some LDAP servers include sensitive information in these messages.

flexVDI manager is available for update running flexvdi-config command on the host where the current manager is running. Instructions are available here. Also it can be manually downloaded from portal.flexvdi.com, for servers not connected to the internet.

Fixes a bug in the creation of flexvdi manager that causes flexvdi manager to get a wrong clock time from the hardware clock when it is started, if the flexVDI Host is not configured in UTC.

The fix will take effect after updating the package, the next time flexVDI manager is started.

The new release can be updated executing in the flexVDI hosts:

# yum -y update flexvdi-agent