Make sure that your files that you punch to the reader are FB 80. If you
don't you get all kinds of weird errors.
From: Cameron Seay cws...@gmail.com
To: LINUX-390@VM.MARIST.EDU
Date: 02/16/2012 10:19 PM
Subject:Re:
Sent by:Linux on 390 Port LINUX-390@VM.MARIST.EDU
Hi Livio,
This is supported in RHEL 6.2, kernel 2.6.32-220 and later.
-Brad
--
Brad Hinson bhin...@redhat.com
Worldwide System z Sales, Strategy, Marketing
Red Hat, Inc.
+1 (919) 360-0443
http://www.redhat.com/z
On Feb 14, 2012, at 10:38 PM, Livio Sousa wrote:
Hi guys,
Just to be sure:
Also make sure the initrd was transferred completely. I've seen this error
when the FTP session had a hidden error that the disk was full. Check query
disk to make sure the 191-a disk isn't at 100% usage.
If you login to the guest and run the 'filelist' command, you'll see the record
length
And I have seen cases where instead of using FTP to transfer the boot
files from the iso image to z/VM, IND$FILE was used instead. That also
led to RedHat boot time errors.
Also check to make sure the virtual guest has enough storage available
to uncompress completely the initrd file.
DJ
On
Cross-posted to the IBMVM discussion list
We're conducting a z/VM 5.4.0 proof of concept with Linux servers running
Oracle DB servers on z196 IFLs. The databases will reside on SAN storage,
accessed through a Cisco 9513 switch, connecting to the HP XP24000 storage
array.
Our SAN guy has
Hello,
We recently started having a chpid start throwing interface control checks.
The z/OS guy made the chpid unavailable to zOS and told us to vary off the
chpid to z/VM. This happened a few months ago. Since then z/VM was IPL'ed.
And the chpid started throwing Interface Control checks.
