Bug 1419572
Summary: | Can't install Fedora 25 in ppc64le/pseries guest | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andrea Bolognani <abologna> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 25 | CC: | anaconda-maint-list, gansalmon, g.kaviyarasu, hodgesto, ichavero, itamar, jkonecny, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab, mkolman, vanmeeuwen+fedora, vponcova |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | ppc64le | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 16:40:31 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andrea Bolognani
2017-02-06 14:29:19 UTC
Indeed it seems to be a kernel bug, and if you are OK with it, not installing zram seemed to function as a workaround for us. Using QEMU Builder for Packer: "boot_command": [ "c<wait10>", "linux /ppc/ppc64/vmlinuz ro ", "ks=http://{{ .HTTPIP }}:{{ .HTTPPort }}/fedora-25/ks-ppc64le-openstack.cfg ", "inst.zram=0 <enter>", ** <--- key addition ** "initrd /ppc/ppc64/initrd.img<enter>", "boot<enter><wait>" ], We are now able to pass the point of failure from before and the installation continues successfully. Screenshot of original exception: http://imgur.com/a/sduXy Source of solution: https://docs.fedoraproject.org/en-US/Fedora//html/Installation_Guide/sect-boot-options-advanced.html Information on zram: https://www.kernel.org/doc/Documentation/blockdev/zram.txt FWIW, the issue seem to have been resolved in Fedora 26. Thanks for letting us know. I'm going to close the bug, feel free to reopen if the problem shows up again, |