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/06/19 10:42:24 UTC

[jira] [Closed] (CLOUDSTACK-1739) VMs are getting 1 GB memory on KVM hypervisor ,when they are deployed with Service Offering having RAM >=1GB and overcommit ratio is set to some value>1

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

prashant kumar mishra closed CLOUDSTACK-1739.
---------------------------------------------

    
> VMs  are getting  1 GB memory on KVM hypervisor  ,when they are deployed with Service Offering having RAM >=1GB and overcommit ratio is set to some value>1
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1739
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1739
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: prashant kumar mishra
>            Assignee: Bharat Kumar
>            Priority: Blocker
>             Fix For: 4.2.0
>
>
> Branch "Master" ;
> Hypervisor "KVM"
> Steps to reproduce
> ---------------------------
> 1-Set  overcommit ratio to 2
> 2-Deploy a vm with service offering having RAM 5 GB
> Expected
> --------------
> VM  should be assigned  Max memory 5 GB and  Min memory 2.5 GB
> Actual
> -----------
> VMs are getting  1 GB Memory 
> DB Details
> ----------------
> ----------------
> mysql> select * from vm_instance where id = 56\G;
> *************************** 1. row ***************************
>                  id: 56
>                name: five2
>                uuid: 6eeff736-1cf5-41a2-ab32-40040c8d6660
>       instance_name: i-2-56-VM
>               state: Running
>      vm_template_id: 203
>         guest_os_id: 112
> private_mac_address: 02:00:03:ca:00:0a
>  private_ip_address: 10.1.1.142
>              pod_id: 1
>      data_center_id: 1
>             host_id: 1
>        last_host_id: 1
>            proxy_id: NULL
>   proxy_assign_time: NULL
>        vnc_password: y8Kx8ZWP8ECtYGqLefzfkdFFZ7rpvew+gN5oDee1MBc=
>          ha_enabled: 0
>       limit_cpu_use: 0
>        update_count: 4
>         update_time: 2013-03-20 10:34:06
>             created: 2013-03-20 10:32:14
>             removed: NULL
>                type: User
>             vm_type: User
>          account_id: 2
>           domain_id: 1
> service_offering_id: 12
>      reservation_id: 8701b3d0-f2c6-471c-8f37-76e1ab768ec7
>     hypervisor_type: KVM
>    disk_offering_id: 3
>                 cpu: NULL
>                 ram: NULL
>               owner: 2
>               speed: 1000
>           host_name: five2
>        display_name: five2
>       desired_state: NULL
> 1 row in set (0.00 sec)
> mysql> select * from service_offering where id = 12\G;
> *************************** 1. row ***************************
>            id: 12
>           cpu: 1
>         speed: 1000
>      ram_size: 5120
>       nw_rate: NULL
>       mc_rate: NULL
>    ha_enabled: 0
> limit_cpu_use: 0
>      host_tag: NULL
>   default_use: 0
>       vm_type: NULL
>      sort_key: 0
>   is_volatile: 0
> 1 row in set (0.00 sec)
> ERROR:
> No query specified
> [root@Rack1Pod1Host7 ~]# virsh list
>  Id    Name                           State
> ----------------------------------------------------
>  1     v-44-VM                        running
>  5     s-46-VM                        running
>  6     r-48-VM                        running
>  11    i-2-47-VM                      running
>  13    i-2-55-VM                      running
>  14    i-2-56-VM                      running
>  15    i-2-57-VM                      running
> [root@Rack1Pod1Host7 ~]# virsh dominfo 14
> Id:             14
> Name:           i-2-56-VM
> UUID:           85c6740f-4916-37d5-9288-a9f68c4ba372
> OS Type:        hvm
> State:          running
> CPU(s):         1
> CPU time:       200.4s
> Max memory:     1048576 kB
> Used memory:    1048576 kB
> Persistent:     no
> Autostart:      disable
> Managed save:   no
> Agent Log
> -----------------
> -----------------
> 2013-03-29 06:30:18,889 DEBUG [kvm.resource.BridgeVifDriver] (agentRequest-Handler-3:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh -v 1104 -p em1 -b brem1-1104 -o add
> 2013-03-29 06:30:18,907 DEBUG [kvm.resource.BridgeVifDriver] (agentRequest-Handler-3:null) Execution is successful.
> 2013-03-29 06:30:18,907 DEBUG [kvm.resource.BridgeVifDriver] (agentRequest-Handler-3:null) Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
> 2013-03-29 06:30:18,907 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-3:null) starting i-2-58-VM: <domain type='kvm'>
> <name>i-2-58-VM</name>
> <uuid>cfa1bb60-f13a-38de-9190-8bfaefd2fc5a</uuid>
> <description>CentOS 5.4 (64-bit)</description>
> <clock offset='utc'>
> </clock>
> <features>
> <pae/>
> <apic/>
> <acpi/>
> </features>
> <devices>
> <emulator>/usr/libexec/qemu-kvm</emulator>
> <interface type='bridge'>
> <source bridge='brem1-1104'/>
> <mac address='02:00:26:81:00:2f'/>
> <model type='virtio'/>
> </interface>
> <serial type='pty'>
> <target port='0'/>
> </serial>
> <graphics type='vnc' autoport='yes' listen='10.147.40.7'/>
> <disk  device='disk' type='file'>
> <driver name='qemu' type='qcow2' cache='none' />
> <source file='/mnt/431c7f9e-3728-395b-8f20-77861a4d5dd7/1af5dd3d-8b7c-418c-8283-94fa32cd0f75'/>
> <target dev='vda' bus='virtio'/>
> </disk>
> <disk  device='cdrom' type='file'>
> <driver name='qemu' type='raw' cache='none' />
> <source file=''/>
> <target dev='hdc' bus='ide'/>
> </disk>
> <console type='pty'>
> <target port='0'/>
> </console>
> <input type='tablet' bus='usb'/>
> </devices>
> <memory>-1048576</memory>
> <currentMemory>1572864</currentMemory>
> <devices>
> <memballoon model='virtio'/>
> </devices>
> <vcpu>1</vcpu>
> <os>
> <type  arch='x86_64' machine='pc'>hvm</type>
> <boot dev='cdrom'/>
> <boot dev='hd'/>
> </os>
> <cputune>
> <shares>250</shares>
> </cputune>
> <on_reboot>restart</on_reboot>
> <on_poweroff>destroy</on_poweroff>
> <on_crash>destroy</on_crash>
> </domain>
> 2013-03-29 06:30:18,909 WARN  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-3:null) Failed to start domain i-2-58-VM: XML error: current memory '1572864k' exceeds maximum '0k'
> org.libvirt.LibvirtException: XML error: current memory '1572864k' exceeds maximum '0k'
>         at org.libvirt.ErrorHandler.processError(Unknown Source)
>         at org.libvirt.Connect.processError(Unknown Source)
>         at org.libvirt.Connect.domainCreateXML(Unknown Source)
>         at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.startVM(LibvirtComputingResource.java:1054)
>         at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3092)
>         at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1149)
>         at com.cloud.agent.Agent.processRequest(Agent.java:525)
>         at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
>         at com.cloud.utils.nio.Task.run(Task.java:83)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:679)
>  

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