I once had a doctor who told me that a wise professor of his told him that if he would listen to his patients, they would tell him what the ptoblem was 80% of the time, and that if he would continue listening, 95% of that 80% would tell him what to do about it. You seem to have been listening to yourself :-)
Regards, Richard Schuh ________________________________ From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Tuesday, October 16, 2007 8:34 AM To: [email protected] Subject: Re: Omegamon XE for z/VM and storage definitions I hate it when I think of an answer my own questions as I type them, and then hit send anyway. Changing the size of the guest from 512m to 528m and restarting solved the problem. The segment does indeed have to match the top of the guest's memory. -- .~. Robert P. Nix Mayo Foundation /V\ RO-OE-5-55 200 First Street SW / ( ) \ 507-284-0844 Rochester, MN 55905 ^^-^^ ----- "In theory, theory and practice are the same, but "Join the story... Ride Ural." in practice, theory and practice are different." ------ Forwarded Message I'm in the process of installing Omegamon XE for z/VM and Linux, and I've gotten to the point of defining the DCSS to the linux guest serving as the monitor collection agent. I defined the Linux guest having 512m of memory. I defined the perfout dcss with "DEFSEG 21000-210FF SN", which, I think, should be from 528M - 529M. I added "mem=768m" to the zipl parameter line and reran mkinitrd and zipl. I did the "modprobe dcssblk" to install the driver. I then did "echo perfout > /sys/devices/dcssblk/add", and the response is as follows: tvmpzl01:/sys/devices/dcssblk # echo perfout > add -bash: echo: write error: Numerical result out of range Obviously, I've missed something. Does the segment need to be immediately adjacent to the top of the guest's virtual memory? Or can the definition leave some space between the two, as above? What other problems can be encountered? The 2.6 device drivers manual documents the dcssblk driver, but includes no indication of what errors can be encountered or what messages might be generated. Any help, or nudges in the right direction, would be appreciated.
