RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1702229 - Fail to install guest with RHEL-7.7-20190420.n.0-Server-ppc64le-dvd1.iso
Summary: Fail to install guest with RHEL-7.7-20190420.n.0-Server-ppc64le-dvd1.iso
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dracut
Version: 7.7
Hardware: ppc64le
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Lukáš Nykrýn
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-23 09:22 UTC by Zhenyu Zhang
Modified: 2021-02-15 09:59 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-07 08:28:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
it will display ":Warning /dev/root does not exist" (241.78 KB, image/png)
2019-04-23 09:22 UTC, Zhenyu Zhang
no flags Details
rdsosreport.txt for RHEL-7.7-20190424.n.0-Server-ppc64le-dvd1.iso (54.92 KB, text/plain)
2019-04-25 12:25 UTC, Zhenyu Zhang
no flags Details
journalctl log from dracut (100.33 KB, image/png)
2019-04-30 03:10 UTC, Yihuang Yu
no flags Details

Description Zhenyu Zhang 2019-04-23 09:22:31 UTC
Created attachment 1557514 [details]
it will display ":Warning /dev/root does not exist"

Description of problem:
When using the RHEL-7.7-20190420.n.0-Server-ppc64le-dvd1.iso install guest, it will display ":Warning /dev/root does not exist"
But when I use RHEL-7.7-20190408.n.0-Server-ppc64le-dvd1.iso, I can install the guest normally.

Version-Release number of selected component (if applicable):
  kernel version:3.10.0-1040.el7.ppc64le
  qemu-kvm version:qemu-kvm-rhev-2.12.0-26.el7

The iso tree :
http://download.eng.bos.redhat.com/rhel-7/nightly/RHEL-7/RHEL-7.7-20190420.n.0/compose/Server/ppc64le/iso/RHEL-7.7-20190420.n.0-Server-ppc64le-dvd1.iso 

How reproducible:
10/10

Steps to Reproduce:
1.install guest
[root@ibm-p8-garrison-03 home]# /usr/libexec/qemu-kvm \
-name zhenyzha-RHEL-7.7 \
-sandbox off \
-machine pseries \
-m 16G \
-nodefaults \
-vga std \
-device nec-usb-xhci,id=xhci \
-device usb-tablet,id=usb-tablet0 \
-device usb-kbd,id=usb-kbd0 \
-smp 16,cores=4,threads=2,sockets=2 \
-vnc :30 \
-monitor stdio \
-rtc base=utc,clock=host \
-boot order=cdn,menu=off,strict=off \
-enable-kvm \
-qmp unix:/var/tmp/qmp-monitor-zhenyzha,server,nowait \
-qmp tcp:0:3001,server,nowait \
-device virtio-scsi-pci,bus=pci.0,addr=0x06,id=scsi-pci-0 \
-netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup \
-device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=40:f2:e9:5d:9c:07 \
-blockdev driver=raw,file.driver=file,node-name=drive_cd1,cache.no-flush=on,cache.direct=off,file.filename=RHEL-7.7-20190420.n.0-Server-ppc64le-dvd1.iso,read-only=on \
-device scsi-cd,id=cd1,drive=drive_cd1,bootindex=0 \
-blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=data.qcow2,node-name=my_file \
-blockdev driver=qcow2,node-name=my,file=my_file \
-device scsi-hd,drive=my,bus=scsi-pci-0.0,id=zhneg \




Actual results:
It will display ":Warning /dev/root does not exist"

Expected results:
Normal installation


Additional info:

The same problem occurs in the following versions:
1. kernel version:4.18.0-80.17.el8.ppc64le
   qemu-kvm version:qemu-kvm-2.12.0-63.module+el8+2833+c7d6d092

2. kernel version:4.18.0-80.17.el8.ppc64le
   qemu-kvm version:qemu-kvm-4.0.0-rc4

Comment 2 Zhenyu Zhang 2019-04-25 08:26:05 UTC
Additional info:
We found guest installation was a failure, in all trees of RHEL-7.7-20190409.n.0-Server-ppc64le-dvd1.iso -----RHEL-7.7-20190424.0.iso  
But when I use RHEL-7.7-20190408.n.0-Server-ppc64le-dvd1.iso, I can install the guest normally.

Comment 3 Gu Nini 2019-04-25 08:31:26 UTC
Please note the bug should be not ppc specific since kernel qe found a similar bz1702867.

Comment 4 Lukáš Nykrýn 2019-04-25 08:40:44 UTC
Can you please attach the generated rdsosreport.txt?

Comment 5 Zhenyu Zhang 2019-04-25 12:25:29 UTC
Created attachment 1558676 [details]
rdsosreport.txt for RHEL-7.7-20190424.n.0-Server-ppc64le-dvd1.iso

Comment 6 CongLi 2019-04-29 10:47:48 UTC
It works well for x86.
Host:
compose: RHEL-7.7-20190424.0
qemu-kvm-rhev-2.12.0-27.el7.x86_64
Guest:
compose: RHEL-7.7-20190424.0

CML:
    -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x4 \
    -drive id=drive_image1,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=test.qcow2 \
    -device scsi-hd,id=image1,drive=drive_image1 \
    -drive id=drive_cd1,if=none,snapshot=off,aio=threads,cache=none,media=cdrom,file=/home/kvm_autotest_root/iso/linux/RHEL-7.7-20190424.0-Server-x86_64-dvd1.iso \
    -device scsi-cd,id=cd1,drive=drive_cd1 \

Comment 7 Lukáš Nykrýn 2019-04-29 11:25:52 UTC
Does this setup use iscsi?

Comment 8 Yihuang Yu 2019-04-30 03:10:57 UTC
Created attachment 1560157 [details]
journalctl log from dracut

(In reply to Lukáš Nykrýn from comment #7)
> Does this setup use iscsi?

Hi Lukáš,
Usually, we use the disk from LocalFS, ISO file from nfs/LocalFS to test this scenario.

In addition, I can successfully launch the installation GUI when I add "-kernel" and "-initrd"

---
-kernel 'vmlinuz'  \
-initrd 'initrd.img'  \
---

Comment 9 Zhenyu Zhang 2019-04-30 03:18:08 UTC
We found that the compose version of RHEL-7.7-20190424.0-Server-ppc64le has the same problem.
But download these two files 'vmlinuz'and 'initrd.img' to the host,add "-kernel" and "-initrd"to the command line to install successfully

/usr/libexec/qemu-kvm \
-name zhenyzha-RHEL-7.7 \
-sandbox off \
-machine pseries \
-m 16G \
-nodefaults \
-vga std \
-device nec-usb-xhci,id=xhci \
-device usb-tablet,id=usb-tablet0 \
-device usb-kbd,id=usb-kbd0 \
-smp 16,cores=4,threads=2,sockets=2 \
-vnc :30 \
-monitor stdio \
-rtc base=utc,clock=host \
-boot order=cdn,menu=off,strict=off \
-enable-kvm \
-qmp unix:/var/tmp/qmp-monitor-zhenyzha,server,nowait \
-qmp tcp:0:3001,server,nowait \
-kernel 'vmlinuz' \
-initrd 'initrd.img' \
-device virtio-scsi-pci,bus=pci.0,addr=0x06,id=scsi-pci-0 \
-device virtio-scsi-pci,bus=pci.0,addr=0x07,id=scsi-pci-1 \
-netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup \
-device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=40:f2:e9:5d:9c:07 \
-blockdev driver=raw,file.driver=file,node-name=drive_cd1,cache.no-flush=on,cache.direct=off,file.filename=RHEL-7.7-20190424.0-Server-ppc64le-dvd1.iso,read-only=on \
-device scsi-cd,id=cd1,drive=drive_cd1,bootindex=0 \
-blockdev driver=file,cache.direct=off,cache.no-flush=on,filename=guest.qcow2,node-name=my_file \
-blockdev driver=qcow2,node-name=my,file=my_file \
-device scsi-hd,drive=my,bus=scsi-pci-0.0,id=zhneg \


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