The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM
The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM
The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
should not be taken as good, (<strong>10</strong>0% hit ratio, when doing only 1 I/O per second is<br />
effectively meaningless).<br />
► Line 4 describes more storage (memory) management. <strong>The</strong> PAGING rate is important.<br />
Higher values will often impact per<strong>for</strong>mance. This can be at least partially offset by<br />
increasing the number of page volumes, but a more thorough examination of this problem<br />
is advisable whenever it arises.<strong>The</strong> STEAL percentage is often misleading. This is basically<br />
the percentage of pages taken from guests that z/<strong>VM</strong> believes are non-dormant. Since<br />
some guests have periodic timers going off, they appear to be active to z/<strong>VM</strong> even when<br />
relatively idle. Pages taken from these guests are still considered to be stolen. So there<br />
are scenarios where a system only has a user set comprising active guests, in which case<br />
all pages taken would be considered stolen. Bearing this in mind, if a high STEAL value is<br />
observed, the paging rate needs to be checked. If the paging rate is relatively low, then<br />
the STEAL value is not important.<br />
► On lines 5 through 8 you also see a series of counters that represent the users in<br />
various queues. <strong>The</strong> z/<strong>VM</strong> scheduler classifies work into 3 different classes (1 through 3)<br />
and a special additional class labelled zero. So the Column of Qx values and Ex represent<br />
the virtual machines in the dispatch list and the eligible list. <strong>The</strong> most important value here<br />
to validate is that there are no virtual machines in the Eligible list: E1, E2, E3; this implies<br />
z/<strong>VM</strong> has stopped dispatching some virtual machines to avoid over committing resources.<br />
Such a system would require further investigation, possibly leading to some tuning work,<br />
or even hardware addition in extreme cases. Do not worry about the values in<br />
parenthesis.<br />
INDICATE QUEUES EXP<br />
Another useful command to understand the state of the system is the INDICATE QUEUES EXP.<br />
Following is an example:<br />
==> ind q exp<br />
DATAMGT1 Q3 AP 00000537/00000537 .... -2.025 A02<br />
BITNER Q1 R00 00000785/00000796 .I.. -1.782 A00<br />
EDLLNX4 Q3 PS 00007635/00007635 .... -1.121 A00<br />
TCPIP Q0 R01 00004016/00003336 .I.. -.9324 A01<br />
APCTEST1 Q2 IO 00003556/00003512 .I.. -.7847 A01<br />
EDLWRK20 Q3 AP 00001495/00001462 .... -.6996 A01<br />
EDL Q3 IO 00000918/00000902 .... -.2409 A01<br />
EDLWRK11 Q3 AP 00002323/00002299 .... -.0183 A00<br />
EDLWRK18 Q3 IO 0000<strong>10</strong>52/00000388 .... -.0047 A00<br />
EDLWRK4 Q3 AP 00004792/00002295 .... .0055 A01<br />
EDLWRK8 Q3 AP 00004804/00004797 .... .0089 A02<br />
EDLWRK16 Q3 AP 00002378/00002378 .... .0170 A02<br />
EDLWRK2 Q3 AP 00005544/00002956 .... .0360 A00<br />
EDLWRK12 Q3 AP 00004963/00002348 .... .0677 A01<br />
EDLWRK6 Q3 IO 00000750/00000302 .... .0969 A02<br />
EDLWRK3 Q3 AP 00005098/00005096 .... .0999 A02<br />
EDLWRK17 Q3 AP 00004786/00004766 .... .<strong>10</strong>61 A01<br />
EDLWRK9 Q3 AP 00002372/00002334 .... .1<strong>10</strong>7 A02<br />
EDLWRK5 Q3 IO 00002376/00002376 .... .1205 A01<br />
EDLWRK14 Q3 AP 00002426/00002323 .... .1238 A02<br />
EDLLIB19 Q3 IO 00001226/00001<strong>10</strong>0 .... .1309 A02<br />
EDLWRK19 Q3 AP 00002322/00002298 .... .1705 A00<br />
EDLWRK15 Q3 AP 00002839/00002781 .... .2205 A02<br />
EDLWRK1 Q3 AP 00002969/00002935 .... .2491 A02<br />
This is another class E command and displays the virtual processors associated with a given<br />
user ID (a single virtual machine may have multiple virtual processors) what queue (dispatch<br />
list, eligible list, limit list) they are in and what state they are in. This is a snapshot in time.<br />
Again you want to check this output to make sure there are no virtual machines in the eligible<br />
Chapter 14. Monitoring and tuning z/<strong>VM</strong> and Linux 225