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-10193) SystemVMs/VRs face kernel panic due to OOM on VMware
Date Tue, 19 Dec 2017 06:23:01 GMT


ASF subversion and git services commented on CLOUDSTACK-10193:

Commit 04f4baa1dc89bbaf54d5168866c1ac70cedecce3 in cloudstack's branch refs/heads/debian9-systemvmtemplate
from []
[;h=04f4baa ]

CLOUDSTACK-10193: Use other64Linux for systemvms on VMware

In default/fresh installations, the guest os type for systemvms with id=15
or Debian 5 (32-bit) can cause memory allocation issues to guest. Using
Other Linux 64-bit as guest OS systemvms get all the allocated RAM. This
avoids OOM related kernel panics for certain VRs such as rVRs, lbvm etc.

Signed-off-by: Rohit Yadav <>

> SystemVMs/VRs face kernel panic due to OOM on VMware
> ----------------------------------------------------
>                 Key: CLOUDSTACK-10193
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>             Fix For:
> An edge case, systemvms use the guest os type 15 (or Debian 32-bit) which may lead VMware
vCenter to not allocate all the RAM (default 256MB) to the guest. Via vCenter it shows that
256MB is allocated, but free -m (or cat /proc/meminfo) revealed that only 157MB was allocate
in my testing against VMware 5.5 and 6.5. The fix would be to use a more appropriate guest
os type that works for VMware 5.0+, other 64-bit Linux. We cannot use Debian7+ 64-bit as the
guest os type is not available on older vCenter.

This message was sent by Atlassian JIRA

View raw message