Eric,
> then I get a "STORAGE ACTIVATION FAILED" popup
Yup, I got that too. From another system, I vmcp LINKed, chccwdev -e'd and
dasdfmt'd the minidisks onto which I was trying to install. Then I
chccwdev -d'd, and vmcp DETached them. Then the install worked fine.
"Mike MacIsaac"(845) 433-70
>Has anyone successfully installed RHEL6.0 Beta under z/vm yet?
>I have 5.4 running with no problem.>
>I've selected "specialized storage devices" and select the correct
devices.
>get warning - device may need to be reinitialized, so I let it init all
the devices that will be.
>then I get a "STORAG
Has anyone successfully installed RHEL6.0 Beta under z/vm yet?
I have 5.4 running with no problem.
I've selected "specialized storage devices" and select the correct devices.
get warning - device may need to be reinitialized, so I let it init all the
devices that will be.
then I get a "STORAGE A
On 10/05/2010 07:35 PM, Wiggins, Mark wrote:
I'm trying to
add some multipath'd devices to a Debian(Lenny) instance. I can get
the devices configured properly,
I just can't get these definitions to hold across a reboot. I've
In order to narrow down which activation step does not work correc
On Monday, 10/04/2010 at 11:01 EDT, Jean Nelson/Jacksonville/i...@ibmus
wrote:
> So we have 64 devices on Channel 98 and 64 devices on Channel 99.
>
> My question is this?
>
> If on the SAN side , if they define a disk on PATH 98 , do ALL of the 64
> address defined in the IODF see the WWPN/LUN?
>
I guess , u need to make device-mapper kernel module to be built into
initramfs
On Wed, Oct 6, 2010 at 9:45 PM, Wiggins, Mark wrote:
> I guess what I'm really looking for is the equivalent to mkinitrd on
> Debian. Again, I can configure the two LUNS to be multipath'd,
>
> mpath1 (3600507680192
I guess what I'm really looking for is the equivalent to mkinitrd on Debian.
Again, I can configure the two LUNS to be multipath'd,
mpath1 (360050768019281af7153) dm-1 IBM ,2145
[size=3D3.7G][features=3D0][hwhandler=3D0]
\=5F round-robin 0 [prio=3D0][active]
\=5F 0:0:0:32 sde 8:6
Thanks Heiko, much appreciated.
Shane ...
On Wed, 6 Oct 2010 10:24:00 +0200
Heiko Carstens wrote:
> Or in other words: Linux is not aware if memory is local or remote.
> However the cpu topology is known (that is: which cpu belongs to which
> book) and the Linux kernel makes use of this in build
On Sat, Oct 02, 2010 at 09:29:38AM +1000, Shane wrote:
> I made the following comment in a thread on IBM-MAIN - perhaps the
> Boeblingen folks might know.
>
> Given that Linux is (NUMA) node aware, it would be interesting to see
> how a (non-z/VM) multi-book s390x Linux partition would appear re n
