Hello list,
It's been a few years since I looked at these memory management tools, and back
then there were some concerns about the production readiness of CMM or CMMA for
prod environments. It looks like CPUPLUGD can also do memory ballooning via
CMM? The problem I'm trying to solve is to
taking a step back and going to jump on vendors that does not allow at
least 3days on a different systemnot very smart not allowing this for
DR purposes and couple vendors we have normally mess up the key/password
we need on DR...
From: David Kreuter dkreu...@vm-resources.com
To:
CMMA is gone, didn't work right and support was pulled.
VMRM does not have proper feedback and is more likely to crash your
linux server than help
CPUPLUGD - never seen any measured value.
Focus on understanding the storage requirements. One of the
presentations at the VMWorkshop last week was
As a guy who has some experience with DR (on zOS) I can tell you that if you
are having problems getting good codes for a CPU change during a test, the same
thing will probably happen if the real thing occurs. Thus, your DR plan should
incorporate possible delays while these errant CPU codes
The workshop presentations can be found here, Jon:
http://www.vmworkshop.org/2013/presentations
However, I don't see the presentation listed that Barton refers to
below; I attended it and it has a lot of good info how these things work.
Have a good one, too.
DJ
On 06/27/2013 09:42 AM, Barton
A whitepaper was published about a year ago about the updates to cpuplugd.
It can be found at
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102139
I believe you would need SLES 11 for the updated cpuplugd. I don't think
the updates are available in SLES 10.
On Thu, Jun 27, 2013
we do allow it in plan...frustrating on some vendors getting key/psw's...
then I have others that do exactly what I suggest...grace period to get
keys/psw's..but your up and running..
From: William Lyle bl...@bjc.org
To: LINUX-390@VM.MARIST.EDU
Date: 06/27/2013 09:53 AM
Subject:
Hi Ron,
You can set both CPU and model. CPU serial can be set with a command or
within the directory entry for the guest. If you also want to set the
CPU model you need to modify the storage address within the VMDBK that
contains the CPU model for a guest. But some products query the model in
a
Has anyone else run into this? We were running RHEL 6.2 on s390x (z/VM 6.2,
actually) with no problems, but the same kickstart modified to point to the
RHEL 6.4 ISO seems to ignore the clearpart --initlabel --all/zerombr lines.
We have a standard (small) zlinux build that was defined in the
I was never much enamoured with the original cpuplugd - and my customer
response to testing it was less than enthusiastic. This, however, looks more
interesting.
Now to see if I can convince the customer to retest using it (R/H 6.4).
Shane ...
On Fri, Jun 28th, 2013 at 1:12 AM, Bruce Hayden
10 matches
Mail list logo
