Am 23/10/2024 um 11:56 schrieb Fiona Ebner:
> Maybe we could have (datacenter-wide?) default profiles (one for
> containers, one for VMs) whose values are used for new guest creation?
> Users could modify them if desired and they could also be used to
> pre-fill values in the UI. Could then be ship
Am 22.10.24 um 15:35 schrieb Thomas Lamprecht:
> Am 22/10/2024 um 14:15 schrieb Maximiliano Sandoval:
>> Thomas Lamprecht writes:
>>
>>> And even then, would this still break restoring backups made before that
>>> change?
>>> If, this would fall under the changes that need versioning the guest
>>>
Am 22/10/2024 um 14:15 schrieb Maximiliano Sandoval:
> Thomas Lamprecht writes:
>
>> And even then, would this still break restoring backups made before that
>> change?
>> If, this would fall under the changes that need versioning the guest
>> configs. Which naturally is possible but is IMO also
Thomas Lamprecht writes:
> And even then, would this still break restoring backups made before that
> change?
> If, this would fall under the changes that need versioning the guest
> configs. Which naturally is possible but is IMO also not something I'd
> do lightly, as that's something that migh
Am 22/10/2024 um 13:23 schrieb Fiona Ebner:
> Am 01.10.24 um 16:08 schrieb Maximiliano Sandoval:
>> This makes it so newly created VMs, e.g. with `qm create` will have the
>> same default value as VMs created via the web UI.
>>
>> Signed-off-by: Maximiliano Sandoval
>> ---
>> I am not entirely sur
Am 01.10.24 um 16:08 schrieb Maximiliano Sandoval:
> This makes it so newly created VMs, e.g. with `qm create` will have the
> same default value as VMs created via the web UI.
>
> Signed-off-by: Maximiliano Sandoval
> ---
> I am not entirely sure if there is side-effect that I am not taking into
note that the gui's default is a bit "fake". it pre-sets the field to
`x86-64-v2-AES`, but if you click the little "x" next to it, the field
will be cleared and if you submit the form like that the default ends up
being `kvm64` again. this happens because the final config file does not
specify a cp
This makes it so newly created VMs, e.g. with `qm create` will have the
same default value as VMs created via the web UI.
Signed-off-by: Maximiliano Sandoval
---
I am not entirely sure if there is side-effect that I am not taking into
account.
PVE/API2/Qemu.pm | 4
1 file changed, 4 inser
