The menu is Devices » USB » ... exactly as mentioned in the on-the-fly section of the instructions, which is the method you want to use.
The main thing to understand here is what a VM is, how does it work and how it handles hardware. A VM uses for the most part a virtual CPU (one or more cores from the real one), part of the RAM, a virtual graphics subsystem and a virtual drive, that's it. Just because the VM is running doesn't mean it can access and use the stuff connected by USB. As a matter of fact, this is exactly the beginning of the instructions:
USB devices cannot be shared at the bus level. That means that two computers (a host and a guest) cannot share the same device. Think of it as having a USB stick, a printer, a webcam or a WiFi adapter hooked into two computers at the same time. You simply can't.
Unfortunately this whole discussion suggests your expectations were very different than what can be done in reality. No, in order to use the device in the VM it need to be "detached" (become unavailable) from the host OS first. The guide provides two methods, one transient via a point-and-click menu, and one "permanent" (as long as Virtualbox and that VM are running) that sequesters the device as soon as it detects it. The "permanent" way, via USB filter, does indeed require "Vendor ID" and Product ID". Those can be obtained with 'lsusb'. Example:
Code:
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
In the above example (Bluetooth USB dongle), the Vendor ID=0a12 and the Product ID=0001
Whether or not you should have the drivers/software already installed I don't know but it should be the exact same way as in a bare-metal installation. When the device is passed to the guest via Virtualbox menu that is exactly the same as connecting the device in a normal installation, the (guest) OS behaves the same indicating "new hardware found", plays a sound, etc.
32-bit or 64-bit doesn't matter unless the required drivers/software only run in one or another.
If this is hard to understand - it shouldn't be... - then consider using supported hardware instead. Only you can know how valuable your time is. I certainly wouldn't have spent even half of that just to make a piece of museum work.
Bookmarks