You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a VM is started before setting the global var enable.dynamic.scale.vm to true, scaling is not possible on the specific VM until it is stopped and started again. Setting the global var before starting the VM solves the problem. The template also needs dynamic scaling enabled. But after checking those variables the VM instance would still fail due to the default max vCPUs being set to 16.
Spaceman1984
changed the title
Added global var before scaling VM
Enabled dynamic scaling before starting a VM for Marvin VM scaling test
Nov 5, 2020
Spaceman1984
changed the title
Enabled dynamic scaling before starting a VM for Marvin VM scaling test
Enabled dynamic scaling before starting a VM for Marvin VM scaling test on Xenserver
Nov 5, 2020
Spaceman1984
changed the title
Enabled dynamic scaling before starting a VM for Marvin VM scaling test on Xenserver
Fixed VM scaling test on Xenserver
Nov 11, 2020
Hello @rohityadavcloud
We still have this issue with ACS 4.16.0 and Xcp-NG 8.2
Could it be possible to have a fix or a tweak to allow bypass "memory-static-max" constraint violation moreover of the xen max vcpu ?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
If a VM is started before setting the global var enable.dynamic.scale.vm to true, scaling is not possible on the specific VM until it is stopped and started again. Setting the global var before starting the VM solves the problem. The template also needs dynamic scaling enabled. But after checking those variables the VM instance would still fail due to the default max vCPUs being set to 16.
Fixes: #4237
Types of changes
Screenshots (if appropriate):
How Has This Been Tested?
Run the Marvin test - scaling works fine.