[jira] [Comment Edited] (CLOUDSTACK-10193) SystemVMs/VRs face kernel panic due to OOM on VMware

["Paul Angus (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-10193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16294046#comment-16294046 ] 

Paul Angus edited comment on CLOUDSTACK-10193 at 12/17/17 9:10 AM:
-------------------------------------------------------------------

[~bhaisaab]

we could consider a special OS type of SystemVM and create the correct/best mappings for each hypervisor and version thereof in the guestos table.


was (Author: paulangus):
[~bhaisaab]
I can't find PR to comment on.
[please include so i can comment in-line]

we could consider a special OS type of SystemVM and create the correct/best mappings for each hypervisor and version thereof in the guestos table.

> 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)