cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "prashant kumar mishra (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-2454) system vm "memory-actual" is not getting changed after scaleup system vm
Date Mon, 13 May 2013 09:11:18 GMT
prashant kumar mishra created CLOUDSTACK-2454:
-------------------------------------------------

             Summary:  system vm "memory-actual" is not getting changed after  scaleup system
vm
                 Key: CLOUDSTACK-2454
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2454
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server, XenServer
    Affects Versions: 4.2.0
            Reporter: prashant kumar mishra
             Fix For: 4.2.0


memory-actual  of system vms are not getting changed  after scaling up.

Steps to reproduce
---------------------------
1-create system vm service offering  {say cp2 with cpu=1000mzh ram=2048MB}
2-scaleup cpvm 

Expected
-----------------
After scale up cpvm memory-actual should also change to new value

Actual
----------
memory-dynamic-max and memory-dynamic-min got changed to new value but memory-actual remain
unchanged


My observation
----------------------
1-After restart memory-actual got changed to new value
2-memory actual is getting changed for user vm with scale up 

Snippet of MS log
----------------------------

2013-05-13 09:57:18,650 DEBUG [agent.transport.Request] (catalina-exec-17:null) Seq 5-1401815077:
Sending  { Cmd , MgmtId: 7635042566263, via: 5, Ver: v1, Flags: 100111, [{"ScaleVmCommand":{"vm":{"id":1,"name":"v-46-VM","cpus":1,"speed":1000,"minRam":2048,"maxRam":2048,"rebootOnCrash":false,"enableHA":false,"limitCpuUse":false},"vmName":"v-46-VM","cpus":1,"speed":1000,"minRam":2048,"maxRam":2048,"wait":0}}]
}
2013-05-13 09:57:18,655 DEBUG [agent.transport.Request] (catalina-exec-17:null) Seq 5-1401815077:
Executing:  { Cmd , MgmtId: 7635042566263, via: 5, Ver: v1, Flags: 100111, [{"ScaleVmCommand":{"vm":{"id":1,"name":"v-46-VM","cpus":1,"speed":1000,"minRam":2048,"maxRam":2048,"rebootOnCrash":false,"enableHA":false,"limitCpuUse":false},"vmName":"v-46-VM","cpus":1,"speed":1000,"minRam":2048,"maxRam":2048,"wait":0}}]
}
2013-05-13 09:57:18,656 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-15:null) Seq
5-1401815077: Executing request
2013-05-13 09:57:19,156 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-15:null) scaling
VM v-46-VM is successful on host com.xensource.xenapi.Host@dc0eeeb1
2013-05-13 09:57:19,157 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-15:null) Seq
5-1401815077: Response Received:


vm detail on xen
------------------------
[root@Rack1Pod1Host7 bin]# xe vm-list params=all uuid=a74880a7-c226-71fa-6185-14481afcecf8
|grep mem
                 memory-actual ( RO): 1073741824
                 memory-target ( RO): <expensive field>
               memory-overhead ( RO): 101711872
             memory-static-max ( RW): 8589934592
            memory-dynamic-max ( RW): 2147483648
            memory-dynamic-min ( RW): 2147483648
             memory-static-min ( RW): 134217728
               recommendations ( RO): <restrictions><restriction field="memory-static-max"
max="34359738368" /><restriction field="vcpus-max" max="16" /><restriction property="number-of-vbds"
max="7" /><restriction property="number-of-vifs" max="7" /></restrictions>
                        memory (MRO): <not in database>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message