Usually, default settings are fit for everyone, but sometimes flexVDI components must be further configured to your needs. flexvdi-config is the main configuration utility, but not-so-common options can be set through various configuration files.

flexVDI Agent

The flexVDI Agent is configured by editing the file /etc/flexvdi/flexvdi-agent.conf. Editing it will automatically reload the flexvdi-agent service, so you do not need to do it explicitly. This is an INI-formated text file that configures the CherryPy engine. Values are integers, booleans or strings. For boolean values, casi-insensitive values "true", "yes" and 1 all mean true, and anything else means false. The configuration file also contains the following flexVDI-specific sections:


When the flexVDI Agent is also in charge of keeping the flexVDI Manager instance up and running, it uses another configuration file at /etc/flexvdi/flexvdi-agent-watchdog.conf. It must contain a JSON object with information on how to check that the flexVDI Manager instance is alive, and restart it when needed. This file is created and maintained automatically when the Manager is installed, upgraded or moved to a different volume, so you should not need to modify it.

The following keys are recognized, and all of them are mandatory (no default values):

Log files

Log messages are output to /var/log/flexvdi/flexvdi-agent.log, as configured in the flexvdi-agent.conf file. This file is rotated every 10MB and the last 10 files are kept. Besides, since Libvirt is used to manage virtual machines, you should also check the files in directory /var/log/libvirt. In particular, a log file is created for each virtual machine in the /var/log/libvirt/qemu directory. Although they use very small space, their number can grow quite fast if you use volatile desktops. Keep an eye on this directory to delete the log files of virtual machines that you do not need anymore.

flexVDI Manager

The flexVDI Manager instance is a virtual machine running CentOS 6.9, with the flexvdi-manager service and a mongodb database. You can log into this virtual machine with SSH, user root and the Manager password you have configured with flexvdi-config (the password is flexvdi by default).

This virtual machine's storage consists of two disk images. The first one, vda, contains one partition with the operating system and the binary code of flexvdi-manager and mongodb. It is replaced every time you upgrade the Manager version, so everything you install to this disk will be deleted.

The second one, vdb, contains two partitions. The first one is mounted in /flexvdi/external with the following directories:

The second partition is mounted in /flexvdi/external/log and contains the log files for the flexvdi-manager and mongodb services.


The configuration file for the flexvdi-manager service is /flexvdi/external/manager/application.conf. It configures the Play and Akka Frameworks, so it uses de HOCON file format. It also includes a set of properties for flexVDI features.

Do not change Play and Akka configuration unless you know what you are doing.

The flexVDI properties are:

Log files

The flexVDI Manager's log files are stored in /flexvdi/external/log/manager.*.log. The MongoDB log files are also stored in /flexvdi/external/log/mongod.log.

The logging configuration resides in the file /flexvdi/etc/flexvdi-manager-log.xml. It is an XML log file that configures Logback, check its documentation for details. By default, up to INFO log level is recorded, and the log files are rotated every day and every 20 MB, keeping 15 days worth of logs and 4GB at most. Two main loggers exist:

If you need additional messages to be recorded, set the DEBUG level in the correct logger and restart the flexvdi-manager service.

Take into account that the log configuration file resides in the first disk image. If you modify it, your changes will be deleted when you upgrade the Manager.