Hi,
I experienced Virtualbox 4.3.14 x86_64 as broken, when I tried to sync an iPad2 with iTunes running on a XP SP3 guest. I only tested it with USB2 enabled, since it worked with 4.3.12.
Usually I use the packages virtualbox, virtualbox-host-dkms, virtualbox-extension-pack and I add the guest additions, that fit to the used vbox version.
Because I wasted much time with trying to use 4.3.14, I did an incomplete downgrade to 4.3.12 yet, since I'm short in time, but even with
virtualbox 4.3.12-1 virtualbox-host-dkms 4.3.12-1 no extension pack, no USB2 and with wrong guest additions, version 4.3.14, I get rid of the issues.
I will complete the downgrade on my machine ASAP and IMO the community packages should be downgraded for the repositories too.
Do others experienced issues with Virtualbox 4.3.14 USB too?
Since I'm short in time I only reported the bug to https://bugs.archlinux.org/task/41424 I didn't find a related bug, just 4 completely other vbox bug reports.
https://www.virtualbox.org/search?q=4.13.14&noquickjump=1&ticket=on results in "No matches found." https://www.virtualbox.org/search?q=usb&noquickjump=1&ticket=on gives tons of hits, no time to care about them right now
Regards, Ralf
I have experienced problems with USB also. My guest is Windows 8.1. When I try to access the USB device from Windows, the access fails and then everything inside the VM seems to start misbehaving. I cannot properly shutdown the VM - I have to kill the VBox process.
If I don't try to use the USB device, everything works fine.
Cheers, Marco
On Fri, Aug 1, 2014 at 1:15 PM, Ralf Mardorf ralf.mardorf@rocketmail.com wrote:
Hi,
I experienced Virtualbox 4.3.14 x86_64 as broken, when I tried to sync an iPad2 with iTunes running on a XP SP3 guest. I only tested it with USB2 enabled, since it worked with 4.3.12.
Usually I use the packages virtualbox, virtualbox-host-dkms, virtualbox-extension-pack and I add the guest additions, that fit to the used vbox version.
Because I wasted much time with trying to use 4.3.14, I did an incomplete downgrade to 4.3.12 yet, since I'm short in time, but even with
virtualbox 4.3.12-1 virtualbox-host-dkms 4.3.12-1 no extension pack, no USB2 and with wrong guest additions, version 4.3.14, I get rid of the issues.
I will complete the downgrade on my machine ASAP and IMO the community packages should be downgraded for the repositories too.
Do others experienced issues with Virtualbox 4.3.14 USB too?
Since I'm short in time I only reported the bug to https://bugs.archlinux.org/task/41424 I didn't find a related bug, just 4 completely other vbox bug reports.
https://www.virtualbox.org/search?q=4.13.14&noquickjump=1&ticket=on results in "No matches found." https://www.virtualbox.org/search?q=usb&noquickjump=1&ticket=on gives tons of hits, no time to care about them right now
Regards, Ralf
On Mon, 2014-08-04 at 20:15 +0100, Marco Monteiro wrote:
I have experienced problems with USB also. My guest is Windows 8.1. When I try to access the USB device from Windows, the access fails and then everything inside the VM seems to start misbehaving. I cannot properly shutdown the VM - I have to kill the VBox process.
Hi Marco,
when the USB data transfer paused, the graphic performance and access to the VDI drive slowed down, for iTunes and other apps running on the XP guest. Performance for iTunes always is bad, but other apps usually run without issues. I always could shut down Windows, but sometimes much time was needed before I could use the menu. If you can't shutdown your guest, you could try to shut down the virtual machine by closing the VBox window, instead off killing the process.
I add an additional comment to my bug report.
"There isn't an issue for the USB mouse, but data transfer between VBox and an iPad2 is broken when I use 4.3.14. There aren't issues anymore, after I downgraded all packages to 4.3.12. The whole performance of Vbox is slower when syncing iTunes and an iPad with .14 and there are many unknown errors and timeouts, if you e.g. try to install 20 applications or more from iTunes running on the VBox guest to an iPad. Disconnecting the iPad's USB causes VBox to crash, if it is done without unchecking the iPad in VBox's devices menu, this doesn't happen when using .12.
The used packages are virtualbox, virtualbox-host-dkms, virtualbox-extension-pack and I install the guest additions that fit to the installed version of virtualbox. Perhaps the culprit isn't the package virtualbox, it might be the package virtualbox-extension-pack, since it's needed for USB2 support." - https://bugs.archlinux.org/task/41424
JFTR everything already was ok, when I only downgraded the package virtualbox, disabled USB2 support and kept the 4.3.14 guest additions. In the mean time I downgraded all packages and add the 4.3.12 guest additions, so with the outdated version I now can use USB2 again.
Perhaps you have the time confirm my bug report.
Regards, Ralf
Hi,
I have also issues with USB devices on Windows 7 32Bit guest. The devices I use are mainly USB Serial COM ports. On top of that a proprietary binary protocol is used.
The applications that communicate with the USB Serial COM ports are constantly having problems reading and writing data.
Installed: virtualbox 4.3.14-3 virtualbox-guest-iso 4.3.14-1 virtualbox-guest-modules 4.3.14-5 virtualbox-host-modules 4.3.14-5 Linux localhost 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux
Extension Pack 4.3.14r95030
With usbmon and wireshark I could see a lot of malformed USB packets. I'm afraid I don't know enough to make an exact conclusion whats wrong in detail.
I will try a downgrad from 4.3.14-3 to 4.3.12 and report again.
Am 04.08.2014 um 22:05 schrieb Ralf Mardorf:
On Mon, 2014-08-04 at 20:15 +0100, Marco Monteiro wrote:
I have experienced problems with USB also. My guest is Windows 8.1. When I try to access the USB device from Windows, the access fails and then everything inside the VM seems to start misbehaving. I cannot properly shutdown the VM - I have to kill the VBox process.
Hi Marco,
when the USB data transfer paused, the graphic performance and access to the VDI drive slowed down, for iTunes and other apps running on the XP guest. Performance for iTunes always is bad, but other apps usually run without issues. I always could shut down Windows, but sometimes much time was needed before I could use the menu. If you can't shutdown your guest, you could try to shut down the virtual machine by closing the VBox window, instead off killing the process.
I add an additional comment to my bug report.
"There isn't an issue for the USB mouse, but data transfer between VBox and an iPad2 is broken when I use 4.3.14. There aren't issues anymore, after I downgraded all packages to 4.3.12. The whole performance of Vbox is slower when syncing iTunes and an iPad with .14 and there are many unknown errors and timeouts, if you e.g. try to install 20 applications or more from iTunes running on the VBox guest to an iPad. Disconnecting the iPad's USB causes VBox to crash, if it is done without unchecking the iPad in VBox's devices menu, this doesn't happen when using .12.
The used packages are virtualbox, virtualbox-host-dkms, virtualbox-extension-pack and I install the guest additions that fit to the installed version of virtualbox. Perhaps the culprit isn't the package virtualbox, it might be the package virtualbox-extension-pack, since it's needed for USB2 support." - https://bugs.archlinux.org/task/41424
JFTR everything already was ok, when I only downgraded the package virtualbox, disabled USB2 support and kept the 4.3.14 guest additions. In the mean time I downgraded all packages and add the 4.3.12 guest additions, so with the outdated version I now can use USB2 again.
Perhaps you have the time confirm my bug report.
Regards, Ralf
I downgraded and have postive results.
Currently installed:
virtualbox 4.2.18-1 virtualbox-guest-iso 4.2.18-1 virtualbox-host-modules 4.2.18-7 linux 3.11.6-1
No USB read/write problems any more. I still get Malformed Packet in Wireshark, but this seems unrelated.
However now I receive crashes of my VM when attaching/detaching USB devices to my VM often. Guess I have to live with that.
Am 03.09.2014 um 12:54 schrieb Peter Bauer:
Hi,
I have also issues with USB devices on Windows 7 32Bit guest. The devices I use are mainly USB Serial COM ports. On top of that a proprietary binary protocol is used.
The applications that communicate with the USB Serial COM ports are constantly having problems reading and writing data.
Installed: virtualbox 4.3.14-3 virtualbox-guest-iso 4.3.14-1 virtualbox-guest-modules 4.3.14-5 virtualbox-host-modules 4.3.14-5 Linux localhost 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux
Extension Pack 4.3.14r95030
With usbmon and wireshark I could see a lot of malformed USB packets. I'm afraid I don't know enough to make an exact conclusion whats wrong in detail.
I will try a downgrad from 4.3.14-3 to 4.3.12 and report again.
Am 04.08.2014 um 22:05 schrieb Ralf Mardorf:
On Mon, 2014-08-04 at 20:15 +0100, Marco Monteiro wrote:
I have experienced problems with USB also. My guest is Windows 8.1. When I try to access the USB device from Windows, the access fails and then everything inside the VM seems to start misbehaving. I cannot properly shutdown the VM - I have to kill the VBox process.
Hi Marco,
when the USB data transfer paused, the graphic performance and access to the VDI drive slowed down, for iTunes and other apps running on the XP guest. Performance for iTunes always is bad, but other apps usually run without issues. I always could shut down Windows, but sometimes much time was needed before I could use the menu. If you can't shutdown your guest, you could try to shut down the virtual machine by closing the VBox window, instead off killing the process.
I add an additional comment to my bug report.
"There isn't an issue for the USB mouse, but data transfer between VBox and an iPad2 is broken when I use 4.3.14. There aren't issues anymore, after I downgraded all packages to 4.3.12. The whole performance of Vbox is slower when syncing iTunes and an iPad with .14 and there are many unknown errors and timeouts, if you e.g. try to install 20 applications or more from iTunes running on the VBox guest to an iPad. Disconnecting the iPad's USB causes VBox to crash, if it is done without unchecking the iPad in VBox's devices menu, this doesn't happen when using .12.
The used packages are virtualbox, virtualbox-host-dkms, virtualbox-extension-pack and I install the guest additions that fit to the installed version of virtualbox. Perhaps the culprit isn't the package virtualbox, it might be the package virtualbox-extension-pack, since it's needed for USB2 support." - https://bugs.archlinux.org/task/41424
JFTR everything already was ok, when I only downgraded the package virtualbox, disabled USB2 support and kept the 4.3.14 guest additions. In the mean time I downgraded all packages and add the 4.3.12 guest additions, so with the outdated version I now can use USB2 again.
Perhaps you have the time confirm my bug report.
Regards, Ralf
On Wed, 2014-09-03 at 14:10 +0200, Peter Bauer wrote:
However now I receive crashes of my VM when attaching/detaching USB devices to my VM often. Guess I have to live with that.
Downgrading solved all my USB issues with the XP guest. I experienced VBox to crash, when disconnecting USB, only for the updated version. I could avoid the crashes, by un-checking the USB device in VBox's device menu, before unplugging it.
Hi,
I needed to downgrade again.
Using Windows XP (32 bit) Service Pack 3 as guest, in 2014-10-21 I upgraded iTunes to 12.0.1.26 and iOS 8.0.2 -> iOS 8.1 to an iPad 2 by an USB connection.
In 2014-10-28 I upgraded virtualbox 4.3.12-1 -> 4.3.18-1.
This month upgrading iOS 8.1 -> 8.1.1 by an USB connection failed.
So I run
# dkms remove -m vboxhost -v 4.3.18 --all # downgrade virtualbox virtualbox-host-dkms virtualbox-guest-iso # pacman -R virtualbox-ext-oracle # pacman -U /var/cache/aur/virtualbox-extension-pack-4.3.12-1-x86_64.pkg.tar.xz
# dkms install vboxhost/4.3.12 -k 3.14.23-rt20-1-rt worked :) # dkms install vboxhost/4.3.12 -k 3.10.58-rt62-2-rt-lts worked :)
_But_ unfortunately it doesn't work for the current kernel:
# dkms install vboxhost/4.3.12 -k $(uname -r)
Kernel preparation unnecessary for this kernel. Skipping...
Building module: cleaning build area.... make KERNELRELEASE=3.17.3-1-ARCH -C /usr/lib/modules/3.17.3-1-ARCH/build M=/var/lib/dkms/vboxhost/4.3.12/build........................(bad exit status: 2) Error! Bad return status for module build on kernel: 3.17.3-1-ARCH (x86_64) Consult /var/lib/dkms/vboxhost/4.3.12/build/make.log for more information.
I suspect this issue already startet after upgrading 3.16.4-1 -> 3.17.1-1. I upgraded virtualbox 4.3.12-1 -> 4.3.18-1, because building the modules for the kernel didn't work anymore.
Any ideas how to build the vbox modules for the current linux package?
Regards, Ralf
PS: Now I try upgrading iOS 8.1 -> 8.1.1 using virtualbox 4.3.12-1. Perhaps virtualbox 4.3.18-1 isn't the culprit, but since I experienced a few USB issues before, I have good reason to expect that it will solve the issue.
On Sat, 2014-11-22 at 14:01 +0100, Ralf Mardorf wrote:
# pacman -R virtualbox-ext-oracle # pacman -U /var/cache/aur/virtualbox-extension-pack-4.3.12-1-x86_64.pkg.tar.xz
Now USB works again, the iOS upgrade didn't cause an issue, even while I still had 4.3.18 guest additions installed on the Windows guest while upgrading iOS.
Devices > Insert Guest Additions... has to be done manually, to downgrade to 4.3.12.
Still odd that we still have a broken virtualbox package in the repositories. When there's no interest to stay with a stable version, then perhaps virtualbox should be dropped from the repositories and become an AUR package. Following upstream when the software is broken IMO doesn't make sense. Sure, current version of virtualbox USB works for mouse and to transfer small amounts of data by USB, but it is completely useless to transmit huge amounts of data.
OT: Does anybody know, if it's possible to import a virtualbox vdi to another VM? If so, I would consider to switch to another VM.
Regards, Ralf
On 11/22, Ralf Mardorf wrote:
Still odd that we still have a broken virtualbox package in the repositories. When there's no interest to stay with a stable version, then perhaps virtualbox should be dropped from the repositories and become an AUR package. Following upstream when the software is broken IMO doesn't make sense. Sure, current version of virtualbox USB works for mouse and to transfer small amounts of data by USB, but it is completely useless to transmit huge amounts of data.
How much data are you trying to transmit? Based on your messages, I'm guessing you have an iPod Touch or iPhone and you're using VB to manage a music library. Calling VirtualBox broken because its USB implementation doesn't play well with Apple's DRM model is unfair, and your single experience doesn't amount to an objectively broken package. In any case, Arch follows upstream. Occasionally users experience setbacks. That's just the nature of the game.
OT: Does anybody know, if it's possible to import a virtualbox vdi to another VM? If so, I would consider to switch to another VM.
http://wiki.archlinux.og/index.php/Virtualbox
On Sat, 22 Nov 2014 11:54:04 -0600 Bigby James bigby.james@crepcran.com wrote:
How much data are you trying to transmit? Based on your messages, I'm guessing you have an iPod Touch or iPhone and you're using VB to manage a music library. Calling VirtualBox broken because its USB implementation doesn't play well with Apple's DRM model is unfair, and your single experience doesn't amount to an objectively broken package. In any case, Arch follows upstream. Occasionally users experience setbacks. That's just the nature of the game.
As I already pointed out, I tried to upgrade iOS of an iPad 2 by USB. I don't listen to music by crappy lossy codecs, anyway, using an USB mouse and transmitting an app, a PDF or text file, a few pics does work, but could also require a restart of the host. Everything works fine after downgrading virtualbox. I'm not the only one and it's not the first package that is broken and btw. I don't use any DRM crap and I dislike Apple myself, I won the iPad, however, the USB issue is _not_ caused by Apple, virtualbox is broken. You should read all threads about this issue and you should read them completely instead of guessing.
Regards, Ralf
Hi Ralf,
Following upstream when the software is broken IMO doesn't make sense.
Arch Linux policy is to follow upstream whenever it's possible and things generally work. A bug with USB doesn't mean VirtualBox is broken. Please submit a bug to the upstream, and use the older version for now.
Arch is not Debian stable. You get fresh packages (a plus), which sometimes may not work (a minus). It's your choice what you prefer most. I for one have to stay on MESA 10.1.4, otherwise I'd experience random hangs a few times a day.
IgnorePkg = llvm lib32-llvm lib32-llvm-libs llvm-libs ati-dri lib32-ati-dri mesa lib32-mesa mesa-libgl lib32-mesa-libgl svga-dri lib32-svga-dri xf86-video-ati
On Sat, 22 Nov 2014 20:25:16 +0100 Nowaker enwukaer@gmail.com wrote:
Following upstream when the software is broken IMO doesn't make sense.
Arch Linux policy is to follow upstream whenever it's possible and things generally work. A bug with USB doesn't mean VirtualBox is broken. Please submit a bug to the upstream, and use the older version for now.
Arch is not Debian stable. You get fresh packages (a plus), which sometimes may not work (a minus). It's your choice what you prefer most. I for one have to stay on MESA 10.1.4, otherwise I'd experience random hangs a few times a day.
IgnorePkg = llvm lib32-llvm lib32-llvm-libs llvm-libs ati-dri lib32-ati-dri mesa lib32-mesa mesa-libgl lib32-mesa-libgl svga-dri lib32-svga-dri xf86-video-ati
Hi Damian,
all released packages > 4.3.12 suffered from the same bug. It was reported to the Arch bugtracker. Around the same time there was a serious upstream bug for Evolution too, but it get fixed with the next released package and even if it wouldn't have been fixed yet, just down grading and keeping an older version of sqlite (or for other software other packages) is not an issue. Unfortunately downgrading virtualbox (dkms) doesn't work with the current kernel version, IMO this is something completely different. I can downgrade, because I use other kernels too.
IOW I know how to use Arch Linux, I'm aware about Arch's policy, that's why I'm using it. IMO virtualbox has to be better maintained or it should be moved to AUR.
Why should I report a bug that already is reported? It's not wanted to report a bug that already was reported.
https://www.virtualbox.org/ticket/13575
And as you can see, it's not related to Apple. And not everybody who does use Apple, does automatically use DRM and other crap.
Some people might use vim and/or other similar software and just like the hardware of the iPad, https://itunes.apple.com/us/app/vim/id492668168?mt=8 .
Regards, Ralf
On 11/22, Ralf Mardorf wrote:
Unfortunately downgrading virtualbox (dkms) doesn't work with the current kernel version, IMO this is something completely different. I can downgrade, because I use other kernels too.
You're saying that running 'dkms autoinstall' after downgrading VirtualBox doesn't work?
On Sat, 22 Nov 2014 14:59:13 -0600 Bigby James bigby.james@crepcran.com wrote:
On 11/22, Ralf Mardorf wrote:
Unfortunately downgrading virtualbox (dkms) doesn't work with the current kernel version, IMO this is something completely different. I can downgrade, because I use other kernels too.
You're saying that running 'dkms autoinstall' after downgrading VirtualBox doesn't work?
https://lists.archlinux.org/pipermail/arch-general/2014-November/037866.html
Regards, Ralf
I need to downgrad systemd to keep my system working with the older kernel (3.11.6-1). I received huge amount of errors in when I ran tail -f /var/log/messages:
Sep 5 18:49:38 localhost kernel: cdb[0]=0x28: 28 00 00 38 07 28 00 00 08 00 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Unhandled sense code Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: Result: hostbyte=0x07 driverbyte=0x08 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: Sense Key : 0x4 [current] Sep 5 18:49:38 localhost kernel: Info fld=0x0 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: ASC=0x0 ASCQ=0x0 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] CDB: Sep 5 18:49:38 localhost kernel: cdb[0]=0x28: 28 00 00 38 07 30 00 00 08 00 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Unhandled sense code Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: Result: hostbyte=0x07 driverbyte=0x08 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: Sense Key : 0x4 [current] Sep 5 18:49:38 localhost kernel: Info fld=0x0 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: ASC=0x0 ASCQ=0x0 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] CDB: Sep 5 18:49:38 localhost kernel: cdb[0]=0x28: 28 00 00 38 07 38 00 00 08 00 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Unhandled sense code Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: Result: hostbyte=0x07 driverbyte=0x08 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: Sense Key : 0x4 [current] Sep 5 18:49:38 localhost kernel: Info fld=0x0 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: ASC=0x0 ASCQ=0x0 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] CDB: Sep 5 18:49:38 localhost kernel: cdb[0]=0x28: 28 00 00 38 07 40 00 00 08 00 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Unhandled sense code
This could be cause by my internal SD-Card-Reader. I have a Lenovo X230 tablet.
I copied old versions from /var/cache/pacman/pkg/ downgraded following packages:
pacman -U syslog-ng-3.5.6-1-x86_64.pkg.tar.xz systemd-sysvcompat-216-3-x86_64.pkg.tar.xz libsystemd-216-3-x86_64.pkg.tar.xz systemd-216-3-x86_64.pkg.tar.xz lib32-systemd-216-2-x86_64.pkg.tar.xz
My IgnPkg line in /etc/pacman.conf is getting ridicolous:
IgnorePkg = virtualbox virtualbox-guest-iso virtualbox-guest-modules virtualbox-host-modules linux syslog-ng systemd-sysvcompat libsystemd systemd lib32-systemd
All this just to keep USB passtrough working. Hopefully gnome will not make a dependency on a systemd version. Then I will be really f*.
Am 03.09.2014 um 14:10 schrieb Peter Bauer:
I downgraded and have postive results.
Currently installed:
virtualbox 4.2.18-1 virtualbox-guest-iso 4.2.18-1 virtualbox-host-modules 4.2.18-7 linux 3.11.6-1
No USB read/write problems any more. I still get Malformed Packet in Wireshark, but this seems unrelated.
However now I receive crashes of my VM when attaching/detaching USB devices to my VM often. Guess I have to live with that.
Am 03.09.2014 um 12:54 schrieb Peter Bauer:
Hi,
I have also issues with USB devices on Windows 7 32Bit guest. The devices I use are mainly USB Serial COM ports. On top of that a proprietary binary protocol is used.
The applications that communicate with the USB Serial COM ports are constantly having problems reading and writing data.
Installed: virtualbox 4.3.14-3 virtualbox-guest-iso 4.3.14-1 virtualbox-guest-modules 4.3.14-5 virtualbox-host-modules 4.3.14-5 Linux localhost 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux
Extension Pack 4.3.14r95030
With usbmon and wireshark I could see a lot of malformed USB packets. I'm afraid I don't know enough to make an exact conclusion whats wrong in detail.
I will try a downgrad from 4.3.14-3 to 4.3.12 and report again.
Am 04.08.2014 um 22:05 schrieb Ralf Mardorf:
On Mon, 2014-08-04 at 20:15 +0100, Marco Monteiro wrote:
I have experienced problems with USB also. My guest is Windows 8.1. When I try to access the USB device from Windows, the access fails and then everything inside the VM seems to start misbehaving. I cannot properly shutdown the VM - I have to kill the VBox process.
Hi Marco,
when the USB data transfer paused, the graphic performance and access to the VDI drive slowed down, for iTunes and other apps running on the XP guest. Performance for iTunes always is bad, but other apps usually run without issues. I always could shut down Windows, but sometimes much time was needed before I could use the menu. If you can't shutdown your guest, you could try to shut down the virtual machine by closing the VBox window, instead off killing the process.
I add an additional comment to my bug report.
"There isn't an issue for the USB mouse, but data transfer between VBox and an iPad2 is broken when I use 4.3.14. There aren't issues anymore, after I downgraded all packages to 4.3.12. The whole performance of Vbox is slower when syncing iTunes and an iPad with .14 and there are many unknown errors and timeouts, if you e.g. try to install 20 applications or more from iTunes running on the VBox guest to an iPad. Disconnecting the iPad's USB causes VBox to crash, if it is done without unchecking the iPad in VBox's devices menu, this doesn't happen when using .12.
The used packages are virtualbox, virtualbox-host-dkms, virtualbox-extension-pack and I install the guest additions that fit to the installed version of virtualbox. Perhaps the culprit isn't the package virtualbox, it might be the package virtualbox-extension-pack, since it's needed for USB2 support." - https://bugs.archlinux.org/task/41424
JFTR everything already was ok, when I only downgraded the package virtualbox, disabled USB2 support and kept the 4.3.14 guest additions. In the mean time I downgraded all packages and add the 4.3.12 guest additions, so with the outdated version I now can use USB2 again.
Perhaps you have the time confirm my bug report.
Regards, Ralf
I accidently upgraded VirtualBox, systemd and linux. The problem I had with USB passtrough are gone. I don't know at which version they were resolved, as reference here my currently installed versions:
core/linux 3.18.5-1 (base) community/virtualbox 4.3.20-4
Am 03.12.2014 um 09:46 schrieb Peter Bauer:
I need to downgrad systemd to keep my system working with the older kernel (3.11.6-1). I received huge amount of errors in when I ran tail -f /var/log/messages:
Sep 5 18:49:38 localhost kernel: cdb[0]=0x28: 28 00 00 38 07 28 00 00 08 00 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Unhandled sense code Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: Result: hostbyte=0x07 driverbyte=0x08 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: Sense Key : 0x4 [current] Sep 5 18:49:38 localhost kernel: Info fld=0x0 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: ASC=0x0 ASCQ=0x0 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] CDB: Sep 5 18:49:38 localhost kernel: cdb[0]=0x28: 28 00 00 38 07 30 00 00 08 00 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Unhandled sense code Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: Result: hostbyte=0x07 driverbyte=0x08 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: Sense Key : 0x4 [current] Sep 5 18:49:38 localhost kernel: Info fld=0x0 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: ASC=0x0 ASCQ=0x0 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] CDB: Sep 5 18:49:38 localhost kernel: cdb[0]=0x28: 28 00 00 38 07 38 00 00 08 00 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Unhandled sense code Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: Result: hostbyte=0x07 driverbyte=0x08 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: Sense Key : 0x4 [current] Sep 5 18:49:38 localhost kernel: Info fld=0x0 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Sep 5 18:49:38 localhost kernel: ASC=0x0 ASCQ=0x0 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] CDB: Sep 5 18:49:38 localhost kernel: cdb[0]=0x28: 28 00 00 38 07 40 00 00 08 00 Sep 5 18:49:38 localhost kernel: sd 8:0:0:0: [sdb] Unhandled sense code
This could be cause by my internal SD-Card-Reader. I have a Lenovo X230 tablet.
I copied old versions from /var/cache/pacman/pkg/ downgraded following packages:
pacman -U syslog-ng-3.5.6-1-x86_64.pkg.tar.xz systemd-sysvcompat-216-3-x86_64.pkg.tar.xz libsystemd-216-3-x86_64.pkg.tar.xz systemd-216-3-x86_64.pkg.tar.xz lib32-systemd-216-2-x86_64.pkg.tar.xz
My IgnPkg line in /etc/pacman.conf is getting ridicolous:
IgnorePkg = virtualbox virtualbox-guest-iso virtualbox-guest-modules virtualbox-host-modules linux syslog-ng systemd-sysvcompat libsystemd systemd lib32-systemd
All this just to keep USB passtrough working. Hopefully gnome will not make a dependency on a systemd version. Then I will be really f*.
Am 03.09.2014 um 14:10 schrieb Peter Bauer:
I downgraded and have postive results.
Currently installed:
virtualbox 4.2.18-1 virtualbox-guest-iso 4.2.18-1 virtualbox-host-modules 4.2.18-7 linux 3.11.6-1
No USB read/write problems any more. I still get Malformed Packet in Wireshark, but this seems unrelated.
However now I receive crashes of my VM when attaching/detaching USB devices to my VM often. Guess I have to live with that.
Am 03.09.2014 um 12:54 schrieb Peter Bauer:
Hi,
I have also issues with USB devices on Windows 7 32Bit guest. The devices I use are mainly USB Serial COM ports. On top of that a proprietary binary protocol is used.
The applications that communicate with the USB Serial COM ports are constantly having problems reading and writing data.
Installed: virtualbox 4.3.14-3 virtualbox-guest-iso 4.3.14-1 virtualbox-guest-modules 4.3.14-5 virtualbox-host-modules 4.3.14-5 Linux localhost 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux
Extension Pack 4.3.14r95030
With usbmon and wireshark I could see a lot of malformed USB packets. I'm afraid I don't know enough to make an exact conclusion whats wrong in detail.
I will try a downgrad from 4.3.14-3 to 4.3.12 and report again.
Am 04.08.2014 um 22:05 schrieb Ralf Mardorf:
On Mon, 2014-08-04 at 20:15 +0100, Marco Monteiro wrote:
I have experienced problems with USB also. My guest is Windows 8.1. When I try to access the USB device from Windows, the access fails and then everything inside the VM seems to start misbehaving. I cannot properly shutdown the VM - I have to kill the VBox process.
Hi Marco,
when the USB data transfer paused, the graphic performance and access to the VDI drive slowed down, for iTunes and other apps running on the XP guest. Performance for iTunes always is bad, but other apps usually run without issues. I always could shut down Windows, but sometimes much time was needed before I could use the menu. If you can't shutdown your guest, you could try to shut down the virtual machine by closing the VBox window, instead off killing the process.
I add an additional comment to my bug report.
"There isn't an issue for the USB mouse, but data transfer between VBox and an iPad2 is broken when I use 4.3.14. There aren't issues anymore, after I downgraded all packages to 4.3.12. The whole performance of Vbox is slower when syncing iTunes and an iPad with .14 and there are many unknown errors and timeouts, if you e.g. try to install 20 applications or more from iTunes running on the VBox guest to an iPad. Disconnecting the iPad's USB causes VBox to crash, if it is done without unchecking the iPad in VBox's devices menu, this doesn't happen when using .12.
The used packages are virtualbox, virtualbox-host-dkms, virtualbox-extension-pack and I install the guest additions that fit to the installed version of virtualbox. Perhaps the culprit isn't the package virtualbox, it might be the package virtualbox-extension-pack, since it's needed for USB2 support." - https://bugs.archlinux.org/task/41424
JFTR everything already was ok, when I only downgraded the package virtualbox, disabled USB2 support and kept the 4.3.14 guest additions. In the mean time I downgraded all packages and add the 4.3.12 guest additions, so with the outdated version I now can use USB2 again.
Perhaps you have the time confirm my bug report.
Regards, Ralf
arch-general@lists.archlinux.org