Thank you all for sharing experiences and for advice. It gives me
hope there may be a way around my brick wall!
Rob, page-in is what this problem feels like. But
the lpar has 6G/2G of main/xstor and the total virtual storage
of all the guests together is 3264M, of which the problem linux guest
has 2G. VM reports 0 paging.
Just to clarify, there is one ifl on the z800. The lpar is running the
regular VM service machines, two small non-load-balanced linuxes
and then this problem instance. The linux I'm talking about
is load-balanced with five standalone (not on VM)
boxes. Our vm linux instance shouldn't be running a firewall
but it's another thing I should verify.
Mark, the lpar is running z/VM 5.2 at 0601. The linux guests are
running SLES9 SP3 (64bit). The system is using Performance Toolkit.
cat /proc/meminfo shows:
MemTotal: 2050128 kB LowFree: 343412 kB
MemFree: 343412 kB SwapTotal: 475852 kB
Buffers: 143588 kB SwapFree: 475852 kB
Cached: 1128868 kB Dirty: 444 kB
SwapCached: 0 kB Writeback: 0 kB
Active: 1035208 kB Mapped: 279544 kB
Inactive: 486132 kB Slab: 163204 kB
HighTotal: 0 kB Committed_AS: 2997492 kB
HighFree: 0 kB PageTables: 2496 kB
LowTotal: 2050128 kB VmallocTotal: 4292861952 kB
VmallocUsed: 2532 kB
VmallocChunk: 4292859180 kB
thanks,
kate
On 9/11/07, Rob van der Heij wrote:
>Although you say there's enough real memory, it may be the system is
>not configured correctly and still pages the Linux guests. Your
>performance monitor should be able to provide more data than what you
>mention in your post. You'd need to see whether it's indeed these two
>Linux servers that consume the extra cycles, and if so, see which
>processes are doing that in Linux. I would not expect that opening a
>connecting on port 443 and ending it would cause a lot of CPU activity
>(unless it triggers firewalls in Linux).
>
>I think I read from your post that there's one IFL on the z800. That
>means that you probably don't make things go faster by spreading the
>load over multiple virtual machines (actually, you will make it
>slower). The folks who came up with the model of probing port 443 may
>have had a different failure model than what's applicable to running
>two Linux virtual machines on the same z/VM (but I also know that such
>sometimes is a nasty fight).
>
>Rob
>--
>Rob van der Heij
----------------------------------------------------------------------
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
