Jerry Gilliam wrote: > > I am sponsoring this fast-track on behalf of Strony Zhang, > with a timeout set to 08/12/2009. The project desires > minor release binding.
That means no S10 version, so I guess virtualbox will be designed to work on systems both with and without this new interface? > -jg > > > ---------------------------------- > > Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > VirtualBox USB Device Capture > 1.2. Name of Document Author/Supplier: > Author: Strony.Zhang > 1.3 Date of This Document: > 04 Aug, 2009 > > 4. Technical Description [...] > Solution: > The usba(7D) provides the registration entry to VirtualBox for the > callback and makes the Virtual-specific USB client driver higher > priority than the default USB client driver. When a USB device is > plugged in the system, the usba(7D) will first call the registered > callback function to query if VirtualBox wants to capture the device. > If yes, the VirtualBox-specific USB client driver will be attached to > the device. Once the VirtualBox exits or user doesn't want to access the > USB device on guest OS, the VirtualBox will unregister the callback and > then Solaris will take over the USB device taken by VirtualBox. This seems to me to be lacking some necessary configuration. For example, if systems are configured with "exclude: scsa2usb" as a matter of site security, it would seem that I could bypass this by using virtualbox? Is it sensible to allow virtualbox to take over all USB devices without any configurability? If I plug in a USB device, let's say a memory stick, how does the system decide if native Solaris wants to use it, or an OS instance in Virtualbox, or which one across potentially several virtualboxes? -- Andrew
