[
https://issues.apache.org/jira/browse/CLOUDSTACK-7591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712976#comment-14712976
]
Alireza Eskandari commented on CLOUDSTACK-7591:
-----------------------------------------------
I found the reason.
Problem originated from wrong data in "guest_os" table. For example (in CS
4.5.2) when you use "CentOS 6 (64-bit)" with id of 249 as your OS on VMWare,
you can't find related record in "guest_os_hypervisor" table for VMWare.
(guest_os_id column with value of 249 is only mapped to Xenserver but there is
no record for VMWare) so VMWare consider this vm as "otherGuest".
The above problem is the reason of 2 other problems:
1- You can't do dynamic scale on this vm because vmware sets maximum hotadd
memory limit equal to its actual amount of RAM. ("otherGuest" aren't
dynamically scalable)
2- The request for mounting "vmware-tools.iso" on this vm fails. ("otherGuest"
doesn't have vmware-tools).
Thanks
> Dynamic scaling doesn't work in CloudStack 4.4 with vmware
> ----------------------------------------------------------
>
> Key: CLOUDSTACK-7591
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7591
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, VMware
> Affects Versions: 4.4.0, 4.5.0
> Reporter: Alireza Eskandari
> Priority: Critical
> Labels: 4.4, dynamic, scaling, vmware
> Attachments: acs45.log, log.txt
>
>
> In cloudstack 4.4 with vSphere 5.5, I create a CentOS 6 instance with dynamic
> scalability enabled with this resources:
> RAM: 512MB , CPU:1 core - 500MHz
> After I scale this instance to below resources I got "Failed to scale the VM":
> RAM: 1024MB , CPU:1 core - 1000MHz
> I don't face with above issue in cloudstack 4.3
> ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-116:ctx-abd65263 10.10.171.156)
> Unexpected exception:
> com.cloud.utils.exception.CloudRuntimeException: Memory of VM i-2-14-VM
> cannot be scaled to 1024MB. Requested memory limit is beyond the hotadd
> memory limit for this VM at the moment is 512MB.
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:1261)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:471)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
