[Pkg-virtualbox-devel] Bug#594726: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND.

[Ludovic Rousseau]

2010/8/28 Felix Geyer <debfx-pkg at fobos.de>:
>  On 08/28/2010 08:29 PM, Ludovic Rousseau wrote:
>> $ sudo /etc/init.d/virtualbox-ose-guest-utils start
>> Starting VirtualBox Additions: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND.
>>  failed!
>>
>>
>> I can also reproduce the error message using:
>> $ VBoxService
>> : error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND.
> Why did you remove the virtualbox-ose-guest-dkms package?

I don't think I removed virtualbox-ose-guest-dkms package.
I see that virtualbox-ose-guest-utils has a Recommends: on it.

> Is the vboxdrv kernel module loaded?

Having now installed virtualbox-ose-guest-dkms I do not have vboxdrv
but vboxguest instead.

$ sudo modprobe vboxguest
$ sudo /etc/init.d/virtualbox-ose-guest-utils start
Starting VirtualBox AdditionsVBoxService: 3.2.8_OSE r64453 started.
Verbose level = 0
.

It looks like the problem is fixed once vboxguest is loaded.

>> I am using Debian as a guest system in VirtualBox 3.2.8 r64453 on Mac OS
>> X.
>>
>> I also note that I can't use a USB device (a CCID smart card reader)
>> inside the guest Debian.
>> lsusb is blocked in a system call and returns only when I unplug the USB
>> device.
>>
> VirtualBox OSE doesn't support passing through USB devices to the guest OS.

I do not use VirtualBox OSE on Mac OS X but the "full" version of VirtualBox.
Debian is run _inside_ the virtual machine.

But I still can't use my USB device.

> If you want USB support, you need to remove all virtualbox-ose-guest-*
> packages
> and install the guest additions from the iso image:
> http://www.virtualbox.org/manual/ch04.html#id2658274

I removed all the virtualbox-* packages and rebooted. I now have a
resolution of 800x600 only. And still not USB.

When I connect the USB device and attach it to the guest the guest the
guest kernel logs:
[   84.476306] usb 2-1: new full speed USB device using ohci_hcd and address 2
and then 5 seconds later:
[   99.642034] usb 2-1: device descriptor read/64, error -110

The device is not visible in the USB tree. Only the two USB hubs.
~$ find /dev/bus/usb/
/dev/bus/usb/
/dev/bus/usb/002
/dev/bus/usb/002/001
/dev/bus/usb/001
/dev/bus/usb/001/001

And lsusb is blocked in a iotcl():
[...)
munmap(0x7fabc5cd0000, 4096)            = 0
open("/dev/bus/usb", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 3
fcntl(3, F_GETFD)                       = 0x1 (flags FD_CLOEXEC)
getdents(3, /* 4 entries */, 32768)     = 96
close(3)                                = 0
open("/dev/bus/usb", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 3
getdents(3, /* 4 entries */, 32768)     = 96
getdents(3, /* 0 entries */, 32768)     = 0
close(3)                                = 0
open("/dev/bus/usb/002", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 3
getdents(3, /* 3 entries */, 32768)     = 72
open("/dev/bus/usb/002/001", O_RDWR)    = 4
ioctl(4, USBDEVFS_CONNECTINFO

The ioctl() finishes after 1 minute (or so) with no error but the USB
device is still not visible.

[...]
ioctl(4, USBDEVFS_CONNECTINFO, 0x7fff576ca430) = 0
read(4, "\22\1\0\2\t\0\0 at k\35\2\0\6\2\3\2\1\1", 18) = 18
read(4, "\t\2\31\0\1\1\0\340", 8)       = 8
read(4, "\0\t\4\0\0\1\t\0\0\0\7\5\201\3\4\0\f", 17) = 17
close(4)                                = 0
getdents(3, /* 0 entries */, 32768)     = 0
close(3)                                = 0
open("/dev/bus/usb/001/001", O_RDWR)    = 3
ioctl(3, USBDEVFS_IOCTL or USBDEVFS_IOCTL32, 0x7fff576ca430) = 9
close(3)                                = 0
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x7fabc5cd0000
write(1, "Bus 002 Device 001: ID 1d6b:0001"..., 63Bus 002 Device 001:
ID 1d6b:0001 Linux Foundation 1.1 root hub
) = 63
write(1, "Bus 001 Device 001: ID 1d6b:0002"..., 63Bus 001 Device 001:
ID 1d6b:0002 Linux Foundation 2.0 root hub
) = 63
exit_group(0)                           = ?

I guess the problem is with the Linux kernel and not with virtualbox
components. So you can close this bug unless you know what could be
the problem.

Thanks a lot for your time

-- 
 Dr. Ludovic Rousseau