Bug 1858655
| Summary: | Can not boot from the redireted usb stick | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | yduan |
| Component: | qemu-kvm | Assignee: | Gerd Hoffmann <kraxel> |
| qemu-kvm sub component: | USB | QA Contact: | yduan |
| Status: | CLOSED DUPLICATE | Docs Contact: | |
| Severity: | medium | ||
| Priority: | high | CC: | coli, jinzhao, juzhang, kraxel, lmiksik, virt-maint |
| Version: | 8.3 | Keywords: | Regression, Triaged |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | 8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-01-25 08:36: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: | |||
|
Description
yduan
2020-07-20 00:46:49 UTC
> libusbx-1.0.23-3.el8.x86_64 > This is not reproduced with > qemu-kvm-core-4.2.0-29.module+el8.2.1+7297+a825794d.x86_64. > Version-Release number of selected component (if applicable): > Host: > # uname -r > 4.18.0-193.13.2.el8_2.x86_64 > # rpm -q qemu-kvm-core > qemu-kvm-core-4.2.0-29.module+el8.2.1+7297+a825794d.x86_64 > # rpm -qa | grep usb > libgusb-0.3.0-1.el8.x86_64 > usbutils-010-3.el8.x86_64 > usb_modeswitch-data-20191128-1.el8.noarch > libertas-usb8388-firmware-20191202-97.gite8a0f4c9.el8.noarch > usbredir-0.8.0-1.el8.x86_64 > usbmuxd-1.1.0-13.el8.x86_64 > libusbmuxd-1.0.10-9.el8.x86_64 > usb_modeswitch-2.5.2-1.el8.x86_64 > libusbx-1.0.22-1.el8.x86_64 What happens when using the working package versions and only upgrade libusbx from 1.0.22 to 1.0.23? Hi Gerd, Using the RHEL 8.2.1 Host mentioned in Comment 0 'Additional info', only updating libusbx from libusbx-1.0.22-1.el8.x86_64 to libusbx-1.0.23-3.el8.x86_64, the redirected usb stick can be found in the boot menu list and inside guest. Host: # uname -r 4.18.0-193.13.2.el8_2.x86_64 # rpm -q qemu-kvm-core qemu-kvm-core-4.2.0-29.module+el8.2.1+7297+a825794d.x86_64 # rpm -qa | grep usb libgusb-0.3.0-1.el8.x86_64 usbutils-010-3.el8.x86_64 usb_modeswitch-data-20191128-1.el8.noarch libusbx-1.0.23-3.el8.x86_64 libertas-usb8388-firmware-20191202-97.gite8a0f4c9.el8.noarch usbredir-0.8.0-1.el8.x86_64 usbmuxd-1.1.0-13.el8.x86_64 libusbmuxd-1.0.10-9.el8.x86_64 usb_modeswitch-2.5.2-1.el8.x86_64 Guest: # uname -r 4.18.0-193.6.3.el8_2.x86_64 Hmm, ok, that excludes the #1 candidate from, the list. qemu-kvm is unlikely too (29-> 30 has only 4 patches and none of them looks even remotely usb related). Another candidate is virt-viewer. What are the versions for the working/non-working cases? Any effect if you upgrade or downgrade virt-viewer only? (In reply to Gerd Hoffmann from comment #7) > Hmm, ok, that excludes the #1 candidate from, the list. > qemu-kvm is unlikely too (29-> 30 has only 4 patches and none of them looks > even remotely usb related). > > Another candidate is virt-viewer. What are the versions for the > working/non-working cases? > Any effect if you upgrade or downgrade virt-viewer only? On the RHEL 8.3 host (non-working case), the virt-viewer version is 9.0-3. # rpm -q virt-viewer virt-viewer-9.0-3.el8.x86_64 # rpm -q qemu-kvm qemu-kvm-4.2.0-30.module+el8.3.0+7298+c26a06b8.x86_64 I downgrade the virt-viewer to version 7.0-9, cannot connect the VM with remote-viewer: # rpm -q virt-viewer virt-viewer-7.0-9.el8.x86_64 # remote-viewer spice://$IP:5900 remote-viewer: symbol lookup error: remote-viewer: undefined symbol: ovirt_vm_get_host, version GOVIRT_0.3.2 ========================================================================= On the RHEL 8.2.1 host (working case), the virt-viewer version is 7.0-9. # rpm -q virt-viewer virt-viewer-7.0-9.el8.x86_64 # rpm -q qemu-kvm qemu-kvm-4.2.0-29.module+el8.2.1+7297+a825794d.x86_64 I update the virt-viewer to version 9.0-3 and re-test, everything still works well. # rpm -q virt-viewer virt-viewer-9.0-3.el8.x86_64 Hmm, can't reproduce. Can you retest with latest 8.3? (In reply to Gerd Hoffmann from comment #9) > Hmm, can't reproduce. > Can you retest with latest 8.3? Hi Gerd, I can reproduce this with qemu-kvm-4.2.0-33.module+el8.3.0+7705+f09d73e4.x86_64. Also hit this problem with latest qemu-kvm-5.1.0-3.module+el8.3.0+7708+740a1315.x86_64. I think the key step is boot the VM with '-S' option and redirect the usb stick before resuming the VM: > 1.Boot VM with usb-redir device: > /usr/libexec/qemu-kvm \ > -S \ > > 3.Redirect SanDisk USB stick: > When remote-viewer connects, click 'File' --> 'USB device selection' --> > select the 'SanDisk' to enable usb redirection. > > 4.Resume the VM: > (qemu) cont Thanks, yduan (In reply to yduan from comment #10) > (In reply to Gerd Hoffmann from comment #9) > > Hmm, can't reproduce. > > Can you retest with latest 8.3? > > Hi Gerd, > > I can reproduce this with > qemu-kvm-4.2.0-33.module+el8.3.0+7705+f09d73e4.x86_64. > > Also hit this problem with latest > qemu-kvm-5.1.0-3.module+el8.3.0+7708+740a1315.x86_64. > > I think the key step is boot the VM with '-S' option and redirect the usb > stick before resuming the VM: > Hi Gerd, This issue can also be reproduced with qemu-kvm-5.1.0-4.module+el8.3.0+7846+ae9b566f.x86_64. Do we need to file a new bz to track the fast train qemu 5.1 ? Thanks, yduan > I think the key step is boot the VM with '-S' option and redirect the usb
> stick before resuming the VM:
>
> > 1.Boot VM with usb-redir device:
> > /usr/libexec/qemu-kvm \
> > -S \
> >
> > 3.Redirect SanDisk USB stick:
> > When remote-viewer connects, click 'File' --> 'USB device selection' -->
> > select the 'SanDisk' to enable usb redirection.
> >
> > 4.Resume the VM:
> > (qemu) cont
Ok, so if you reset the guest at this point, will seabios find the device on the second boot?
> Hi Gerd,
>
> This issue can also be reproduced with
> qemu-kvm-5.1.0-4.module+el8.3.0+7846+ae9b566f.x86_64.
>
> Do we need to file a new bz to track the fast train qemu 5.1 ?
Maybe, but we should better find the root cause first.
(In reply to Gerd Hoffmann from comment #12) > > I think the key step is boot the VM with '-S' option and redirect the usb > > stick before resuming the VM: > > > > > 1.Boot VM with usb-redir device: > > > /usr/libexec/qemu-kvm \ > > > -S \ > > > > > > 3.Redirect SanDisk USB stick: > > > When remote-viewer connects, click 'File' --> 'USB device selection' --> > > > select the 'SanDisk' to enable usb redirection. > > > > > > 4.Resume the VM: > > > (qemu) cont > > Ok, so if you reset the guest at this point, will seabios find the device on > the second boot? Actually no. Tested with qemu-kvm-4.2.0-33.module+el8.3.0+7705+f09d73e4.x86_64 and qemu-kvm-5.1.0-4.module+el8.3.0+7846+ae9b566f.x86_64. Hmm, looks suspicious simliar to bug 1874740, possibly a dup. |