[prev in list] [next in list] [prev in thread] [next in thread] 

List:       vdsm-devel
Subject:    [ovirt-devel] OVIRT-3.5-TEST-DAY-3: CPU SLA for capping
From:       Martin Perina <mperina () redhat ! com>
Date:       2014-09-19 7:06:34
Message-ID: 540000454.25188280.1411110394704.JavaMail.zimbra () redhat ! com
[Download RAW message or body]

Hi,

I tested the support to limit CPU utilization of hosts. Setting it up
in the GUI worked correctly, but for running VM settings are ignored.
I used XMLRPC protocol to avoid [1]. To simulate VM CPU utilization
I used stress tool [2].

Testing steps:

1. Create a VM with the same number of CPUs as Host
2. Create CPU type QoS in DC and set the limit to desired value
3. In Cluster create new CPU profile with above QoS and remove the default CPU profile
4. Start the VM and execute (N is a number of CPUs in VM)
   stress --cpu N
5. Connect to Host and execute
   sar -u 1 10


No matter what the limit was set to (1, 50, 100), host CPUs were always utilized to 100%.
So I create bug to cover this [3].

Martin Perina


[1] http://bugzilla.redhat.com/1142851
[2] http://people.seas.harvard.edu/~apw/stress/
[3] http://bugzilla.redhat.com/1144280
_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
[prev in list] [next in list] [prev in thread] [next in thread]