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 1467274 - Failed to install guest os from passthrough USB device
Summary: Failed to install guest os from passthrough USB device
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.4
Hardware: ppc64le
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-03 09:55 UTC by Yongxue Hong
Modified: 2022-01-14 19:28 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-15 07:39:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
installation.log (35.56 KB, image/png)
2017-11-13 06:41 UTC, Yongxue Hong
no flags Details
dsosreport.txt (3.50 MB, text/plain)
2018-04-18 06:27 UTC, Yongxue Hong
no flags Details

Description Yongxue Hong 2017-07-03 09:55:42 UTC
Description of problem:
Failed to install guest os from passthrough USB device

Version-Release number of selected component (if applicable):
Host kernel: kernel-3.10.0-689.el7.ppc64le
qemu: qemu-kvm-rhev-2.9.0-14.el7.ppc64le
SLOF: SLOF-20170303-4.git66d250e.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1.Prepare a bootable usb stick on host.
On host:
 dd if=/root/test_home/yhong/iso/RHEL-7.4-20170621.0-Server-ppc64le-dvd1.iso of=/dev/sde bs=100M oflag=direct or dd if=/root/test_home/yhong/iso/boot.iso of=/dev/sde bs=100M oflag=direct

2.Boot guest with the passthrough USB stick assigned
eg:
[root@ibm-p8-kvm-02-qe command]# lsusb
Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2

[root@ibm-p8-kvm-02-qe image]# cat ../command/qemu-kvm-rhev-rhel7-42216.sh
/usr/libexec/qemu-kvm \
-name "rhel-7.4-42216" \
-m 8G \
-nodefaults \
-smp 4 \
-boot menu=on,order=cd \
-device VGA,id=vga0 \
-device nec-usb-xhci,id=xhci \
-device usb-tablet,id=usb-tablet0 \
-device usb-kbd,id=usb-kbd0 \
-chardev socket,id=qmp_id_qmpmonitor,path=/var/tmp/monitor-qmpmonitor0,server,nowait \
-mon chardev=qmp_id_qmpmonitor,mode=control  \
-chardev socket,id=qmp_id_catch_monitor,path=/var/tmp/monitor-catch_monitor0,server,nowait \
-mon chardev=qmp_id_catch_monitor,mode=control  \
-chardev socket,id=serial_id_serial,path=/var/tmp/serial-serial0,server,nowait \
-device spapr-vty,reg=0x30000000,chardev=serial_id_serial \
-device virtio-scsi-pci,id=scsi-pci-0 \
-drive file=/root/test_home/yhong/image/rhel-7_4-42216-20G.qcow2,format=qcow2,if=none,cache=none,media=disk,werror=stop,rerror=stop,id=drive-0 \
-device scsi-hd,bus=scsi-pci-0.0,id=scsi-hd-0,drive=drive-0,channel=0,scsi-id=0,lun=1 \
-netdev tap,id=hostnet0,script=/etc/qemu-ifup \
-device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=40:f2:e9:5d:9c:03 \
-device nec-usb-xhci,id=controller \
-device usb-host,hostbus=2,hostaddr=2,id=host-usbstick,bus=controller.0,bootindex=0 \
-serial unix:./sock0,server,nowait \
-qmp tcp:0:3000,server,nowait \
-monitor stdio \
-vnc :10

3.Select boot from the passthrough USB device in guest

4.Install guest os from this passthrough USB stick.

Actual results:
Failed to install guest os.

Expected results:
Install guest successfully.

Additional info:
It is not reproduced on x86.

Comment 2 David Gibson 2017-11-09 03:00:14 UTC
This has been postponed quite a bit.  Can you please retest with current kernel and qemu?

Comment 3 Yongxue Hong 2017-11-13 06:41:58 UTC
Created attachment 1351439 [details]
installation.log

Comment 4 Yongxue Hong 2017-11-13 06:43:25 UTC
Hi David,

Reproduced with latest kernel and qemu:
Version:
Host kernel version : 3.10.0-781.el7.ppc64le
Qemu-kvm version : qemu-kvm-rhev-2.10.0-5.el7.ppc64le
SLOF version : SLOF-20170724-2.git89f519f.el7.noarch

1. Check usd device inserted on host
[root@ibm-p8-kvm-01-qe home]# lsusb
Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[root@ibm-p8-kvm-01-qe home]# 

2. Prepare a bootable usb stick on host.
[root@ibm-p8-kvm-01-qe home]# dd if=./RHEL-7.4-20170711.0-Server-ppc64le-dvd1.iso of=/dev/sdm bs=100M oflag=direct

3. Boot a guest to install os from passthrough usb device.

[root@ibm-p8-kvm-01-qe home]# cat install-from-usb.sh
/usr/libexec/qemu-kvm \
-name "guest" \
-m 8G \
-nodefaults \
-smp 4 \
-boot menu=on,order=cd \
-device VGA,id=vga0 \
-device nec-usb-xhci,id=xhci \
-device usb-tablet,id=usb-tablet0 \
-device usb-kbd,id=usb-kbd0 \
-chardev socket,id=qmp_id_qmpmonitor,path=/var/tmp/monitor-qmpmonitor0,server,nowait \
-mon chardev=qmp_id_qmpmonitor,mode=control  \
-chardev socket,id=qmp_id_catch_monitor,path=/var/tmp/monitor-catch_monitor0,server,nowait \
-mon chardev=qmp_id_catch_monitor,mode=control  \
-chardev socket,id=serial_id_serial,path=/var/tmp/serial-serial0,server,nowait \
-device spapr-vty,reg=0x30000000,chardev=serial_id_serial \
-device virtio-scsi-pci,id=scsi-pci-0 \
-drive file=./rhel75-guest-20G.qcow2,format=qcow2,if=none,cache=none,media=disk,werror=stop,rerror=stop,id=drive-0 \
-device scsi-hd,bus=scsi-pci-0.0,id=scsi-hd-0,drive=drive-0,channel=0,scsi-id=0,lun=1 \
-netdev tap,id=hostnet0,script=/etc/qemu-ifup \
-device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=40:f2:e9:5d:9c:03 \
-device nec-usb-xhci,id=controller \
-device usb-host,hostbus=2,hostaddr=2,id=host-usbstick,bus=controller.0,bootindex=0 \
-serial unix:./sock0,server,nowait \
-qmp tcp:0:3000,server,nowait \
-monitor stdio \
-vnc :10

4. Select option to install os.

Actual result:
Failed to install guest os.
The attachment is the vnc info.

Comment 5 David Gibson 2018-03-13 05:05:04 UTC
Serhii, here's another RHEL 7.6 bug for you to look at when you can.

Comment 6 David Gibson 2018-03-20 02:46:02 UTC
Xujun,

Serhii wasn't able to reproduce this.  Can you still reproduce the original problem?

Comment 7 Xujun Ma 2018-03-21 00:53:36 UTC
(In reply to David Gibson from comment #6)
> Xujun,
> 
> Serhii wasn't able to reproduce this.  Can you still reproduce the original
> problem?

OK,will update results later.

Comment 8 Xujun Ma 2018-03-22 03:31:47 UTC
Hi David,

I can reproduce this problem if without any additional arguments behind boot kernel.

if I add "inst.stage2=hd:UUID=2018-03-15-20-44-56-00" behind boot kernel acorrding to IBM's document, the os will be installed smoothly.

I think maybe it's not a bug.

Comment 9 David Gibson 2018-03-26 00:56:09 UTC
Xujun,

Which IBM document are you referring to in comment 8?

Comment 10 Xujun Ma 2018-03-26 06:08:48 UTC
(In reply to David Gibson from comment #9)
> Xujun,
> 
> Which IBM document are you referring to in comment 8?

https://www.ibm.com/support/knowledgecenter/en/linuxonibm/liabw/liabwinstallusb.htm

Comment 11 Serhii Popovych 2018-03-26 07:29:19 UTC
(In reply to Xujun Ma from comment #8)
> Hi David,
> 
> I can reproduce this problem if without any additional arguments behind boot
> kernel.
> 
> if I add "inst.stage2=hd:UUID=2018-03-15-20-44-56-00" behind boot kernel
> acorrding to IBM's document, the os will be installed smoothly.
> 
> I think maybe it's not a bug.

But this behavior is different from one on x86_64 machines. I think something with search for installation phase 2 by initramfs dracut code. It just cannot find USB stick and according to your comment we need to provide UUID explicitly
to force dracut to find USB stick.

Comment 12 David Gibson 2018-04-12 06:00:11 UTC
Right.

In addition the instructions from IBM are for installing a host, it turns out that using those instructions works for a guest too, but that's not necessarily obvious.

My best guess at this point is that the problem is in anaconda not locating the USB drive on Power.  Reassigning accordingly.


Hi anaconda-devs:

I think at the least this bug needs some analysis to work out why anaoconda isn't able to automatically find the stage2 installer when booting from a USB stick on a Power guest.

It's possible the problem does go back to qemu or the kernel, but we need a better idea of what's happening at the installer level first, I think.

Comment 13 Jiri Konecny 2018-04-13 09:52:16 UTC
Hello,

Could you please run the boot with the rd.debug parameter and provide us rdsosreport log?

Thank you

Comment 14 Yongxue Hong 2018-04-18 06:27:20 UTC
Created attachment 1423352 [details]
dsosreport.txt

Comment 15 Yongxue Hong 2018-04-18 06:29:26 UTC
Hi Jiri

Please check the attachment.

Thanks.

Comment 16 Jiri Konecny 2018-04-18 08:42:42 UTC
Based on the comment 8 there is a missing or wrongly set-up path to the stage2. The stage2 device position should be specified by a bootloader. I'm not sure what bootloader is used on ppc64 but I think there is a grub2 used.

Peter could you please confirm, that this issue is in grub2 or is it something else?

Comment 17 David Gibson 2018-04-19 00:05:14 UTC
grub2 is used on installed Power guests.  It's not used on Power hosts, however.  I'm not sure if it's used on Power install media or not.

Comment 19 RHEL Program Management 2021-01-15 07:39:11 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


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