[Users] how to temporarily solve low disk space problem preventing start of VM

[Gianluca Cecchi]

On Tue, Jan 7, 2014 at 4:08 PM, Gadi Ickowicz  wrote:
> Hi,
>
> The low disk space is controlled by a parameter in the engine called FreeSpaceCriticalLowInGB, and can be configured using the cli tool engine-config.
>
> you should be able to set it to something like 4 GB or maybe 3GB so you can start your vms with the following command:
>
> engine-config -s FreeSpaceCriticalLowInGB=3
>
> After doing this you have to restart the engine service (service ovirt-engine restart) for the changes to take effect.
>
> If you want to see what the current value is use engine-config -g FreeSpaceCriticalLowInGB.
>
>
> To see a list of all configurable values you can use engine-config --list
>
> Thanks,
> Gadi Ickowicz

It did the trick, thanks!

Could this parameter impact in general only start of new VMs or in any
way also already running VMs?
Gianluca