[Bug 1205737] New: USB passthrough not working for Win 7 client in Virtualbox 7.04
http://bugzilla.opensuse.org/show_bug.cgi?id=1205737 Bug ID: 1205737 Summary: USB passthrough not working for Win 7 client in Virtualbox 7.04 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs@suse.de Reporter: timothyadams@ymail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 863110 --> http://bugzilla.opensuse.org/attachment.cgi?id=863110&action=edit /var/log/virtualbox.log Symptoms are similar to those reported in Bug 1204331. https://bugzilla.opensuse.org/show_bug.cgi?id=1204331 When I start either of two USB scanners in the Win 7 client, I get the Windows error: * * * One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it. The location of the device is shown in bold type. * USB Root hub (12 ports) - Unknown Device * * * As it may help in troubleshooting, I'd better mention that the 6.1.38 bug referred to in: https://forums.opensuse.org/showthread.php/576712-VirtualBox-with-enabled-US... was not present with 6.1.38 in kubuntu. In kubuntu, 6.1.38 passthrough worked fine. I need to use these scanners, so have restored an earlier snapshot and locked virtualbox files at version 6.1.40. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205737 Andreas Stieger <Andreas.Stieger@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Larry.Finger@gmail.com, | |llrainey15@gmail.com Assignee|virt-bugs@suse.de |Larry.Finger@gmail.com QA Contact|qa-bugs@suse.de |virt-bugs@suse.de -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205737 http://bugzilla.opensuse.org/show_bug.cgi?id=1205737#c1 --- Comment #1 from Larry Rainey <llrainey15@gmail.com> --- I can attach fine in Windows 10 and Windows 11. You have to install the 7.0.4 guest additions in Windows and the extension pack in the host for it to work. The extension pack will not install properly if any of VirtualBox is running. You have to reboot the host after installing 7.0.4 or you will still have the old kernel module for 6.1.40 loaded. I suggest that you 1st stop all virtualbox running. then remove the old pieces zypper rm virtualbox virtualbox-kmp-default virtualbox-qt then install 7.0.4 zypper in virtualbox virtualbox-kmp-default virtualbox-qt add the extension pack for 7.0.4 and reboot. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205737 http://bugzilla.opensuse.org/show_bug.cgi?id=1205737#c2 --- Comment #2 from T Adams <timothyadams@ymail.com> --- First, Larry, thanks for the quick response. I printed out your instructions, and followed them to the letter, with one exception: I also had virtualbox-host-source installed, and added it to the list of files to 'zypper rm' and 'zypper in.' So: I now have installed: virtualbox virtualbox-host-source virtualbox-kmp-default virtualbox-qt All version 7.0.4 I used VBoxManage to install the new extension pack, and made sure to install the 7.0.4 guest additions before trying the scanner. I remembered to reboot, as you suggested. Unfortunately: same results as before, with the same Windows "One of the USB devices attached to this computer has malfunctioned" error message. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205737 http://bugzilla.opensuse.org/show_bug.cgi?id=1205737#c3 --- Comment #3 from Larry Rainey <llrainey15@gmail.com> --- Is the failure in Linux VirtualBox or Windows 7 Guest Additions? The Windows guest additions are not part of the Tumbleweed Virtualbox as they are copyright by Oracle. If it is the Windows guest additions - they are now done by the OpenSUSE team but by Oracle Virtualbox and they need to get the logs from you to see what failed. The Oracle Virtualbox forum is the place to put the bug information in the Windows guests section. I am wondering if the scanner is not freeing from the Linux driver when the Devices > USB > USB Settings selects the scanner. I don't have a USB scanner to test with. I test with USB camera, USB to nvme converter, USB to SSD converter, USB 2 flash drive, and a USB 3 flash drive. They all work in windows 10, 11 and back in Tumbleweed. I am trying to remember Windows 7 - I think it had USB 3 support. Have you tried the USB 2 in the Windows 7 config instead of the USB 3 to see if it is the Virtualbox USB pass thru? What does the lsusb show for the scanner in Tumbleweed? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205737 http://bugzilla.opensuse.org/show_bug.cgi?id=1205737#c4 --- Comment #4 from T Adams <timothyadams@ymail.com> --- I download the extension pack and guest additions from https://download.virtualbox.org/virtualbox/, don't remember ever having gotten them another way. The "One of the USB devices attached to this computer has malfunctioned" message comes from within the Windows 7 client itself. I use two scanners through the Win 7 client, and the problem affects both. I again restored the working 6.1.40 snapshot, and will post again here if I do more troubleshooting. I then can try different USB configurations in Win 7 and see what lsusb shows for the scanner in Tumbleweed, as you suggest. I understand that I may be in the lurch if other users aren't affected by this issue. There may be something odd in my setup. Larry, thanks again for your response, and for your work on VB for openSUSE. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205737 http://bugzilla.opensuse.org/show_bug.cgi?id=1205737#c5 --- Comment #5 from Larry Rainey <llrainey15@gmail.com> --- The Oracle Guest Additions and Extension Packs are Oracle only. And are copyright so we cannot touch them. We do not get the source code for them - we do build a "Guest Addition" for openSUSE Linux guests with permission from Oracle to do so. You need to go to the VirtualBox forum and fill out a problem report for Windows 7 guest and 7.0.4. If you run 15.3 or 15.4 you could try the Oracle VirtualBox 7.0.4 for 15.3 - it works for both and it is how I compare our 7.0.4 build to Oracles - there are slight differences that have to be done to make it build in Open Build System. Most are to allow the compiler options to build and not error out due to openSUSE security requirements that Oracle does not code for yet. There are still a lot of minor problems reported to Oracle on VirtualBox 7.0.4, I suspect that 7.0.6 release is not far behind. The day we got 7.0.2 to build in OBS, 7.0.4 came out. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205737 http://bugzilla.opensuse.org/show_bug.cgi?id=1205737#c6 --- Comment #6 from Larry Finger <Larry.Finger@gmail.com> --- I do have a USB scanner - a Canoscan LIDE 200, which is a USB 2 device. My testing, so far, results are as follows: Using a fully updated fresh install of a TW VM without installing any Guest Additions in guest. 7.0.4 additions in host, using xsane for scan program: openSUSE Tumbleweed host - Tumbleweed guest - USB 3 port: Everything works. openSUSE Tumbleweed host - Tumbleweed guest - USB 2 port: Everything works. Both ports initially got a garbled input and had to be disconnected and xsane restarted. After installing Guest Additions 7.0.4: openSUSE Tumbleweed host - Tumbleweed guest - USB 3 port: Everything works. openSUSE Tumbleweed host - Tumbleweed guest - USB 2 port: Everything works. Again, it took some fiddling to get the correct output from xsane. With a Windows 7 VM, the device manager reports that the driver is unable to start for either USB2 or 3. With a Windows 10 VM and using the driver for Windows 8.1, which is reported to work, the Device Manager says the "The device reported an I/O error." I reinstalled the driver and the Guest Extensions without any effect. To test if the problem was that suspect Windows driver, I installed the driver and software for an Epson V600, which works on my wife's Windows 10 machine. Again the I/O error resulted. It appears that the problem is only with Windows, other than the problems getting a correct connection in Linux, but that may not be new. I have only done scanning with the host until this test. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205737 http://bugzilla.opensuse.org/show_bug.cgi?id=1205737#c7 --- Comment #7 from T Adams <timothyadams@ymail.com> --- Larry Finger, I feel vindicated, as you're seeing the same issue in Win VMs... and also optimistic. If this problem is present in both Win 7 and Win 10 VMs, I'm not an orphan, and feel confident that it will be addressed eventually. I think it might be best to stand pat with 6.1.40 for awhile until the fix comes in, perhaps with 7.0.6. Thanks very much to both of you for your attention and feedback. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205737 http://bugzilla.opensuse.org/show_bug.cgi?id=1205737#c8 --- Comment #8 from T Adams <timothyadams@ymail.com> --- Problem solved (in a way), thanks to a bug report on virtualbox.org: https://www.virtualbox.org/ticket/21312 I reduced memory on the Win7 VM to 2048 MB and fired up one scanner, then the other. Both worked properly in the Win7 VM! I need only remember to reduce memory to 2048 MB when I want to scan something. This feels like a stopgap solution, so I won't close this bug report. Please feel free to close it as solved, if you think it should be closed. Please also let me know if you think I should post a thread with this information on the virtualbox forum. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205737 http://bugzilla.opensuse.org/show_bug.cgi?id=1205737#c9 --- Comment #9 from Larry Finger <Larry.Finger@gmail.com> --- If reducing the guest memory "fixes" the problem, then the real cause is a bug in Win 7, but we both know that will not be fixed. You should probably add your findings to VirtualBox defect ticket 21312, but it is unlikely that Oracle will take any action. I will leave this Bug open, but do not expect me to try to debug this problem. I have worked nearly full-time getting Version 7.0.X to build correctly on openSUSE, and I am exhausted. At 82, I may be getting too old for this. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205737 http://bugzilla.opensuse.org/show_bug.cgi?id=1205737#c10 --- Comment #10 from T Adams <timothyadams@ymail.com> --- I added a comment to the ticket: https://www.virtualbox.org/ticket/21312#comment:1 Larry, you've made a tremendous contribution to VirtualBox in openSUSE over the years, and are entitled to rest! -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com