flexVDI Blog

follow us on

Released flexVDI Client v3.1.2

Changes since v3.1.1

  • Fix crash when the connection is closed by the server.
  • Fix CRITICAL log messages that make reference to a NULL pointer cast.
  • Linux: Ungrab the keyboard and mouse after 50 seconds of inactivity so that the screen saver and lock screen apps can run.
  • Windows: Fix installing to “C:\Program files” on 64-bit OS.
  • Windows: Fix showing model and vendor of known USB devices.

Released flexVDI Client v3.1.1

Changes since v3.1.0

  • First version that includes support for Mac OS X
  • Make sure flexVDI Client looks right in different desktop environments/distributions/GTK themes.
  • Fix loging in automatically when the assigned Terminal Policy is non-authenticated, after the server address is changed with the settings panel.
  • Desktop names are sorted case-insensitively.
  • Fix double free looking for the terminal ID on Windows.
  • Install Lato font on Windows.

NEW!! flexVDI v3.1

And finally, after almost 2 years of hard work, flexVDI v3.1 comes to life. It is a minor release update, but comes with a ton of new features and improvements under the hood:

  • New flexVDI HTML5 Dashboard. The old Java Dashboard has been replaced with a faster, leaner, curvier and fancier HTML5 Dashboard. Its new interface provides an agile experience and boosts the productivity of your system administrators. You just need to point a modern web browser (Mozilla Firefox or Google Chrome are recommended) to the Manager’s address, there is no need to download or install an additional application.
  • New flexVDI Desktop Client. A new client for Linux, Windows and MacOS X desktops with unified interface and all the features of the latest Spice client library: folder sharing, video acceleration with GStreamer, selectable compression algorithms… And soon, multi-screen support! The live USB client has also been promoted to flexVDI ThinClient OS, a Linux distribution to easily boot hundreds of thin clients and old computers and connect to your flexVDI platform.
  • No downtime upgrade. The upgrade process will only stop the flexVDI Manager and Agent for some seconds, while they are updated. All your guests will keep running and your users will not even notice the change.
  • Up-to-date components: CentOS 7.6, Qemu 2.12, Libvirt 4.5, Spice server 0.14, Spice GTK 0.36, Virtio drivers for Windows 0.1.171…
  • Improved scalability and performance. flexVDI 3.1 provides a professional-grade VDI experience, even for the most demanding workloads. We have added support for the new Virtio GPU on Linux desktops; PCI passthrough for maximum performance on dedicated NVMe devices; easier user configuration with LDAP groups; arbitrary Desktop Policy parameters for fully configurable desktops; and more features to come!

Check your Customer Portal‘s account for flexVDI Installer 3.1 downloads, and flexVDI Downloads page for anything else. Also, do not forget the flexVDI 3.1 documentation to read about how to install a new flexVDI 3.1. platform, or upgrade your old one.

Enjoy flexVDI!

Released flexvdi-agent v3.0.6

Changelog from flexVDI Agent v3.0.5

  • Fix listing network interfaces
  • Do not try to use huge pages explicitly. Transparent huge pages are used automatically if they are available.
  • Kill libvirtd if checking the domains’ status is stuck for too long:
    As of libvirt 3.9.0-14.el7_5, there is a bug that hungs libvirtd for unknown reasons. This renders the flexVDI platform unusable. If the agent suspects the libvirtd daemon to be hung, it kills it. Systemd automatically respawns it moments later and the problem is (temporally) solved.

Released flexVDI Manager v3.0.4

Changelog from flexVDI Manager v3.0.3

  • Added globally unique desktop policy parameters: such a parameter will generate values that are unique among all the guests of the platform, not only the desktop policy it applies to.
  • Allow multiple values of the desktop policy attribute. Now, you do not need to write all the desktop policies for a user in a comma-separated list.
  • Fixed image creation task to avoid timing out too soon. This could happen with images created on filesystems that do not support the fallocate operation (CIFS, NFS, …)
  • Fixed destroying VDI sessions when the desktop’s guest was in a transitory unknown state.