Supported OSes
Workstation, Player and Fusion support passing individual Bluetooth devices in these cases:
- Linux guests: ALL
- Mac OS guests: ALL
- Windows guests: XP SP1 and later
- Linux hosts: ALL
- Mac OS hosts: ALL
- Windows hosts: XP SP1 and later
Note: Both the host and the guest must be supported.
Windows has multiple Bluetooth stacks; an official Microsoft stack and a few vendor-specific stacks. The Microsoft stack (by far the most common) is the only stack supported on the host.
Supported device classes
Workstation and Fusion support passing these classes of Bluetooth devices:
- Cell phones
- GPS receivers
- Serial Port Profile (SPP) devices
- Most other devices
Workstation and Fusion offer limited support for these classes of Bluetooth devices:
- Input devices (HID): Can be attached to guests when using Linux/Mac OS hosts, but not on Windows hosts.
- OBEX File Transfer: Outgoing (guest to device) transfers only. Guest may not act as an OBEX server.
Workstation and Fusion do not support passing these classes of Bluetooth devices:
- Headphones, headsets, hands-free audio devices
Limitations
Workstation and Fusion have these limitations for Bluetooth support:
- Outgoing connections only. A virtual machine may establish a connection to a remote Bluetooth device, but remote devices do not see services that virtual machines try to advertise.
- Virtual machines cannot change the name, class, or discoverability of the host's Bluetooth adapter. The host is exclusively in control over setting whether other Bluetooth devices can discover the host, and what name it appears as.
- The host is exclusively in control of the pairing process and collecting/displaying PIN numbers. The guest may scan for devices, and initiate a connection with any device. If pairing is required, the pairing dialog box appears on the host, not in the guest. From the guest's perspective, the device appears to pair without having needed a PIN.
- Any vendor-specific capabilities on the host's Bluetooth radio are not passed through to the guest. For example, some radios provide a vendor-specific command to change their BDADDR. These commands do not appear in the guest. The guest sees a generic VMware-brand radio.
- The virtual Bluetooth controller itself is not part of snapshots. During snapshots, it is disconnected and reconnected. Any ongoing connections with Bluetooth devices are terminated at the time of a snapshot.
仮想マシンとの Bluetooth デバイスの共有与虚拟机共享蓝牙设备