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 flexvdi.com

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 flexvdi.com

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 flexvdi.com

 

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.

ChangeLog for Manager 2.2.25

We’ve just released version 2.2.25 of flexVDI Manager. The biggest change in this version is the addition of Security Attributes as an extension of Desktop Policy. This allows you to selectively disable some features (USB redirection, Copy&Paste, Power Events…) on your VDI Desktops, to increase the security and isolation of every Guest.

Most relevant changes from 2.2.22:

    • FLEXVDI-1520: Add a new CPU emulation mode (AMD Opteron_G6)
    • FLEXVDI-1523: Allow to choose between PS/2 and USB keyboard mode
    • FLEXVDI-1827: Detect when an Active Directory account password has expired, and let it login to change password
    • FLEXVDI-1865: Implement support for Security Attributes on Desktop Policy

You can update to the latest Manager version, by running flexvdi-config and selecting Manager->Upgrade.

Buggy transparency effect in windows 7 taskbar

Transparency, taskbar, and high CPU usage

Lately I have been using flexVDIClient full time, and I have noticed that the fan in my PC turned into high speed frequently, due to CPU usage. So I investigated the issue, expecting I could find a way to optimize the program. What I found was quite unexpected, though.

First I will describe my setup: my computer is a Windows 7 laptop with a 1366×768 screen, and an additional 1920×1080 monitor in the right side. GPU is an Intel HD Graphics 4000, and the processor is an Intel i5.

My favorite layout is using the full big screen in the right side for a flexVDIClient connected to the console of one of my VM´s, and the small one for messaging, email… The windows taskbar is in the bottom of the left screen, where I can see the notifications.

My desktop looks like this:

desktop-1

First Observations:

Initially I found that when flexVDIClient was full screen, the global cpu usage (4 cpu threads) was around 45%, with “System“ as the main CPU consumer. As soon as I closed flexVDIClient, the cpu felt down to 14%, so it looked like  flexVDIClient was the problem. Then I started playing with it.

flexVDIClient´s main task is showing images of the remote console of a virtual machine, so the amount of computations per second it has to do depends on the amount of pixels it has to move to the local display. So my first tests involved resizing the client: when I made flexVDIClient only slightly smaller than the full screen, CPU usage went down to 20%, which looked quite good. Maybe it wasn´t flexVDIClient´s fault after all.

Window positioning seems to be the key

After changing the windows size, without affecting too much to CPU usage, I had to try something else. Then I started moving the window, and I noticed the following:

Let “x” be the distance (in pixels) from the left border of the big screen to the left border of flexVDIClient, with negative values indicating that part of the window is in the left screen:

x (windows position)

Total CPU use

-100, -4, -2, 0, 1, 2

45%

3, 4, 5

35%

> 6

15-18%

What?!

When flexVDIClient window is “close” to the left screen, up to 5 pixels away, CPU usage (by the “System” process) is high. But if all the window is inside the left screen, CPU usage is low again.

Taskbar transparency

I went on testing possible factors.
I found that it was not window position itself, but window position relative to Windows taskbar what caused the problem. If I moved the taskbar to the left side or to the top of the left screen, so that the window was not behind the taskbar, the high CPU usage disappeared.
But it is not the full taskbar what caused the problem. Just the “show desktop button” in the right side of the taskbar. And not even the whole button: the bottom part of this button does not present this effect. But a small area to the right (remember those 5 pixels in the table?) and to the left of this button does.

And if I put the big monitor with flexVDIClient left to the small screen with the taskbar, then CPU usage is high when flexVDIClient is next to the “Start button”. Go figure.
Transparency must be present too. If I disable transparency, CPU usage goes down.

Conclusions:

There seems to be a bug in Windows 7 when applying transparency around the left and right borders of the taskbar, at least on my machine. But there is not much I can do about it.

In general terms, transparency effects can cost a lot of CPU. I have seen more than 20% of my i5 continuously dedicated to transparency during these tests. If you want performance, disabling visual effects can give the machine a noticeable amount of extra power. Disabling “Use visual styles on windows and buttons”  makes the trick too, as it does disabling “Visual Glass style”, or any other option in windows that removes transparency. You can find several of them under “Visual effects configuration”.

In the end I came up with a workaround. Now my Desktop is arranged like this:

desktop-2

Now the taskbar (bottom of the left screen) is below the right screen. So its sides do not “interfere” with the windows in the right screen, and CPU usage is normal again.

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

flexvdi+drbd
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.

(more…)

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…)