> On 26 Jul 2017, at 14:59, Ladislav Humenik wrote:
>
> Hallo, after engine update to 4.1.2 from 4.0.6 we have following bug
>
> *Your Future Description: *
>
> Maximum memory value is stored in |VmBase.maxMemorySizeMb| property. It is
> validated against range [/memory of VM/, /*MaxMemorySiz
Hello, thank you for fast response.
The point of changing the max_mem_size is little tricky, as we have
environments with together ~13k VMs running on top of ovirt, no kidding
:) and currently doing upgrades from 3.6 > 4.1. So we can easy set those
values to the needed ones for every VM, thats
Hallo, after engine update to 4.1.2 from 4.0.6 we have following bug
*Your Future Description: *
Maximum memory value is stored in |VmBase.maxMemorySizeMb| property. It
is validated against range [/memory of VM/, /*MaxMemorySizeInMB/], where
/*MaxMemorySizeInMB/ is one of |VM32BitMaxMemorySize
yes, max memory size is customizabe even for Blank template
On Wed, Jul 26, 2017 at 4:32 PM, Ladislav Humenik wrote:
> Hello, thank you for fast response.
>
> The point of changing the max_mem_size is little tricky, as we have
> environments with together ~13k VMs running on top of ovirt, no kid
> On 26 Jul 2017, at 16:50, Jakub Niedermertl wrote:
>
> Hello Ladislav,
>
> the function computing size of default maximum memory size is currently not
> configurable from DB.
>
> If you want it to be so please feel free to file an RFE [1].
>
> [1]: https://bugzilla.redhat.com/enter_bug.cgi
Hello Ladislav,
the function computing size of default maximum memory size is currently not
configurable from DB.
If you want it to be so please feel free to file an RFE [1].
[1]: https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
Best regards,
Jakub
On Wed, Jul 26, 2017 at 1:59 PM
6 matches
Mail list logo
