Discuss the 4.0.6 Release
-
- Oracle Corporation
- Posts: 3362
- Joined: 7. Jun 2007, 09:11
- Primary OS: Debian Sid
- VBox Version: PUEL
- Guest OSses: Linux, Windows
- Location: Dresden, Germany
- Contact:
Discuss the 4.0.6 Release
This topic is for discussing the 4.0.6 release.
-
- Posts: 1
- Joined: 7. Jul 2009, 17:23
- Primary OS: MS Windows 2008
- VBox Version: PUEL
- Guest OSses: OpenSolaris
Failed to access the USB subsystem.
when ever I access the settings of a VM, I get a dialog box - labelled as a warning, that virtualbox has failed to access the USB subsystem.
here are the details:
Result Code:
E_FAIL (0x00004005)
Component:
Host
Interface:
IHost {35b004f4-7806-4009-bfa8-d1308adba7e5}
Callee:
IMachine {662c175e-a69d-40b8-a77a-1d719d0ab062}
here are the details:
Result Code:
E_FAIL (0x00004005)
Component:
Host
Interface:
IHost {35b004f4-7806-4009-bfa8-d1308adba7e5}
Callee:
IMachine {662c175e-a69d-40b8-a77a-1d719d0ab062}
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Discuss the 4.0.6 Release
@pbelb ,
Did you install the Extension Pack?
Did you install the Extension Pack?
-
- Volunteer
- Posts: 3342
- Joined: 10. May 2007, 16:59
- Location: Israel
Re: Discuss the 4.0.6 Release
Congrats on the new release !
-Technologov
-Technologov
-
- Posts: 24
- Joined: 9. May 2010, 06:37
- Primary OS: Mac OS X Leopard
- VBox Version: PUEL
- Guest OSses: Windows
Re: Discuss the 4.0.6 Release
Thanks for update.
However, using Mac OS X (10.6.7) host, updating to 4.0.6 from 4.0.4 resulted in some shared folders not showing/detected in both Win7 (64bit) and Win 2000 guests.
Reverted to 4.0.4 and everything functioning normally.
Peter
PS Extension pack etc were installed.
However, using Mac OS X (10.6.7) host, updating to 4.0.6 from 4.0.4 resulted in some shared folders not showing/detected in both Win7 (64bit) and Win 2000 guests.
Reverted to 4.0.4 and everything functioning normally.
Peter
PS Extension pack etc were installed.
-
- Posts: 93
- Joined: 17. May 2010, 01:10
- Primary OS: MS Windows 7
- VBox Version: OSE other
- Guest OSses: Linux
Re: Discuss the 4.0.6 Release
When will the "removit" option start to work?
-
- Posts: 3
- Joined: 13. Feb 2011, 10:23
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Archlinux, CentOS, Windows
Re: Failed to access the USB subsystem.
The same problem here. Here is how is problem manifested on my computer:pbelb wrote:when ever I access the settings of a VM, I get a dialog box - labelled as a warning, that virtualbox has failed to access the USB subsystem.
here are the details:
Result Code:
E_FAIL (0x00004005)
Component:
Host
Interface:
IHost {35b004f4-7806-4009-bfa8-d1308adba7e5}
Callee:
IMachine {662c175e-a69d-40b8-a77a-1d719d0ab062}
First had a corruption of VM after upgrading from Vbox 4.0.4. (it wasn't big deal, I wanted to upgrade to new folder structure anyway - had old folder structure from 3.2.x release)
Removed everything and made a clean install of this new version Vbox and extensions.
Created new VM (Windows XP SP3), needed to close vbox for a couple of minutes, when I came back to proceed with configuration before install, got this message.
Is it safe to continue with installation, or is there any other solution of this problem ?
-
- Posts: 3
- Joined: 22. Apr 2011, 10:00
- Primary OS: Ubuntu other
- VBox Version: OSE Debian
- Guest OSses: FreeBSD
- Location: Tel-Aviv
Re: Discuss the 4.0.6 Release
confirming this on my machine after upgrading from 4.0.4 to 4.0.6 the host machine is running ubuntu 10.04.2
usb devices not recognized by the vm
already tried removing VB and reinstalling it, and also tried installing the matching extpack, Oracle_VM_VirtualBox_Extension_Pack-4.0.6-71344.
get the same warning, "failed to access the usb subsystem", NS_ERROR_FAILURE (0x00004005).
usb devices not recognized by the vm
already tried removing VB and reinstalling it, and also tried installing the matching extpack, Oracle_VM_VirtualBox_Extension_Pack-4.0.6-71344.
get the same warning, "failed to access the usb subsystem", NS_ERROR_FAILURE (0x00004005).
Edit: rebuilding the dynamic kernel module and rebooting the host did not solve the problem for me. the host is running 2.6.32-31-generic. going back to 4.0.4 for now. |
Last edited by efraty on 22. Apr 2011, 13:42, edited 1 time in total.
Re: Discuss the 4.0.6 Release
Unfortunately I can confirm this bug (USB not working) on Fedora 14 (Linux 2.6.35.12-88.fc14.x86_64 x86_64).
After downgrading to VirtualBox 4.0.4 I can access all my USB devices again.
After downgrading to VirtualBox 4.0.4 I can access all my USB devices again.
-
- Posts: 3
- Joined: 22. Apr 2011, 14:29
- Primary OS: Ubuntu other
- VBox Version: PUEL
- Guest OSses: Windows XP
Re: Discuss the 4.0.6 Release
Seeing this failure as well on Xubuntu 10.04.2, 64-bit 2.6.32-31-generic. Prior to upgrade from 4.0.4, USB "just worked;" now I see the error when entering the settings dialog and no USB devices are visible to the guests. Updated extensions to the 4.0.6 version with no improvement.
Re: Discuss the 4.0.6 Release
Host: Ubuntu 10.10 64-bit - kernel 2.6.35-28-generic
Guest: Windows XP Pro SP3 32-bit
VirtualBox 4.0.4 + VirtualBox 4.0.2 Oracle VM VirtualBox Extension Pack ==> no error, USB devices work
VirtualBox 4.0.6 + VirtualBox 4.0.6 Oracle VM VirtualBox Extension Pack ==> NS_ERROR_FAILURE (0x00004005), USB devices do not work
Note the error shows up when clicking "Settings" in the Oracle VM VirtualBox Manager.
I am using the Synaptic Package Manager, does anyone know how to tell it to revert back to 4.0.4?
Mike
Guest: Windows XP Pro SP3 32-bit
VirtualBox 4.0.4 + VirtualBox 4.0.2 Oracle VM VirtualBox Extension Pack ==> no error, USB devices work
VirtualBox 4.0.6 + VirtualBox 4.0.6 Oracle VM VirtualBox Extension Pack ==> NS_ERROR_FAILURE (0x00004005), USB devices do not work
Note the error shows up when clicking "Settings" in the Oracle VM VirtualBox Manager.
I am using the Synaptic Package Manager, does anyone know how to tell it to revert back to 4.0.4?
Mike
-
- Posts: 3
- Joined: 22. Apr 2011, 10:00
- Primary OS: Ubuntu other
- VBox Version: OSE Debian
- Guest OSses: FreeBSD
- Location: Tel-Aviv
Re: Discuss the 4.0.6 Release
http://www.virtualbox.org/wiki/Download_Old_Builds_4_0mmorris wrote:does anyone know how to tell it to revert back to 4.0.4?
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Discuss the 4.0.6 Release
For those having issues with the USB not working in 4.0.6.
How many upgraded VirtualBox while the guest was in a saved state and not shut down?
The reason I ask is there was a change in the USB subset from 4.0.4 and issues were worked out during building. I upgraded from 4.0.4 to 4.0.6 today including the Ext. Pack and do not have this issue. Also I noticed that if I did not upgrade the Extension Pack the USB was not available (greyed out) but it did not produce an error message which is understandable.
Another question is were these VirtualBox upgrades or from a distro VirtualBox upgrades?
How many upgraded VirtualBox while the guest was in a saved state and not shut down?
The reason I ask is there was a change in the USB subset from 4.0.4 and issues were worked out during building. I upgraded from 4.0.4 to 4.0.6 today including the Ext. Pack and do not have this issue. Also I noticed that if I did not upgrade the Extension Pack the USB was not available (greyed out) but it did not produce an error message which is understandable.
Another question is were these VirtualBox upgrades or from a distro VirtualBox upgrades?
-
- Posts: 7
- Joined: 17. Feb 2010, 21:07
- Primary OS: openSUSE
- VBox Version: OSE other
- Guest OSses: openSUSE 64bit, Windows 7 64bit, Windows XP 32bit
- Location: Germany
Re: Discuss the 4.0.6 Release
I can confirm this USB error (Result Code: E_FAIL (0x00004005)) on my Win7 Pro x86_64 machine after upgrading from 4.0.4 to 4.0.6 (including extension pack). It shows up whenever I try to edit any of the VM settings.
However, on my Linux 2.6.35.10 x86_64 machine there seems to be no such error after upgrading. I used the following packages:
- http://download.virtualbox.org/virtualb ... _amd64.run
- http://download.virtualbox.org/virtualb ... ox-extpack
As I currently do not need any USB support I am going to stay with the 4.0.6 version.
However, on my Linux 2.6.35.10 x86_64 machine there seems to be no such error after upgrading. I used the following packages:
- http://download.virtualbox.org/virtualb ... _amd64.run
- http://download.virtualbox.org/virtualb ... ox-extpack
As I currently do not need any USB support I am going to stay with the 4.0.6 version.
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Discuss the 4.0.6 Release
OK I finally got this on a Windows 7 host. Upgraded and installed new Ext. Pack. (all guests shut down)
Started the guest selected the USB device and the USB failed when Windows was installing the driver.
Closed the guest and VirtualBox and made sure that nothing VirtualBox was listed in the task manager and then started VirtualBox. This is where I got the message of missing USB subsystem and starting the guest shows that it is not available.
Login off and back in does not clear this up. Rebooting the host however did fix this for me.
Started the guest selected the USB device and the USB failed when Windows was installing the driver.
Closed the guest and VirtualBox and made sure that nothing VirtualBox was listed in the task manager and then started VirtualBox. This is where I got the message of missing USB subsystem and starting the guest shows that it is not available.
Login off and back in does not clear this up. Rebooting the host however did fix this for me.