HyperVDsc icon indicating copy to clipboard operation
HyperVDsc copied to clipboard

Published 20 hours ago • verified publisher icon dsccommunity

VMHyperV: Update to support higher 2016 memory limits

Open bgelens opened this issue 7 years ago • 0 comments

Currently xVMHyperV bounds the amount of memory specified by having the [ValidateRange()] attribute on the parameters:

  • StartupMemory
  • MinimumMemory
  • MaximumMemory

Since limitations differ from OS version to OS version, this needs to change to a validation mechanism within the functions based on the OS version where the resource is used. This needs to be done to avoid having unnecessary constraints on usage of the resource on newer OS versions.

To make this clear to the end-user, the readme should be updated to explain that the behavior is a per platform version limit and the description in the schema should make users aware as well.

Limit docs:

bgelens avatar Jun 14 '17 06:06 bgelens