Bug 1663366
Summary: | USB selection option disabled even though USB support is enabled in RHV-4.2 | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Abhishekh Patil <abpatil> |
Component: | ovirt-engine | Assignee: | Nobody <nobody> |
Status: | CLOSED ERRATA | QA Contact: | Beni Pelled <bpelled> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.2.6 | CC: | abpatil, ahadas, bpelled, mavital, michal.skrivanek, mkalinin, mtessun, rdlugyhe, srosenbe |
Target Milestone: | ovirt-4.4.0 | Keywords: | TestOnly |
Target Release: | --- | Flags: | lsvaty:
testing_plan_complete-
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-08-04 13:16:51 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Abhishekh Patil
2019-01-04 04:57:25 UTC
Just to make sure, are they using SPICE? > On 11 Dec 2018, at 19:06, Abhishekh Patil <abpatil> wrote:
>
> Michal,
>
> below is the USB controller available on the guest:
> -------------------
> Intel Corporation 82801I (ICH9 Familty) USB UHCI Controller
if that is the only one then that’s a problem
VMs with SPICE graphics are configured with 1 USB 2 and 3 USB 1 companion controllers which are then used by SPICE client. This explains why it’s not working later on
What is in VM’s “Console” tab in VM configuration? Also the complete list of VM Devices would be helpful (screenshot with that tab would work too).
Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both VM devices? I am trying to follow the instructions for simulating this issue. I have a VM with os guest running Windows and installed the usbdk. It is not clear how you are running the virt-viewer in order to obtain the warning. Please provide more information. (In reply to Steven Rosenberg from comment #13) > I am trying to follow the instructions for simulating this issue. I have a > VM with os guest running Windows and installed the usbdk. > > It is not clear how you are running the virt-viewer in order to obtain the > warning. > > Please provide more information. 1. Create a VM from RHV portal. 2. Edit the VM and enable USB support from the portal. 3. Now, try to access this VM from windows client using virt-viewer and make sure usbdk is also installed on client. 4. When you open VM console using virt-viewer, under 'File' there is an option 'USB device selection option'. But, in case of customer, this option is disabled(grayed out) even though USB support is enabled from RHV-portal for the VM. Please let me know if this helps. (In reply to Abhishekh Patil from comment #14) > (In reply to Steven Rosenberg from comment #13) > > I am trying to follow the instructions for simulating this issue. I have a > > VM with os guest running Windows and installed the usbdk. > > > > It is not clear how you are running the virt-viewer in order to obtain the > > warning. > > > > Please provide more information. > > 1. Create a VM from RHV portal. > 2. Edit the VM and enable USB support from the portal. > 3. Now, try to access this VM from windows client using virt-viewer and make > sure usbdk is also installed on client. > 4. When you open VM console using virt-viewer, under 'File' there is an > option 'USB device selection option'. But, in case of customer, this option > is disabled(grayed out) even though USB support is enabled from RHV-portal > for the VM. > > Please let me know if this helps. Thank you for your response. I was asking more of how you are running the virt-viewer such as the parameters, example. As I understand it should be run on the command line on the same machine as the browser that runs our ovirt UI. I suppose it’s just a regular association in browser and opened from webadmin (In reply to Steven Rosenberg from comment #15) > (In reply to Abhishekh Patil from comment #14) > > (In reply to Steven Rosenberg from comment #13) > > > I am trying to follow the instructions for simulating this issue. I have a > > > VM with os guest running Windows and installed the usbdk. > > > > > > It is not clear how you are running the virt-viewer in order to obtain the > > > warning. > > > > > > Please provide more information. > > > > 1. Create a VM from RHV portal. > > 2. Edit the VM and enable USB support from the portal. > > 3. Now, try to access this VM from windows client using virt-viewer and make > > sure usbdk is also installed on client. > > 4. When you open VM console using virt-viewer, under 'File' there is an > > option 'USB device selection option'. But, in case of customer, this option > > is disabled(grayed out) even though USB support is enabled from RHV-portal > > for the VM. > > > > Please let me know if this helps. > > Thank you for your response. I was asking more of how you are running the > virt-viewer such as the parameters, example. As I understand it should be > run on the command line on the same machine as the browser that runs our > ovirt UI. >> USB selection is not just grayed out when using virt-viewer, but this also happens when accessing the VM through VM portal. sync2jira sync2jira Beni, can you please test this on 4.3 to see if it's really resolved/ Verified on: - RHV 4.3.6.7-0.1.el7 - VM Portal 1.6.0-1 - VirtViewer 6.0.256 - UsbDk_1.0.21_x64.msi Verification steps: 1. Create windows_7_x64 vm by template. 2. Make sure USB Support (Edit vm > Console > USB Support) is enabled. 3. Connect to a different windows vm (7_x64) and install UsbDk_1.0.21_x64.msi (source: https://www.spice-space.org/download/windows/usbdk/UsbDk_1.0.21_x64.msi). 4. Connect to VM Portal and connect to the new windows vm (from step 1) through console. 5. Connect USB device by "File > USB device selection". Result: - USB device successfully connected WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:3247 |