[SOLVED]Virtualbox 4.0.8 USB problem (BUT not standard env.)
Posted: 26. Jun 2011, 14:27
Hi,
I am new in this Forum, and happy to join the community
... I have more experience using Vmware than Virtualbox BUT ...
Context :
I have do job to be able to run virtualbox on a Intel QNAP NAS (with restriction due to NO VT tech. (it's an ATOM multi-core but without VT))
QNAP run a (limited) not modifiable kernel 2.6.33.2 With lib and utility loaded each time from flash without possibility to mod the init shell and so ...
I choice solution to run inside the QNAP Linux a chroot env. based on Debian Squeeze
and INSIDE this chroot using the Virtualbox repository ... I install the Virtualbox 4.0.8 binary ...
After some mod. to compile the modules ... all is OK
Modules are loaded from the chroot ( I change the vbxodrv shell to use insmod in place of modprobe not available) ... the 3 modules load as well
I provide also a lighttpd server with only phpvirtualbox
and minimum X module need for client side (so we also can run GUI with an external X-Server).
also install : VM_VirtualBox_Extension_Pack 4.0.8 to used RDP
ALL run fine, tested with XP, Windows 2008, Ubuntu server 11.04 and some more (Android, etc.)
Shared resource work as well, Guestaddition when possible ... and RDP work fine (we are in NAS so the standard mode is Headless)
Problem ...
I can't use USB device connected to the QNAP in VirtualBox ... neither listed, neither seen after filter entry.
What I test :
1 ) configuration is as recommended, a virtualbox group (vboxusers) exist and is own /dev/vboxusb (this is correct in Native QNAP env. AND in chroot env. )
usbfs is mounted without arg. by QNAP ...
So I test :
add a mount usbfs with devgid and devmode in chroot ... KO
lsusb correct in QNAP and in chroot.
add a remount with gid and mode in QNAP (remember I can't change the initial init.d mount ... it's in flash before I have the hand ...)
then mount -o bind and /or mount usbfs with same value in chroot ... KO
lsusb correct, and we can see that folder in /proc/bus/usb have vboxusers as group ... (devgid) idem in chroot
So my question is :
Do you have any idea ??? test to do, way to search (I have not yet read all the technical docs.)
Do you thinks it's because I load modules in the chroot and not in native Linux ... (no impact on others services and tools)
I have also tested to add some parameters like I/O APIC ... without success ...
I am impress by the possibility of Virtualbox (more and more when as in QNAP we don't have VT ...) so lot of things run ... but at all I will be very happy if I can also have USB management.
Philippe.
I am new in this Forum, and happy to join the community
... I have more experience using Vmware than Virtualbox BUT ...Context :
I have do job to be able to run virtualbox on a Intel QNAP NAS (with restriction due to NO VT tech. (it's an ATOM multi-core but without VT))
QNAP run a (limited) not modifiable kernel 2.6.33.2 With lib and utility loaded each time from flash without possibility to mod the init shell and so ...
I choice solution to run inside the QNAP Linux a chroot env. based on Debian Squeeze
and INSIDE this chroot using the Virtualbox repository ... I install the Virtualbox 4.0.8 binary ...
After some mod. to compile the modules ... all is OK
Modules are loaded from the chroot ( I change the vbxodrv shell to use insmod in place of modprobe not available) ... the 3 modules load as well
I provide also a lighttpd server with only phpvirtualbox
and minimum X module need for client side (so we also can run GUI with an external X-Server).
also install : VM_VirtualBox_Extension_Pack 4.0.8 to used RDP
ALL run fine, tested with XP, Windows 2008, Ubuntu server 11.04 and some more (Android, etc.)
Shared resource work as well, Guestaddition when possible ... and RDP work fine (we are in NAS so the standard mode is Headless)
Problem ...
I can't use USB device connected to the QNAP in VirtualBox ... neither listed, neither seen after filter entry.
What I test :
1 ) configuration is as recommended, a virtualbox group (vboxusers) exist and is own /dev/vboxusb (this is correct in Native QNAP env. AND in chroot env. )
usbfs is mounted without arg. by QNAP ...
So I test :
add a mount usbfs with devgid and devmode in chroot ... KO
lsusb correct in QNAP and in chroot.
add a remount with gid and mode in QNAP (remember I can't change the initial init.d mount ... it's in flash before I have the hand ...)
then mount -o bind and /or mount usbfs with same value in chroot ... KO
lsusb correct, and we can see that folder in /proc/bus/usb have vboxusers as group ... (devgid) idem in chroot
So my question is :
Do you have any idea ??? test to do, way to search (I have not yet read all the technical docs.)
Do you thinks it's because I load modules in the chroot and not in native Linux ... (no impact on others services and tools)
I have also tested to add some parameters like I/O APIC ... without success ...
I am impress by the possibility of Virtualbox (more and more when as in QNAP we don't have VT ...) so lot of things run ... but at all I will be very happy if I can also have USB management.
Philippe.
