You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "prashant kumar mishra (JIRA)" <ji...@apache.org> on 2013/07/18 11:40:49 UTC
[jira] [Commented] (CLOUDSTACK-3624) system vm scaleup is failing
on vmware;java.lang.RuntimeException: Memory size after hot add must be at
least 2048MB
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712171#comment-13712171 ]
prashant kumar mishra commented on CLOUDSTACK-3624:
---------------------------------------------------
Observation
============
manually scaleup ==scaling up using vcenter
->i was able to manually scale up rhel 6.3/window 8 to Memory =1.5 GB
--->was able to manually scale up system vms to Memory =2.0GB
---->Not able to scale up sytem vm to any SO having Memory<2.0GB
Since memory hot add limit is 3 GB ,should be able to scaleup to any SO having Memory<3.00GB .But i dint see this behavior with system vm,
> system vm scaleup is failing on vmware;java.lang.RuntimeException: Memory size after hot add must be at least 2048MB
> --------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3624
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3624
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Environment: branch :master stable hypervisor: Esxi-4.2
> Reporter: prashant kumar mishra
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: Logs_DB.rar
>
>
> Steps to reproduce
> -----------------------------
> 1-Create a service offering say storage1:(cpu=500,Memory=512)
> 2-try to scale up secondary storage vm to SO storage1
> Expected
> --------------
> scaling up should be successful
> Actual
> -----------
> Scaling up failed
> Log
> -------
> 2013-07-18 17:00:01,606 WARN [cloud.vm.UserVmManagerImpl] (Job-Executor-11:job-84 = [ 71db5c27-ff25-4de0-bb86-850a89e660ac ]) Received exception while scaling
> com.cloud.utils.exception.CloudRuntimeException: Unable to scale vm due to Unable to execute ScaleVmCommand due to java.lang.RuntimeException: Memory size after hot add must be at least 2048MB.
> at com.cloud.vm.VirtualMachineManagerImpl.reConfigureVm(VirtualMachineManagerImpl.java:3283)
> at com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1211)
> at com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1084)
> at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at org.apache.cloudstack.api.command.user.vm.ScaleVMCmd.execute(ScaleVMCmd.java:92)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-07-18 17:00:01,664 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-11:job-84 = [ 71db5c27-ff25-4de0-bb86-850a89e660ac ]) Deploy avoids pods: null, clusters: null, hosts:
>
--
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