Force even memory values for MEM attribute
|Assignee:||Abel Coronado||% Done:|
|Target version:||Release 5.4.3|
After I type wrong memory value (1027 MB) instead 1024 MB, and try instantiate new VM, I got error in vCenter (vcenter_error.png)
After check it, the vCenter/vSphere only allow values increased from 4 to 4 values, in this case the allowed values are 1028 MB or 1024 MB.
Other point is, after this problem, I tried delete the instance by Sunstone GUI (Recover/Delete). After this the instance it was deleted on Sunstone GUI, but remain on vCenter, then I needed delete it manually.
#3 Updated by Miguel Ángel Álvarez Cabrerizo over 3 years ago
- Category changed from vCenter to Core & System
- Target version changed from Release 5.2 to Release 5.4
First part of the issue has been reproduced. VM fails to boot due to "GenericVmConfigFault: Memory (RAM) size (257) is invalid." This issue is not only related with vCenter so category has been changed.
Sunstone allows to use an odd number for RAM memory so it would be a good idea to check that value before submitting. As RAM memory may be a multiple of 2 MB or 4 MB depending on the hypervisor and architecture (see discussion http://serverfault.com/questions/771922/allocating-non-standard-memory-quantities-to-virtual-machines) forcing the number to be only a multiple of 4 wouldn't be appropiate. So the odd number check would be the right path. Also Core support for this feature should be added when selecting RAM memory for CLI users.
The second part of the issue already has a ticket assigned: http://dev.opennebula.org/issues/4648