1 |
On 05/26/2011 01:53 AM, Valmor de Almeida wrote: |
2 |
> On 05/25/2011 07:45 PM, Valmor de Almeida wrote: |
3 |
>> On 05/25/2011 06:14 PM, Mark Knecht wrote: |
4 |
>> [snip] |
5 |
>>>> |
6 |
>>>> For the record. |
7 |
>>>> |
8 |
>>>> Tried and it is very nice. The 4.0.6 version with extpack uses the GPL |
9 |
>>>> vbox (source). |
10 |
>>>> |
11 |
>>>> All usb devices on the gentoo host are visible on a Windows7 guest. The |
12 |
>>>> problem I am facing now is that the Windows7 virtual machine tries to |
13 |
>>>> install drivers for the USB devices and it fails. Not sure what is going |
14 |
>>>> on... It may be an issue with USB 1.0 versus 2.0? |
15 |
>>>> |
16 |
>>>> |
17 |
>>>> -- |
18 |
>>>> Valmor |
19 |
>>> |
20 |
>>> Hi Valmor, |
21 |
>>> Good to know it at least gets you 1 step further in the right direction. |
22 |
>>> |
23 |
>>> As for Win 7 installing USB drivers is there an option to not |
24 |
>>> install it automatically and then you go look for the right driver and |
25 |
>>> install it by hand? |
26 |
>>> |
27 |
>>> One other possibility might be that either Linux or another VM is |
28 |
>>> claiming the device and hence it's not responding correctly to the |
29 |
>>> driver install. i typically run 3 VMs every day - 2 VMPLayer/XP and 1 |
30 |
>>> virtualbox/Win 7. I've noted that I have to be a little careful to |
31 |
>>> ensure the VMs don't interfere with each other WRT USB devices. |
32 |
>>> |
33 |
>>> Good luck figuring it out. Please post back if you find interesting info. |
34 |
>>> |
35 |
>>> Cheers, |
36 |
>>> Mark |
37 |
>>> |
38 |
>> |
39 |
>> I think you are in the right track as far as a race between host and |
40 |
>> guest for claiming the device. It is not the driver installation that is |
41 |
>> the problem. The driver is installed and Windows7 says it is the latest |
42 |
>> driver. The problem is that at the end of the installation W7 tries to |
43 |
>> mount/start the device and that is when things do not work. The status |
44 |
>> of the device is listed as |
45 |
>> |
46 |
>> This device cannot start. (Code 10) |
47 |
>> |
48 |
>> There is quite a bit on the web on the "Code 10" error. Still |
49 |
>> investigating... |
50 |
>> |
51 |
>> fdisk -l on the gentoo host lists the device if the guest is not |
52 |
>> running. As soon as the guest boots, the device is not listed by fdisk |
53 |
>> -l, this means that things are at least going in the right direction. |
54 |
>> The vbox manual says that the device should be hidden from the host once |
55 |
>> the guest gets a hold of it. |
56 |
>> |
57 |
>> |
58 |
>> |
59 |
>> -- |
60 |
>> Valmor |
61 |
> |
62 |
> After much digging, no success. Apparently it is an ongoing bug. |
63 |
> |
64 |
> http://bugs.gentoo.org/show_bug.cgi?id=364717 |
65 |
> |
66 |
> When virtualbox is installed with the extension USE flag it pulls the |
67 |
> oracle extension package and the USB interface on the Virtualbox manager |
68 |
> is supposed to present a USB 2.0 box. This does not show up. Therefore |
69 |
> it appears that USB 2.0 devices can't start on the VM guest since only |
70 |
> USB 1.0 is enabled. |
71 |
> |
72 |
> No luck so far but it is pretty close to be resolved. All USB devices I |
73 |
> have tried are identified by the Win7 VM guest and the drivers correctly |
74 |
> installed. It is only the startup that fails. |
75 |
> |
76 |
> That is all folks. |
77 |
> |
78 |
> -- |
79 |
> Valmor |
80 |
|
81 |
Those involved in dealing with the bug link above have concluded: |
82 |
|
83 |
This bug can stay confirmed as it's quite obvious that USB-2 doesn't work: |
84 |
|
85 |
So no USB-2 support on >=virtualbox-4.0.6 at the moment. |
86 |
|
87 |
-- |
88 |
Valmor |