> From: Mike Walter
> To: LINUX-390@VM.MARIST.EDU
> Date: 12.01.2015 20:43
> Subject: Re: [LINUX-390] cio_ignore vs Linux in System z
> Sent by: Linux on 390 Port
>
> Thanks, Sam, Jay, Jim, Harley, and Mark (and anyone else who may
> have replied since I looked at the lo
>>> On 1/12/2015 at 02:48 PM, Linker Harley - hlinke
wrote:
> Until you get around to disabling cio_ignore you can run the following
> command to update the blacklist when you add a volume to Linux to enable it
> to be seen:
> cio_ignore -r 0.0.vdev
Better yes, just
cio_ignore -R
which
] On Behalf Of Mike
Walter
Sent: Monday, January 12, 2015 1:43 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: cio_ignore vs Linux in System z
Thanks, Sam, Jay, Jim, Harley, and Mark (and anyone else who may have replied
since I looked at the log),
There are no LPAR-only Linux servers running here
Thanks, Sam, Jay, Jim, Harley, and Mark (and anyone else who may have replied
since I looked at the log),
There are no LPAR-only Linux servers running here, only those running (RHEL)
under z/VM. I suspected that cio_ignore was something related to security
(perhaps an auditor fearing that an e
>>> On 1/12/2015 at 12:13 PM, "Cohen, Sam" wrote:
> Mike,
>
> This is a RedHat "feature"; it isn't an issue with SuSE. It is an
SUSE, please. (It's been 11 years now.)
> implementation choice by the distributor.
Beginning with SLES12, a feature request from IBM means that (by _changeable_
Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mike
Walter
Sent: Monday, January 12, 2015 11:09 AM
To: LINUX-390@VM.MARIST.EDU
Subject: cio_ignore vs Linux in System z
The cio_ignore table within Linux (at least in RHEL6.5) is used to restrict
access devices, both real and virtual. Being new the Lin
It's also about efficiency. Recall that there aren't many other processors
out there whose I/O architecture is built on (sub)channels. If the
cio_ignore data indicates that signals arriving from certain channels
needn't be processed, then that's less work the kernel has to engage in. In
cases where
It's there for when you bring Linux up in an LPAR with bajillions of
devices defined, like an old z/OS LPAR for example. The IPL takes forever
as udev enumerates all those devices in /sys and /dev, and then you're
running a system that can touch all the devices which it should not have
access to.
Monday, January 12, 2015 10:09 AM
To: LINUX-390@VM.MARIST.EDU
Subject: cio_ignore vs Linux in System z
The cio_ignore table within Linux (at least in RHEL6.5) is used to restrict
access devices, both real and virtual. Being new the Linux on System z, this
has become an occasional stumbling
The cio_ignore table within Linux (at least in RHEL6.5) is used to restrict
access devices, both real and virtual. Being new the Linux on System z, this
has become an occasional stumbling block for our Linux admins; when we z/VM
sysprogs attach a new virtual or real device and the guest cannot
10 matches
Mail list logo
