fix(v2v): computation of memory_static_max (#7971)

Introduced by ad1bf3b The max memory that can be assigned to a VM is not correctly passed by the v2v import
vatesfr · Sep 9, 2024 · 2f7e0d0 · 2f7e0d0
1 parent 01c7141
commit 2f7e0d0
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 0 deletions.
diff --git a/CHANGELOG.unreleased.md b/CHANGELOG.unreleased.md
@@ -16,6 +16,7 @@
 - [REST API] Add `pifs` and `vm-controllers` collections
 - [REST API/Dashboard] Add name and type of the backup in the backup job issues (PR [#7958](https://github.com/vatesfr/xen-orchestra/pull/7958))
 - [Perf-alert] Display warning if no guest tools are detected while monitoring VM memory (PR [#7886](https://github.com/vatesfr/xen-orchestra/pull/7886))
+- [V2V] Fix computation of `memory_static_max`
 
 ### Bug fixes
 

diff --git a/packages/xo-server/src/xo-mixins/vmware/index.mjs b/packages/xo-server/src/xo-mixins/vmware/index.mjs
@@ -38,6 +38,7 @@ export default class MigrateVm {
           ...OTHER_CONFIG_TEMPLATE,
           memory_dynamic_max: memory,
           memory_dynamic_min: memory,
+          memory_static_max: memory,
           // allow the user to reduce the memory of this VM to the limit set by the template
           memory_static_min: template.memory_static_min,
           name_description: `from esxi -- source guest id :${guestId} -- template used:${template.name_label}`,