[
https://issues.apache.org/jira/browse/CLOUDSTACK-7737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176740#comment-14176740
]
Devdeep Singh commented on CLOUDSTACK-7737:
-------------------------------------------
I spoke to Chandan and had a look at his setup.
Hyper-v agent is assigning the right memory to the vm. Even running a
powershell command is reporting the expected memory
PS C:\Users\Administrator.XSQA> Get-VMMemory i-36-59-VM
VMName DynamicMemoryEnabled Minimum(M) Startup(M) Maximum(M)
------ -------------------- ---------- ---------- ----------
i-36-59-VM False 512 512 512
PS C:\Users\Administrator.XSQA> Get-VMMemory i-2-60-VM
VMName DynamicMemoryEnabled Minimum(M) Startup(M) Maximum(M)
------ -------------------- ---------- ---------- ----------
i-2-60-VM False 1024 1024 1024
Here the first VM is the one created by automation run and the second one is
the one I created with a Medium service offering. The default CentOS template
created for hyper-v is enabled with GUI. Maybe the memory is being used by
video ram. On my local setup I created an instance with GUI and reported of 494
MB for a Small service offering when I checked in /proc/meminfo inside the VM.
So I don’t think it is an issue here.
> [Automation] [HyperV] Deployed VM is not respecting the memory configuration
> specified in the service offering
> --------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-7737
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7737
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
> Affects Versions: 4.5.0
> Reporter: Chandan Purushothama
> Assignee: Devdeep Singh
> Priority: Critical
> Fix For: 4.5.0
>
>
> Deployed VM has the following memory configuration on the VM:
> [root@Atoms-VM-2 ~]# cat /proc/meminfo | grep Mem
> MemTotal: 363416 kB
> MemFree: 81864 kB
> [root@Atoms-VM-2 ~]#
> Which is around 354.8984375 MB
> But the Service Offering specified specifies 512 MB as shown below:
> mysql> select id,name,instance_name,state,service_offering_id from
> vm_instance where id=59 \G
> id: 59
> name: Atoms-VM-2
> instance_name: i-36-59-VM
> state: Running
> service_offering_id: 1
> 1 row in set (0.00 sec)
> mysql> select * from service_offering where id=1 \G
> id: 1
> cpu: 1
> speed: 500
> ram_size: 512
> nw_rate: NULL
> mc_rate: NULL
> ha_enabled: 0
> limit_cpu_use: 0
> host_tag: NULL
> default_use: 0
> vm_type: NULL
> sort_key: 0
> is_volatile: 0
> deployment_planner: NULL
> 1 row in set (0.00 sec)
> mysql>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
