We've had many problems over the years that only showed up on out first
level systems. Most of those didn't show up second level because our
second level systems don't have the full size workloads that the first
level systems have.
We've had a couple of problems that only showed up first level because
of the nature of the problem. I don't recall the specifics, but there
was at least one where the older VM that we had on first level was
masking something on the hardware from the newer VM that was running
second level. When the new VM was moved to first level, the problem
appeared. These problems are rare, but they do occur.
Dennis
Are you on the list? -- H.R.G. (Heroes)
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
David Boyes
Sent: Monday, January 22, 2007 04:45
To: [email protected]
Subject: Re: VM test platforms
I'll second this. In 20+ years of running VM, I can remember only two
cases where something worked differently 2nd level than it did 1st
level, and in at least one case, there was a reason for it.
Unless you really have to be 197.34% paranoid about such things (you're
launching missiles or running 47 zillion pacemakers or something like
that), you're plenty safe testing 2nd level. It's lots less hassle, and
the ability to do testing during the day is just too cool to pass up.
----------------------------------------------------------------------
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 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
