...
A: The flexVDI Manager performs resource allocation at boot time, or manually when you issue a rebalance operation. It will iterate over all pools in priority order, and allocate part of the resources of each host to them until all their requirements are fulfilled. This allocation will not change unless explicitly requested, which ensures that higher priority pools always have enough resources for their guests, but leads to some curious situationsituations. For instance, suppose there is a flexVDI cluster with two hosts, A and B, with 8 GB of RAM each. A pool is configured on both hosts which requires 8 GB of RAM. The manager decides to allocate 4 GB on each host for this pool, so there are other 4 GB free on each one. You run a first guest that requires 4 GB of RAM, and the Manager decides to start it on host A. Then, any other guest of the pool will always run on host B, even if host A is its preferred host, because all the resources of host A allocated to the pool are already being used by the first guest, even though it still has 4 GB of free RAM.
...
And the flexVDI Host will update its device list without disturbing end users or virtual machines. The information will be automatically propagated to flexVDI manager and flexVDI dashboard in some seconds.
Q: Can I install all flexVDI software in virtual machines?
A: No. flexVDI is a virtual machine hypervisor, and cannot be installed inside a virtual machine. You have to install it in a physical server.