[ https://issues.apache.org/jira/browse/CLOUDSTACK-10193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299818#comment-16299818 ]
ASF subversion and git services commented on CLOUDSTACK-10193: -------------------------------------------------------------- Commit 52ae714e16ce351a5d16c607cf0b023f63142372 in cloudstack's branch refs/heads/debian9-systemvmtemplate from [~rohit.ya...@shapeblue.com] [ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=52ae714 ] 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 <rohit.ya...@shapeblue.com> > SystemVMs/VRs face kernel panic due to OOM on VMware > ---------------------------------------------------- > > Key: CLOUDSTACK-10193 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10193 > 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: 4.11.0.0 > > > 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 (v6.4.14#64029)