Fedora 15 and z/VM FCP EDEVs

[Vic Cross]

G'day list,

I'm trying out F15 under z/VM 5.4.  I have no ECKD DASD at my site; I rely
on FCP disks.  I try to use z/VM FBA Emulation as much as possible (rather
than zfcp) as it makes disk management much easier.

I tried to install F15 on a guest with FBA minidisks, and the result is a
non-bootable system.  At the completion of the installation phase, I tell
the system to Shutdown and it does so cleanly.  The re-ipl fails however;
the kernel is unable to find the root filesystem and panics.

Two things are notable.  In the kernel output after the reboot, the kernel
command line is about four lines of gibberish (mostly blanks, but a
smattering of random punctuation marks).  Also, I tried attaching the disks
to a running system but no valid filesystem was found.  (I was trying to
fix what I thought might have just been a problem with zipl, by attaching
the disks to a running system.)

I tried to do a RHEL6 install a while ago, but I could not even get it to
install -- Anaconda had no support for FBA disks.  The fact that F15 was
able to successfully go through Anaconda was encouraging, but perhaps it's
not there yet.  Has anyone tried a similar install and has experiences to
share?

On a related note, a Kickstart install to FBA disks fails in much the same
way as my prior RHEL6 attempts.  In the anaconda.log during install I see
Anaconda successfully finds the DASDs and the partition, but it "ignores"
the partitions and then reports that there are no usable disks.

Thanks and regards,
Vic

--
Vic Cross --  System z Technical Specialist -- IBM Australia --
viccross(a)au1.ibm.com

[David Cantrell]

On 08/04/2011 04:27 AM, Vic Cross wrote:
>  I'm trying out F15 under z/VM 5.4.  I have no ECKD DASD at my
> site; I rely
>  on FCP disks.  I try to use z/VM FBA Emulation as much as possible (rather
>  than zfcp) as it makes disk management much easier.
>
>  I tried to install F15 on a guest with FBA minidisks, and the result is a
>  non-bootable system.  At the completion of the installation phase, I tell
>  the system to Shutdown and it does so cleanly.  The re-ipl fails however;
>  the kernel is unable to find the root filesystem and panics.
>
>  Two things are notable.  In the kernel output after the reboot, the kernel
>  command line is about four lines of gibberish (mostly blanks, but a
>  smattering of random punctuation marks).  Also, I tried attaching the disks
>  to a running system but no valid filesystem was found.  (I was trying to
>  fix what I thought might have just been a problem with zipl, by attaching
>  the disks to a running system.)
>
>  I tried to do a RHEL6 install a while ago, but I could not even get it to
>  install -- Anaconda had no support for FBA disks.  The fact that F15 was
>  able to successfully go through Anaconda was encouraging, but perhaps it's
>  not there yet.  Has anyone tried a similar install and has experiences to
>  share?
>
>  On a related note, a Kickstart install to FBA disks fails in much the same
>  way as my prior RHEL6 attempts.  In the anaconda.log during install I see
>  Anaconda successfully finds the DASDs and the partition, but it "ignores"
>  the partitions and then reports that there are no usable disks. 
Known problem:

https://bugzilla.redhat.com/show_bug.cgi?id=707027

Patches welcome.

-- 
David Cantrell <dcantrell(a)redhat.com&gt;
Supervisor, Installer Engineering Team
Red Hat, Inc. | Westford, MA | EST5EDT

[Jim Stephens]

On 8/4/2011 6:57 AM, David Cantrell wrote:
>  On 08/04/2011 04:27 AM, Vic Cross wrote:
> > I'm trying out F15 under z/VM 5.4.  I have no ECKD DASD at my site; I rely
> > on FCP disks.  I try to use z/VM FBA Emulation as much as possible (rather
> > than zfcp) as it makes disk management much easier.
> >
> > I tried to install F15 on a guest with FBA minidisks, and the result is a
> > non-bootable system.  At the completion of the installation phase, I tell
> > the system to Shutdown and it does so cleanly.  The re-ipl fails however;
> > the kernel is unable to find the root filesystem and panics.
> >
> > Two things are notable.  In the kernel output after the reboot, the kernel
> > command line is about four lines of gibberish (mostly blanks, but a
> > smattering of random punctuation marks).  Also, I tried attaching the disks
> > to a running system but no valid filesystem was found.  (I was trying to
> > fix what I thought might have just been a problem with zipl, by attaching
> > the disks to a running system.)
> >
> > I tried to do a RHEL6 install a while ago, but I could not even get it to
> > install -- Anaconda had no support for FBA disks.  The fact that F15 was
> > able to successfully go through Anaconda was encouraging, but perhaps it's
> > not there yet.  Has anyone tried a similar install and has experiences to
> > share?
> >
> > On a related note, a Kickstart install to FBA disks fails in much the same
> > way as my prior RHEL6 attempts.  In the anaconda.log during install I see
> > Anaconda successfully finds the DASDs and the partition, but it "ignores"
> > the partitions and then reports that there are no usable disks.
>  Known problem:
>
>  https://bugzilla.redhat.com/show_bug.cgi?id=707027
>
>  Patches welcome.
>  
"You are not authorized to access bug #707027. To see this bug, you must 
first log in to an account 
<https://bugzilla.redhat.com/show_bug.cgi?id=707027&GoAheadAndLogIn=1> 
with the appropriate permissions"

is it a Fedora bug somewhere?  Then you might get an answer.

[David Cantrell]

On 08/04/2011 12:41 PM, Jim Stephens wrote:
>  On 8/4/2011 6:57 AM, David Cantrell wrote:
> > On 08/04/2011 04:27 AM, Vic Cross wrote:
> >> I'm trying out F15 under z/VM 5.4.  I have no ECKD DASD at my site; I rely
> >> on FCP disks.  I try to use z/VM FBA Emulation as much as possible (rather
> >> than zfcp) as it makes disk management much easier.
> >>
> >> I tried to install F15 on a guest with FBA minidisks, and the result is a
> >> non-bootable system.  At the completion of the installation phase, I tell
> >> the system to Shutdown and it does so cleanly.  The re-ipl fails however;
> >> the kernel is unable to find the root filesystem and panics.
> >>
> >> Two things are notable.  In the kernel output after the reboot, the kernel
> >> command line is about four lines of gibberish (mostly blanks, but a
> >> smattering of random punctuation marks).  Also, I tried attaching the disks
> >> to a running system but no valid filesystem was found.  (I was trying to
> >> fix what I thought might have just been a problem with zipl, by attaching
> >> the disks to a running system.)
> >>
> >> I tried to do a RHEL6 install a while ago, but I could not even get it to
> >> install -- Anaconda had no support for FBA disks.  The fact that F15 was
> >> able to successfully go through Anaconda was encouraging, but perhaps it's
> >> not there yet.  Has anyone tried a similar install and has experiences to
> >> share?
> >>
> >> On a related note, a Kickstart install to FBA disks fails in much the same
> >> way as my prior RHEL6 attempts.  In the anaconda.log during install I see
> >> Anaconda successfully finds the DASDs and the partition, but it
> "ignores"
> >> the partitions and then reports that there are no usable disks.
> > Known problem:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=707027
> >
> > Patches welcome.
> >
>  "You are not authorized to access bug #707027. To see this bug, you must
>  first log in to an account
>  <https://bugzilla.redhat.com/show_bug.cgi?id=707027&GoAheadAndLogIn=1>
>  with the appropriate permissions"
>
>  is it a Fedora bug somewhere? Then you might get an answer. 
It is a Fedora bug, the permissions were wrong.  Corrected now.

Thanks,

-- 
David Cantrell <dcantrell(a)redhat.com&gt;
Supervisor, Installer Engineering Team
Red Hat, Inc. | Westford, MA | EST5EDT