>>> On 1/5/2016 at 08:26 AM, Michael Holzheu <[email protected]> >>> wrote: -snip- > What about: > > You can always monitor the guest operating system where hyptop > runs.
You can always monitor the operating system where hyptop is running. > To monitor any other guest operating system on the same hypervi- > sor as the operating system instance of hyptop, you need the > following additional permissions: To monitor any other operating system(s) _running_on_the_same_hypervisor as hyptop (whether z/VM or PR/SM), you will need additional permissions. (I think underlining or italicizing the "running on the same hypervisor" will help even more.) > For z/VM, the guest virtual machine must be class B. For LPAR, > on the HMC or SE security menu of the LPAR activation profile, > select the Global performance data control checkbox. For z/VM guests, that is CP privilege class B. For systems running in an LPAR (PR/SM), use the HMC Customize/Delete Activation Profiles function to ensure the Global performance data control checkbox is checked. This can be found in the Image profile, under the Security heading. Is there any verbiage that should be added for KVM guests? I haven't tried it myself, but does hyptop work there? Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] 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/
