Bug 904245 - chreipl fails under hercules
Summary: chreipl fails under hercules
Alias: None
Product: Fedora
Classification: Fedora
Component: hercules
Version: 19
Hardware: s390x
OS: Unspecified
Target Milestone: ---
Assignee: Dan Horák
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: ZedoraTracker
TreeView+ depends on / blocked
Reported: 2013-01-25 20:38 UTC by Dan Horák
Modified: 2015-02-17 14:42 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-02-17 14:42:30 UTC
Type: Bug

Attachments (Terms of Use)
full log (37.19 KB, text/plain)
2013-01-25 20:38 UTC, Dan Horák
no flags Details
hercules.log (36.82 KB, text/x-log)
2013-01-26 13:01 UTC, Dan Horák
no flags Details
anaconda.log (4.33 KB, text/x-log)
2013-01-26 13:02 UTC, Dan Horák
no flags Details
storage.log (73.00 KB, text/x-log)
2013-01-26 13:02 UTC, Dan Horák
no flags Details
program.log (23.38 KB, text/x-log)
2013-01-26 13:03 UTC, Dan Horák
no flags Details
packaging.log (80.24 KB, text/x-log)
2013-01-26 13:03 UTC, Dan Horák
no flags Details
kickstart (454 bytes, text/plain)
2013-01-26 13:04 UTC, Dan Horák
no flags Details

Description Dan Horák 2013-01-25 20:38:50 UTC
Created attachment 687675 [details]
full log

I was doing a kickstart installation of F-18 in the Hercules emulator to a FBA disk.

Version-Release number of selected component (if applicable):
anaconda 18.37.11

Comment 1 Dan Horák 2013-01-25 22:03:23 UTC
FWIW F-16 could be installed on FBA disk correctly

Comment 2 Dan Horák 2013-01-26 13:00:11 UTC
I've tried to update the installation environment with parted-3.1-10.fc18 using updates.img, still no change

from an installation in progress:

[anaconda root@s390x ~]# cat /proc/partitions 
major minor  #blocks  name

   7        0     160632 loop0
   7        1    1048576 loop1
   7        2     524288 loop2
  94        0    8388608 dasda
  94        1     204800 dasda1
  94        2    2097152 dasda2
  94        3    6086528 dasda3
 253        0    1048576 dm-0
[anaconda root@s390x ~]# fdisk -l /dev/dasda

Disk /dev/dasda: 8589 MB, 8589934592 bytes, 16777216 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

[anaconda root@s390x ~]#

Comment 3 Dan Horák 2013-01-26 13:01:38 UTC
Created attachment 687953 [details]

Comment 4 Dan Horák 2013-01-26 13:02:20 UTC
Created attachment 687954 [details]

Comment 5 Dan Horák 2013-01-26 13:02:53 UTC
Created attachment 687955 [details]

Comment 6 Dan Horák 2013-01-26 13:03:17 UTC
Created attachment 687956 [details]

Comment 7 Dan Horák 2013-01-26 13:03:42 UTC
Created attachment 687957 [details]

Comment 8 Dan Horák 2013-01-26 13:04:05 UTC
Created attachment 687958 [details]

Comment 9 Dan Horák 2013-01-26 13:26:15 UTC
I suspect the FBA DASD support in parted being wrong. It can be demonstrated on VDISK (virtual FBA disk) where parted and fdisk behave differently. I will open a new bug for it.

Comment 10 Dan Horák 2013-01-30 07:34:59 UTC
Or there can be a difference between LPAR (that's what Hercules emulates) and z/VM guest. Please see also the thread on the Fedora/s390x list - http://lists.fedoraproject.org/pipermail/s390x/2013-January/000574.html

Comment 11 Jan Stodola 2013-08-20 10:19:26 UTC
Reproduced with F19/s390x in hercules-3.09-1.fc19.x86_64.
For some reason, permission of /sys/firmware/reipl/ccw/loadparm is set to 444 during installation in hercules. On a real hardware running in z/VM, permission is set to 644.

Dan gave me an advise to change the permission to 644 during the installation and it resolved this issue, installation finished without any traceback.

Comment 12 Dan Horák 2013-08-20 10:28:36 UTC
It looks as a deficiency in Hercules itself, the default permission for /sys/firmware/reipl/ccw/loadparm is 0644, but it's reduced to 0444 if diag308 is not working.

from arch/s390/kernel/ipl.c

static int __init reipl_ccw_init(void)
        int rc;
        reipl_block_ccw = (void *) get_zeroed_page(GFP_KERNEL);
        if (!reipl_block_ccw)
                return -ENOMEM;
        if (MACHINE_IS_VM) {
                if (!diag308_set_works)
                        sys_reipl_ccw_vmparm_attr.attr.mode = S_IRUGO;
                rc = sysfs_create_group(&reipl_kset->kobj,
        } else {
                        sys_reipl_ccw_loadparm_attr.attr.mode = S_IRUGO;
                rc = sysfs_create_group(&reipl_kset->kobj,
        if (rc)
                return rc;
        if (ipl_info.type == IPL_TYPE_CCW) {
                reipl_block_ccw->ipl_info.ccw.devno = ipl_devno;
        reipl_capabilities |= IPL_TYPE_CCW;
        return 0;

Comment 13 Fedora End Of Life 2015-01-09 17:36:52 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 14 Fedora End Of Life 2015-02-17 14:42:30 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.