Bug 1576733
Summary: | Fedora 28: Can't boot ISO in s390x KVM | |||
---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | IBM Bug Proxy <bugproxy> | |
Component: | lorax | Assignee: | Brian Lane <bcl> | |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 28 | CC: | anaconda-maint-list, bcl, bugproxy, dan, dmach, hannsj_uhl, herrold, jkachuck, jonathan, kellin, thuth, vanmeeuwen+fedora, v.podzimek+fedora, vponcova, wwoods | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | s390x | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | lorax-28.11-1 lorax-28.15-1.fc28 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1578402 1594179 (view as bug list) | Environment: | ||
Last Closed: | 2018-06-28 14:06:30 UTC | Type: | --- | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1478448 | |||
Bug Blocks: | 1594179 |
Description
IBM Bug Proxy
2018-05-10 09:31:14 UTC
---Problem Description--- Can't boot Fedora ISO under KVM. KVM allows to boot virtual machines from an ISO with an s390 boot catalog. E.g., RHEL 7.5 can be booted from ISO under RHEL-Alt 7.5 or any other KVM with ISO boot support. It would really be nice if this would work for Fedora as well. ---uname output--- Linux s3560022.boeblingen.de.ibm.com 4.16.6-202.fc27.s390x #1 SMP Tue May 1 23:15:29 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = 3906-703 (IBM z14) ---boot type--- CDROM / ISO image ---Install repository type--- CDROM ---Point of failure--- Failed during boot of installer What ISO image have you tried? The regular Fedora-Server-dvd-s390x-28-1.1.iso or the netinst one (Fedora-Server-netinst-s390x-28-1.1.iso)? The "netinst" is created with mk-s390-cdboot tool and should be directly bootable. ------- Comment From MIHAJLOV.com 2018-05-14 03:12 EDT------- I've used the netinst ISO. Here's the console output from the start attempt --------------------------------------------------------------------------------- [root@s3560001 ~]# virsh start --console f28 Domain f28 started Connected to domain f28 Escape character is ^] SCSI CD-ROM detected. No suitable boot entry found on ISO-9660 media! --------------------------------------------------------------------------------- I've used the following XML to define the VM: <domain type='kvm'> <name>f28</name> <memory unit='KiB'>2097152</memory> <vcpu>2</vcpu> <os> <type arch='s390x'>hvm</type> </os> <on_crash>preserve</on_crash> <devices> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/var/lib/libvirt/images/Fedora-Server-netinst-s390x-28-1.1.iso'/> <target dev='sda' bus='scsi'/> <readonly/> <boot order='1'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/var/lib/libvirt/images/f28.img'/> <target dev='vda' bus='virtio'/> </disk> <interface type='network'> <source network='default'/> <model type='virtio'/> </interface> <console type='pty'> <target type='sclp' port='0'/> </console> </devices> </domain> I think I see what's the problem, the master branch is missing https://github.com/weldr/lorax/commit/df35857c9bc59b27939e339a27855496114aa3e8 Pushed this to master, it will be in lorax-29.3-1 and eventually in 28.11-1 when I backport lorax-composer lorax-28.11-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-98f6c89898 lorax-28.11-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-98f6c89898 lorax-28.12-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-77b9570ea1 lorax-28.12-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-77b9570ea1 lorax-28.13-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-50a787999b lorax-28.13-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-50a787999b lorax-28.14-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-90c68c133d lorax-28.14-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-90c68c133d lorax-28.15-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-4b709ebc5e lorax-28.15-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-4b709ebc5e lorax-28.15-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report. |