DK101010 commented on a change in pull request #4630:
URL: https://github.com/apache/cloudstack/pull/4630#discussion_r568435815
##########
File path:
plugins/hypervisors/vmware/src/main/java/com/cloud/hypervisor/vmware/resource/VmwareResource.java
##########
@@ -1959,15 +1959,15 @@ protected StartAnswer execute(StartCommand cmd) {
}
// Check for hotadd settings
-
vmConfigSpec.setMemoryHotAddEnabled(vmMo.isMemoryHotAddSupported(guestOsId));
+
vmConfigSpec.setMemoryHotAddEnabled(vmMo.isMemoryHotAddSupported(guestOsId) &&
Boolean.parseBoolean(vmSpec.getDetails().get(VmDetailConstants.HOT_ADD_MEMORY)));
Review comment:
Hi @DaanHoogland, At first I thought it also. But this method will be
called each time when you start a vm and each time will be update the vm config
spec. Btw. you can find in VmwareHelper in method setBasicVmConfig similar
logic to enable/disable hot add but it will be override from this method. I
find it also a little bit strange and perhaps it have refactoring potential.
But currently I have not so much time and knowledge to do it. Independent from
this, I tested the code to enable and disable hot add for cpu and memory and it
works like expected. I checked it also in VCenter if it enabled/disabled.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
