> I'm not sure I like this or not
> http://finance.yahoo.com/news/ibm-share-technology-china-strategy-
> 120007774.html
It's unavoidable -- welcome to the post-NSA spying disclosure world. If IBM
wants to continue to do business in the world's largest market, they have to do
it with Chinese
Hi,
Could one of the wise old wizards tell me if there is a CP command we can use
to deactivate or vary a CPU offline at the hypervisor level? Young wizards
appreciated too.
We want to change the number of CPU's and understand the correct place to do it
is in the HMC. But if we can do it dyn
You should be able to vary if off from VM with
VARY Online|OFFline PROCessor nn
I don't remember exactly, but I think that there is a way to mark the CPU
'reserved' so that it doesn't come online after an IPL.
Harley
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MAR
*#cp vary on proc nn*
On Tue, Mar 24, 2015 at 11:55 AM, Veencamp, Jonathon D. <
jdveenc...@fedins.com> wrote:
> Hi,
>
> Could one of the wise old wizards tell me if there is a CP command we can
> use to deactivate or vary a CPU offline at the hypervisor level? Young
> wizards appreciated too.
>
You mark the CPU reserved (or really, give the number of reserved CPUs) in
the LPAR profile. Putting reserved CPUs and memory in the LPAR profile
avoids IPLs!
On Tue, Mar 24, 2015 at 11:08 AM, Linker Harley - hlinke <
harley.lin...@acxiom.com> wrote:
> You should be able to vary if off from VM w
Am 24.03.2015 um 16:13 schrieb Bruce Hayden:
> You mark the CPU reserved (or really, give the number of reserved CPUs) in
> the LPAR profile. Putting reserved CPUs and memory in the LPAR profile
> avoids IPLs!
On newer systems (does work on z196) you can dynamically add CPUs to the
LPAR profile a
I have my name in a couple patents (US) related to virtualization -- and
what's funny is I have two apparently matching certificates from China as
well - completely written in Chinese. I can only tell what they are for by
the cryptic diagram they printed of the ideas. I haven't bothered looking
Trying to run docker to do a build with docker started with -d, I get a
SEGV doing a lookup of registry-1.docker.io:
#0 0x03fffa176a20 in internal_getent () from /lib64/libnss_files.so.2
#1 0x03fffa177e62 in _nss_files_gethostbyname4_r () from
/lib64/libnss_files.so.2
#2 0x80636
Neale,
I haven't spent much time with it, but I at least got it running:
-) Got RHEL 7 tar file from IBM
-) Copied to RHEL 7
-) Listed contents:
# tar tzf docker-rhel7-20150302.tar.gz
docker-rhel7-20150302/
docker-rhel7-20150302/docker
...
-) untared it:
# tar xzf docker-rhel7-20150302.tar.gz
-)
Hi Neale,
Linux on 390 Port wrote on 24.03.2015 19:03:33:
> Trying to run docker to do a build with docker started with -d, I get a
> SEGV doing a lookup of registry-1.docker.io:
we have been observing this, too, and are in the process of verifying a new
build. I noticed these issues when using
Thanks for the explanation, sounds good about the delivery of the new
version. I was trying to exercise the process so I wasn’t expecting things
to work, just not crash. I’ll take a look at the base image link you sent.
I assume I can set up my own registry and use docker-registry to serve
things o
11 matches
Mail list logo
