Bug 1467274
Summary: | Failed to install guest os from passthrough USB device | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Yongxue Hong <yhong> | ||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||
Status: | CLOSED WONTFIX | QA Contact: | Release Test Team <release-test-team-automation> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 7.4 | CC: | dgibson, jkonecny, knoel, mdeng, pjones, qzhang, rharwood, virt-maint, xianwang, xuma, yhong | ||||||
Target Milestone: | rc | ||||||||
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: | 2021-01-15 07:39:11 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: | |||||||||
Attachments: |
|
Description
Yongxue Hong
2017-07-03 09:55:42 UTC
This has been postponed quite a bit. Can you please retest with current kernel and qemu? Created attachment 1351439 [details]
installation.log
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. Serhii, here's another RHEL 7.6 bug for you to look at when you can. Xujun, Serhii wasn't able to reproduce this. Can you still reproduce the original problem? (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. 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. Xujun, Which IBM document are you referring to in comment 8? (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 (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. 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. Hello, Could you please run the boot with the rd.debug parameter and provide us rdsosreport log? Thank you Created attachment 1423352 [details]
dsosreport.txt
Hi Jiri Please check the attachment. Thanks. 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? 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. 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. |