It's very important to look at it first from the total IFL perspective. What is the total IFL utilization? Then break that down by LPAR. If 100% of your IFLs are in use, and one LPAR is using 60% of the IFL resource and the other LPAR is using 40% of the IFL resource, then it's a matter of prioritizing the workload. Relative share of 100 means there is no prioritization assigned. If the guests need more CPU, then they need a larger share. If the LPAR needs more CPU, it needs a larger weight...
On 2/1/2018 9:47 AM, Victor Echavarry wrote:
We have a situation that a couple of guest has CPU stealing and when we checking the LPAR, the IFL have available CPU for processing. What could be possible? The guest sharing are based on CPU assigned, for example a guest with 1 CPU has 100 relative share and a 2 CPU has 200 relative share. We are running under z/VM 6.4 and the SLES is 11SP4. Regards, Victor Echavarry System Programmer Operating Systems EVERTEC, LLC ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
