virtual box not detecting USB devices

What is the output of:

lsb_release -a; uname -a; apt-cache policy virtualbox

Thanks

Here is the output:
john@john-H81M-S2H-GSM:~$ lsb_release -a; uname -a; apt-cache policy virtualbox
LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
Distributor ID: Ubuntu
Description: Ubuntu 15.10
Release: 15.10
Codename: wily
Linux john-H81M-S2H-GSM 4.2.0-27-generic #32-Ubuntu SMP Fri Jan 22 04:49:08 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
virtualbox:
  Installed: 5.0.14-dfsg-0ubuntu1.15.10.1
  Candidate: 5.0.14-dfsg-0ubuntu1.15.10.1
  Version table:
 *** 5.0.14-dfsg-0ubuntu1.15.10.1 0
        500 http://ca.archive.ubuntu.com/ubuntu/ wily-updates/multiverse amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ wily-security/multiverse amd64 Packages
        100 /var/lib/dpkg/status
     5.0.4-dfsg-2 0
        500 http://ca.archive.ubuntu.com/ubuntu/ wily/multiverse amd64 Packages
john@john-H81M-S2H-GSM:~$

Can you access your tomtom from Ubuntu?
Sometime using 'eject' in Ubuntu helps to let the virtual system access USB devices.

Set up Alt+L shift as a keyboard shortcut to eject media.
It opens my DVD drive but it does not connect with my Tomtom.
When I look at the USB tab in the Win10 settings on the guest machine I find that Enable USB Controller checked but greyed out.
Similarly the radio button for USB 1.1 (OHCI) Controller was checked but also greyed out
However I can add USB Device Filters

Opening the DVD tray is not what I was talking about.

Try something else:
With the Ubuntu system already running, plug in the Tomtom, wait half a minute and then issue the command (in a terminal window)

dmesg | tail

What output do you get?

Here is the output
john@john-H81M-S2H-GSM:~$ dmesg | tail
[ 5200.056887] usb 3-1.4.1: reset low-speed USB device number 7 using xhci_hcd
[ 5200.340529] usb 3-1.4.1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 5200.351192] input: Logitech Desktop USB stand as /devices/pci0000:00/0000:00:1c.3/0000:03:00.0/usb3/3-1/3-1.4/3-1.4.1/3-1.4.1:1.0/0003:046D:ABD0.0004/input/input17
[ 5200.405269] hid-generic 0003:046D:ABD0.0004: input,hiddev0,hidraw2: USB HID v1.10 Keyboard [Logitech Desktop USB stand] on usb-0000:03:00.0-1.4.1/input0
[ 5294.260311] usb 1-8: USB disconnect, device number 4
[ 5294.260380] cdc_ether 1-8:2.0 enx020406080a0c: unregister 'cdc_ether' usb-0000:00:14.0-8, CDC Ethernet Device
[ 5384.227697] usb 3-1.4.1: reset low-speed USB device number 7 using xhci_hcd
[ 5384.511173] usb 3-1.4.1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 5384.521493] input: Logitech Desktop USB stand as /devices/pci0000:00/0000:00:1c.3/0000:03:00.0/usb3/3-1/3-1.4/3-1.4.1/3-1.4.1:1.0/0003:046D:ABD0.0005/input/input18
[ 5384.576029] hid-generic 0003:046D:ABD0.0005: input,hiddev0,hidraw2: USB HID v1.10 Keyboard [Logitech Desktop USB stand] on usb-0000:03:00.0-1.4.1/input0
john@john-H81M-S2H-GSM:~$

Do you have USB2 and USB3 ports?
Can you try another one?

I have a mixture of USB2 and USB3
I was using a USB2 socket as I understand Virtualbox does not yet support USB3.
Changing the USB socket does not seem to do anything

Back to the dmesg output.
I do not see anything that clearly identifies the Tomtom.

Can you issue the command
lsusb
with the Tomtom disconnected,
plug it in, wait half a minute, and re-issue the command
lsusb
and then copy/paste the output into this question document.

john@john-H81M-S2H-GSM:~$ lsusb
Bus 006 Device 002: ID 8087:8000 Intel Corp.
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 03f0:bd07 Hewlett-Packard
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 006: ID 046d:c50c Logitech, Inc. Cordless Desktop S510
Bus 003 Device 007: ID 046d:abd0 Logitech, Inc.
Bus 003 Device 005: ID 0451:2036 Texas Instruments, Inc. TUSB2036 Hub
Bus 003 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 003: ID 046d:0821 Logitech, Inc. HD Webcam C910
Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 8087:8008 Intel Corp.
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
john@john-H81M-S2H-GSM:~$ lsusb
Bus 006 Device 002: ID 8087:8000 Intel Corp.
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 03f0:bd07 Hewlett-Packard
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 006: ID 046d:c50c Logitech, Inc. Cordless Desktop S510
Bus 003 Device 007: ID 046d:abd0 Logitech, Inc.
Bus 003 Device 005: ID 0451:2036 Texas Instruments, Inc. TUSB2036 Hub
Bus 003 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 003: ID 046d:0821 Logitech, Inc. HD Webcam C910
Bus 003 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 8087:8008 Intel Corp.
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 1390:5454 TOMTOM B.V. Blue & Me 2
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
john@john-H81M-S2H-GSM:~$
It looks like the Tomtom is being detected by Ubuntu but not in Virtualbox
Any suggestions?

If you re-try the exercise
disconnect the Tomtom, wait half a minute, plug it in, wait half a minute, what is then the output of
dmesg | tail

Here is the output:
john@john-H81M-S2H-GSM:~$ dmesg | tail
[ 4.937332] r8169 0000:02:00.0 enp2s0: link up
[ 4.937340] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
[ 16.602158] usb 3-1.1: reset high-speed USB device number 3 using xhci_hcd
[ 18.106839] EXT4-fs (sdb7): mounted filesystem with ordered data mode. Opts: (null)
[ 18.194137] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Opts: (null)
[ 144.852293] capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[ 151.180550] SUPR0GipMap: fGetGipCpu=0x3
[ 151.426130] vboxdrv: ffffffffc0648020 VMMR0.r0
[ 151.534781] vboxdrv: ffffffffc057e020 VBoxDDR0.r0
[ 151.536715] vboxdrv: ffffffffc0245020 VBoxDD2R0.r0
john@john-H81M-S2H-GSM:~$ dmesg | tail
[ 232.471135] usb 1-8: SerialNumber: BQ1364B90611
[ 232.488048] cdc_ether 1-8:2.0 usb0: register 'cdc_ether' at usb-0000:00:14.0-8, CDC Ethernet Device, 02:04:06:08:0a:0c
[ 232.489088] usbcore: registered new interface driver cdc_ether
[ 232.493281] cdc_ether 1-8:2.0 enx020406080a0c: renamed from usb0
[ 232.582838] IPv6: ADDRCONF(NETDEV_UP): enx020406080a0c: link is not ready
[ 232.582922] cdc_ether 1-8:2.0 enx020406080a0c: kevent 12 may have been dropped
[ 232.582926] cdc_ether 1-8:2.0 enx020406080a0c: kevent 12 may have been dropped
[ 232.583537] cdc_ether 1-8:2.0 enx020406080a0c: kevent 12 may have been dropped
[ 232.583668] cdc_ether 1-8:2.0 enx020406080a0c: kevent 12 may have been dropped
[ 232.583695] cdc_ether 1-8:2.0 enx020406080a0c: kevent 12 may have been dropped
john@john-H81M-S2H-GSM:~$

This still does not show what I expected to see.

Please try again plugging in the tomtom, and then issue the command
dmesg | tail -n 30

Here is the output.
I have virtual box running and then give the command dmesg | tail -n 30.
I then plugged in the usb and re ran the command.
john@john-H81M-S2H-GSM:~$ dmesg | tail -n 30
[ 4.937332] r8169 0000:02:00.0 enp2s0: link up
[ 4.937340] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
[ 16.602158] usb 3-1.1: reset high-speed USB device number 3 using xhci_hcd
[ 18.106839] EXT4-fs (sdb7): mounted filesystem with ordered data mode. Opts: (null)
[ 18.194137] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Opts: (null)
[ 144.852293] capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[ 151.180550] SUPR0GipMap: fGetGipCpu=0x3
[ 151.426130] vboxdrv: ffffffffc0648020 VMMR0.r0
[ 151.534781] vboxdrv: ffffffffc057e020 VBoxDDR0.r0
[ 151.536715] vboxdrv: ffffffffc0245020 VBoxDD2R0.r0
[ 232.342297] usb 1-8: new high-speed USB device number 2 using xhci_hcd
[ 232.471129] usb 1-8: New USB device found, idVendor=1390, idProduct=5454
[ 232.471132] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 232.471133] usb 1-8: Product: TomTom
[ 232.471134] usb 1-8: Manufacturer: Linux 2.6.28.10 with dwc_otg_pcd
[ 232.471135] usb 1-8: SerialNumber: BQ1364B90611
[ 232.488048] cdc_ether 1-8:2.0 usb0: register 'cdc_ether' at usb-0000:00:14.0-8, CDC Ethernet Device, 02:04:06:08:0a:0c
[ 232.489088] usbcore: registered new interface driver cdc_ether
[ 232.493281] cdc_ether 1-8:2.0 enx020406080a0c: renamed from usb0
[ 232.582838] IPv6: ADDRCONF(NETDEV_UP): enx020406080a0c: link is not ready
[ 232.582922] cdc_ether 1-8:2.0 enx020406080a0c: kevent 12 may have been dropped
[ 232.582926] cdc_ether 1-8:2.0 enx020406080a0c: kevent 12 may have been dropped
[ 232.583537] cdc_ether 1-8:2.0 enx020406080a0c: kevent 12 may have been dropped
[ 232.583668] cdc_ether 1-8:2.0 enx020406080a0c: kevent 12 may have been dropped
[ 232.583695] cdc_ether 1-8:2.0 enx020406080a0c: kevent 12 may have been dropped
[ 615.442520] usb 1-8: USB disconnect, device number 2
[ 615.442613] cdc_ether 1-8:2.0 enx020406080a0c: unregister 'cdc_ether' usb-0000:00:14.0-8, CDC Ethernet Device
[ 5936.109677] vboxdrv: ffffffffc0648020 VMMR0.r0
[ 5936.190523] vboxdrv: ffffffffc057e020 VBoxDDR0.r0
[ 5936.191505] vboxdrv: ffffffffc0245020 VBoxDD2R0.r0
john@john-H81M-S2H-GSM:~$ dmesg | tail -n 30
[ 232.471132] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 232.471133] usb 1-8: Product: TomTom
[ 232.471134] usb 1-8: Manufacturer: Linux 2.6.28.10 with dwc_otg_pcd
[ 232.471135] usb 1-8: SerialNumber: BQ1364B90611
[ 232.488048] cdc_ether 1-8:2.0 usb0: register 'cdc_ether' at usb-0000:00:14.0-8, CDC Ethernet Device, 02:04:06:08:0a:0c
[ 232.489088] usbcore: registered new interface driver cdc_ether
[ 232.493281] cdc_ether 1-8:2.0 enx020406080a0c: renamed from usb0
[ 232.582838] IPv6: ADDRCONF(NETDEV_UP): enx020406080a0c: link is not ready
[ 232.582922] cdc_ether 1-8:2.0 enx020406080a0c: kevent 12 may have been dropped
[ 232.582926] cdc_ether 1-8:2.0 enx020406080a0c: kevent 12 may have been dropped
[ 232.583537] cdc_ether 1-8:2.0 enx020406080a0c: kevent 12 may have been dropped
[ 232.583668] cdc_ether 1-8:2.0 enx020406080a0c: kevent 12 may have been dropped
[ 232.583695] cdc_ether 1-8:2.0 enx020406080a0c: kevent 12 may have been dropped
[ 615.442520] usb 1-8: USB disconnect, device number 2
[ 615.442613] cdc_ether 1-8:2.0 enx020406080a0c: unregister 'cdc_ether' usb-0000:00:14.0-8, CDC Ethernet Device
[ 5936.109677] vboxdrv: ffffffffc0648020 VMMR0.r0
[ 5936.190523] vboxdrv: ffffffffc057e020 VBoxDDR0.r0
[ 5936.191505] vboxdrv: ffffffffc0245020 VBoxDD2R0.r0
[ 5998.958358] usb 1-8: new high-speed USB device number 3 using xhci_hcd
[ 5999.087220] usb 1-8: New USB device found, idVendor=1390, idProduct=5454
[ 5999.087223] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5999.087224] usb 1-8: Product: TomTom
[ 5999.087225] usb 1-8: Manufacturer: Linux 2.6.28.10 with dwc_otg_pcd
[ 5999.087226] usb 1-8: SerialNumber: BQ1364B90611
[ 5999.088539] cdc_ether 1-8:2.0 usb0: register 'cdc_ether' at usb-0000:00:14.0-8, CDC Ethernet Device, 02:04:06:08:0a:0c
[ 5999.102505] cdc_ether 1-8:2.0 enx020406080a0c: renamed from usb0
[ 5999.130383] IPv6: ADDRCONF(NETDEV_UP): enx020406080a0c: link is not ready
[ 5999.130551] cdc_ether 1-8:2.0 enx020406080a0c: kevent 12 may have been dropped
[ 5999.132630] cdc_ether 1-8:2.0 enx020406080a0c: kevent 12 may have been dropped
[ 5999.132641] cdc_ether 1-8:2.0 enx020406080a0c: kevent 12 may have been dropped
john@john-H81M-S2H-GSM:~$

It is a bit unexpected to see that Ubuntu apparently classifies the tomtom as Ethernet device.

Can you suggest a workaround?

You wrote in one of your first comments "Enable USB Controller checked but greyed out."

I assume you have the current virtualbox extension pack installed on Ubuntu and activated inside the Windows guest system, have added your Ubuntu user name to the vboxusers group, and also enabled USB support in virtualbox. You might re-check with the first answer in http://askubuntu.com/questions/25596/how-to-set-up-usb-for-virtualbox

Can you make a screen shot of the settings page where the USB settings are greyed out and upload it to some image hosting service?

You might also try http://www.tomtom.com/support
There are some reports of people who had success connecting and updating their tomtom in a similar setup (Linux with Windows in a virtual system).

And searching the internet also suggests some alternatives running on Linux: pyTomTom and jTomTom, but both with only limited capabilities.

Thank you for your continued interest and help
I am using VirtualBox 5.0.14_Ubuntur105127 and had not installed the extension pack.
Have downloaded the Extension pack, a SDK package, but I am having trouble installing it.
The VB on-line manual suggests a Network controller appears if I double click on the package but that is not happening.
How do I install it in a terminal and where do I install it?

With my Virtual Machine shut down I was able to add the USB device and when I plug or unplug my Tomtom I get the windows sound.
The USB tab in my virtual machine now looks like this: https://www.dropbox.com/s/kltjidpv8il1wmq/Screenshot%20from%202016-02-15%2014-18-36.png?dl=0

However the Tomtom is not connected according to Tomtoms program. Here is a screenshot: https://www.dropbox.com/s/brdw2sa57309q9r/Screenshot%20from%202016-02-15%2015-03-50.png?dl=0

A windows sound is already a good sign.

Maybe enabling remote in the USB settings dialogue helps
http://www.arvydas.co.uk/wp-content/uploads/2011/02/USB-Filter-Details.png

Do you have the Guest extensions installed?
If not, download http://download.virtualbox.org/virtualbox/5.0.14/Oracle_VM_VirtualBox_Extension_Pack-5.0.14-105127.vbox-extpack to your Ubuntu system and open it with virtualbox.
Afterwards inside Windows use the Virtualbox menu entry Devices - Install Guest Extensions...

Thank you for your help.
Downloaded and installed the Guest extensions.
Enabling the remote USB settings meant I had to physically connect the Tomtom each time I plugged it in whereas the Any option did it automatically.
However the Tomtom program is not recognizing the device as connected.
Is that because the Tomtom program is seeing a Unix machine rather than a Windows machine.
When I tried getting the Tomtom program to tell me what sort of device I had it thought I was running a Mac

You might look in the Windows Device Manager what you see there about the Tomtom.

The Tomtom shows up in the Windows device manager but cannot start.
This device cannot start (Code 10)
(Operation Failed)
The requested operation was unsuccessful.
The driver is the best one according to Windows 10

Sorry to say, but I am running out of ideas.

Manfred,
Thank you for all your help.
I deleted my virtual machine and rebuilt it taking advantage of all the work you had done.
The new virtual machine let me update my Tomtom