Disk Pools Overview
Disk pools provide storage for your virtual machines. Each pool contains one or more logical disks, and virtual machine disks are created within a pool.
How Disk Pools Work
A disk pool is a group of one or more logical disks on your server. In most environments, these are virtual disks presented by a hardware RAID controller.
When you create a virtual machine and add a virtual disk, that disk is placed in a disk pool. If the pool contains multiple disks, the virtual disk is stored on one of them — disk pools do not mirror or stripe data across disks.
Disk pools in Gallium Standalone do not provide redundancy. If a disk in a pool fails, any virtual machines stored on that disk will be lost. Use your server's RAID controller to provide hardware-level redundancy for the disks in each pool.
System Pool
The installer automatically creates a System Pool on the installation disk. This pool is used for Gallium's internal data and can also be used to store virtual machines.
For production workloads, it is recommended to create additional disk pools on separate disks to keep VM storage off the system disk. The System Pool cannot be renamed.
Default Pool and Template Pool
Each deployment has two special disk pool designations:
Default Disk Pool — When creating a virtual machine, new virtual disks are placed in the default pool unless you select a different pool. You can change which pool is the default at any time.
Template Disk Pool — Downloaded VM templates are stored in this pool. Only one pool can serve as the template pool at a time.
See Managing Disk Pools for instructions on setting these designations.