ChangeLog of flexVDI Client 2.2.8 for Linux

Version 2.2.8 of flexVDI Client for Linux comes with many new features and improvements. The main one is that the client is now bundled as an AppImage. As soon as you download it, it is ready to run. No need to install it, just put it into your PATH and give it execution permission. Portability has also been improved, since most dependencies are already included in the bundle. The only additional dependencies needed are the X11 and ALSA libraries.

Other relevant changes from 2.2.7:

  • FLEXVDI-1876: Improved UI flow: The user can navigate back and forth between the credentials form and the manager configuration form.
  • FLEXVDI-1952: Show inactivity timeout warning: As the inactivity timeout is about to expire, the client shows a warning message to the user.
  • FLEXVDI-1969: Automagically share clipboard with guest by default.
  • FLEXVDI-1968: Sort desktops alphabetically.
  • FLEXVDI-1965: The manager entered in the configuration form is saved to the configuration file on exit.
  • FLEXVDI-1978: Allow full keyboard navigation through UI.

Changelog of flexVDI Dashboard 2.2.12

We’ve just released flexVDI Dashboard 2.2.12.

It enables configuring a new feature in Desktop Policicy Security Attributes, that enables flexVDI guest machines to be accessed simultaneously by several different clients (requires flexVDI Agent 2.2.29 and flexVDI Manager 2.2.26).

As always, you can download the latest installer, from

ChangeLog of flexVDI Client 2.2.7 for Linux

We’ve just released version 2.2.7 of flexVDI Client for Linux. As with the client for Windows, the main change in this version is the support for applying Desktop Policy Security Attributes. Besides, it is the first flexVDI client to be based on Spice-GTK v0.29, and includes several stability improvements.

Most relevant changes from 2.2.6:

  • FLEXVDI-1869: Support Desktop Policy Security Attributes: hide UI elements and functionality of those features that have been disabled by the Desktop Policy.
  • FLEXVDI-1923: FIX: flexVDI Client for Linux closes unexpectedly when using WebSockets.
  • FLEXVDI-1940: FIX: flexVDI Client for Linux loses the input channel when using WebSockets with PING messages.
  • Update Spice-GTK from v0.28 to v0.29.

Changelog of flexVDI Dashboard 2.2.11

We’ve released flexVDI Dashboard 2.2.11.
The most important improvement is the support for viewing and editing Desktop Policicy Security Attributes (requires flexVDI Agent 2.2.28 and flexVDI Manager 2.2.25). It also corrects some minor flaws:

  • FLEXVDI-1856: Include latest console viewer in Linux version which solves caps-lock switching quickly.
  • FLEXVDI-1486: Host list is shown truncated when it is long.
  • FLEXVDI-1204: Wrong list of network devices in Guest creatino wizard after moving back and forth through the wizard.
  • FLEXVDI-1867: Support Desktop Policy attributes.

You can download the latest installer, from

ChangeLog of flexVDI Client 2.2.39 for windows

We’ve just released version 2.2.39 of flexVDI Client. The main change in this version is the support for applying Desktop Policy Security Attributes, in addition to minor improvements.

Most relevant changes from 2.2.39:

  • FLEXVDI-1868: Honour Desktop Policicy Security Attributes: hide options from the GUI that are not available according to the current security policy.
  • FLEXVDI-1892: Improve crash reporting information.
  • FLEXVDI-1889: Disabling “paste from guest to client” and enabling “paste from client to guest” at the same time does not work.

You can download the latest installer from


ChangeLog for Agent 2.2.28

We’ve just released version 2.2.28 of flexVDI Agent. The biggest change in this version is the support for applying Desktop Policy Security Attributes, in addition to minor bug fixes.

Most relevant changes from 2.2.27:

  • FLEXVDI-1682: Don’t disable PS/2 keyboard, even if not needed. Windows 7 hangs on reboot without it
  • FLEXVDI-1852: By default, disable physical disk monitor
  • FLEXVDI-1865: Implement support for applying Desktop Policy Security Attributes

You can update to the latest Agent version, by running flexvdi-config and selecting Update.

Cómo montar un cluster de flexVDI con DRBD (sin almacenamiento compartido)

Habitualmente, para montar un cluster de flexVDI, es necesario disponer de un almacenamiento compartido con disco directo (una SAN FC o SAS).

Este almacenamiento compartido se emplea para almacenar la imagen de flexVDI Manager (el orquestador de la plataforma), las plantillas de escritorio y los diferenciales de los escritorio no volátiles.

De los tres elementos mencionados, el único que genera una carga de disco significativa es el último, los diferenciales no volátiles (las plantillas de escritorio, generalmente, se encuentran cacheadas en memoria del Host, gracias al sistema de caché de flexVDI). Por tanto, si estamos pensando en montar un sistema de VDI donde la mayor parte de las escritorios van a ser de tipo volátil, podemos plantearnos prescindir del almacenamiento compartido, sustituyéndolo por un sistema de almacenamiento definido por software, como DRBD.


FollowMe Printing en flexVDI

En flexVDI nos esforzamos por mejorar la experiencia de usuario en virtualización de escritorios. Una de las últimas funcionalidades en las que hemos estado trabajando últimamente, y que estará pronto disponible, es FollowMe Printing: compartición de impresoras del cliente con el escritorio virtual. (more…)

Enabling HYP mode on the Raspberry Pi 2

The newest iteration of the wonderful machine designed by Raspberry Pi Foundation, the Raspberry Pi 2, sports a Broadcom BCM2836 SoC, with four Cortex-A7 cores. The Cortex-A7, being the little brother Cortex-A15, features the ARM Virtualization Extensions, so both Xen and KVM based virtualization should work on it.

At this point, you probably are wondering why would someone want to use virtualization on a RPi2. In addition to the usual “because you can!” answer, there’s a pretty good reason for it. Imagine you want to use the RPi2 as a media center and, at the same time, you want to run some personal services (like ownCloud or Pydio) on it. Instead of polluting the media center image, you can run an isolate, secure, virtual machine for such purpose. And, using my VEXPRESS_KVM port, you can even provide those services running NetBSD! 😉

The first step towards being able to use virtualization on the Raspberry Pi 2, is finding a way to boot the kernel in HYP mode. Let’s see how can we do that.