You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "prashant kumar mishra (JIRA)" <ji...@apache.org> on 2013/07/10 14:01:52 UTC

[jira] [Commented] (CLOUDSTACK-3446) Guest OS is getting memory=memory in SO / memory.overcommit.ratio on kvm host even there is no contention

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

prashant kumar mishra commented on CLOUDSTACK-3446:
---------------------------------------------------

these link may help

1-http://blog.braastad.org/?p=211
2-https://lists.fedorahosted.org/pipermail/vdsm-devel/2012-October/001554.html
3-http://www.redhat.com/archives/virt-tools-list/2011-January/msg00001.html
4-http://humblec.com/memory-ballooning-and-virtio_balloon-driver-in-qemu-kvm/
                
> Guest OS is getting memory=memory in SO / memory.overcommit.ratio on kvm host even there is no contention
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3446
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3446
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>         Environment: branch: master-stable, hypervisor :KVM
>            Reporter: prashant kumar mishra
>             Fix For: 4.2.0
>
>         Attachments: Logs_DB.rar
>
>
> Steps to reproduce
> ---------------------------
> 1-prepare  CS setup with kvm
> 2-set  memory overcommit ratio to 2
> 3-deploy a vm with medium service offering(ram=1024MB, cpu=1000)
> 4-run cat /proc/meminfo on guest OS
> Expected
> --------------
> since there is no contention Guest OS should get   1024 MB
> Actual
> -------------
> Guest OS is getting 512 MB even there is no contention on host
> My observation
> ----------------------
> ----------------------
> On KVM host
> virsh # dominfo 7
> Id:             7
> Name:           i-2-5-VM
> UUID:           ebe3a215-3893-4edd-97c0-0ad4e0793359
> OS Type:        hvm
> State:          running
> CPU(s):         1
> CPU time:       45.8s
> Max memory:     1048576 kB
> Used memory:    524288 kB
> Persistent:     no
> Autostart:      disable
> Managed save:   no
> On Guest VM
> -----------------------
> cat /proc/meminfo 
> MemTotal: 524288
> ->Guest os gets memory=used memory on host(can be checked using "dominfo ")

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira