cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9690) Scale CentOS7 VM fails with error
Date Tue, 16 May 2017 05:55:04 GMT


ASF subversion and git services commented on CLOUDSTACK-9690:

Commit e7a7db3ef316bff63b0f0f341bcb6b3f9e29e76e in cloudstack's branch refs/heads/master from
[;h=e7a7db3 ]

CLOUDSTACK-9690: Scale CentOS7 VM fails with error

1. Removed XenServerGuestOsMemoryMap from
This java file was holding a static in memory map named XenServerGuestOsMemoryMap. This was
the source for xenserver dynamic memory values(max and min). These values were moved to guest_os_details

2. DAO layer was modified to access these values.
3. VirtualMachineTo object was modified to populate the dynamic memory values.
4. addGuestOs and UpdateGuestOS api has been modified to update memory values.

> Scale CentOS7 VM fails with error 
> ----------------------------------
>                 Key: CLOUDSTACK-9690
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions:
>            Reporter: Sudhansu Sahu
>            Assignee: Sudhansu Sahu
> Scale CentOS7 VM fails with error "Cannot scale up the vm because of memory constraint
> When creating VM from CentOS 7 template on the XenServer with dynamically scaling enabled,
instance starts with base specified memory instead of memory * 4 as static limit.
> As the result, attempt to scale VM throws error in MS log:
> {noformat}
> java.lang.RuntimeException: Job failed due to exception Unable to scale vm due to Catch
exception when scaling VM:i-24-3976-VM due
to Cannot scale up the vm because of memory
constraint violation: 0 <= memory-static-min(2147483648) <= memory-dynamic-min(8589934592)
<= memory-dynamic-max(8589934592) <= memory-static-max(2147483648)
> {noformat}
> =============================
> # Enable dynamic scaling in Global settings
> # Register an CentOS 7 tempplate(with tools) and tick dynamic scaling
> # Deploy VM with this template
> # Start the VM and try to change service offering
> EXPECTED RESULT: VM should start with static limit 4x<assigned memory> and scale
up when offering is changed
> ACTUAL RESULT: VM starts with maximum static limit of <assigned memory> and doesn't
scale up with error in ms log :
> Cannot scale up the vm because of memory constraint violation: 

This message was sent by Atlassian JIRA

View raw message