Hide Forgot
Created attachment 1226511 [details] Screen shot of gnome-boxes Device tab enabling a Device and windows device manager reporting an error with the device. Description of problem: When a USB device is attached to the host machine (f24). gnome-boxes detects the device in its device list. When a device is turned on by the 'on switch' in gnobe-boxes visualizing windows 7, The visualized OS detects the device but cannot start it, error code 10. Multiple devices and different virtual installations of windows 7 yield the same result. Version-Release number of selected component (if applicable): 3.20.3-1.fc24 How reproducible: Steps to Reproduce: 1. Attach a USB device to Host machine running Fedora 24 2. Enable that device though gnome-boxes and the device "passes-though" 3. visualised windows 7 will report an error starting the device. Actual results: failed to start device. Expected results: Access to USB device via visualised OS. Additional info:
I am also running Spice-guest-tools-0.100 on the virtual windows 7, and spice-gtk form the latest repository build on the Fedora 24 host.
1-) Is it possible to see if redirecting this device in F25 works? 2-) Some debug info from the client could help. Please, reproduce the bug running in a terminal: SPICE_DEBUG=1 gnome-boxes > log 2>&1 3-) Can you attach the domain of you VM to check if this is configuration? virsh dumpxml name-of-your-vm If you are not sure about the name of your vm, virsh list --all should tell you.
Created attachment 1245426 [details] Win10 log
Created attachment 1245427 [details] Debian 8.6 Log
Created attachment 1245428 [details] CentOS 7 Log
Created attachment 1245429 [details] Win10 Domain
Created attachment 1245430 [details] Debian 8.6 Domain
Created attachment 1245431 [details] CentOS 7 Domain
Not the original submitter, but having the same issue in Fedora 25. Tested the following OS images and USB devices: - Guest OSes: CentOS 7, Debian 8.6, Windows 10 - USB devices: 128GB ext4 drive, 8GB Fat32 drive Results: - CentOS 7: 128GB drive not recognized, 8GB is recognized - Debian 8.6: Neither drive recognized - Windows 10: Neither drive recognized 1) As stated, the issue exists (at least for me) in F25. 2) Log for each of the 3 OS images listed above attached. 3) Domain XML file for each of the 3 OS images attached. Please comment if you need further details, or if there is further testing that can help identify the issue here.
Hi, problem still exist, I tested following scenario: Host: - Fedora 25 - Gnome Boxes version 3.22.4 Guest: - Windows 7 Home Premium - Spice version 0.132 In attachment you can see my log. If you need additional information or test I happy to help.
Created attachment 1272368 [details] Boxes_log
Created attachment 1272369 [details] Windows guest dump.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.