MSP-FET with Energia, mspdebug, or virtualized CCS6?

I received my MSP-FET yesterday-- thank you TI! I was so excited to try out everything. I was deflated to find out that my package only contained the programmer-- hopefully the target board and MSP430FR6989s will arrive soon. It almost felt like Christmas morning-- only to find out the batteries were not included!

I wanted to test out my new toy so I hooked up the MSP-FET to some MSP430 chips I hand nearby. I hooked up the MSP-FET to a MSP430G2231 and started Energia on Mac OS X 10.9.4. Although the MSP-FET is seen by the OS, I can't seem to connect to it. On System Info, the vendor/product ID are 0x2047/0x0014 with a description of "MSP Tools Driver."

Here are my issues

1) Energia can't connect. If I use File -> Upload, or File -> Upload using programmer, I get "usbutil: unable to find a device matching 0451:f432"

2) If I use mspdebug, I can't connect using tilib or uif.

$ mspdebug --usb-list
Devices on bus 250:
    250:006 2047:0014  [serial: EFF2blahblah]
    250:005 05ac:0245 
    250:002 0424:2513 
    250:001 05ac:8006 
Devices on bus 253:
    253:001 05ac:8006

$ mspdebug tilib
MSPDebug version 0.22 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2013 Daniel Beer <dlbeer@gmail.com>
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

MSP430_GetNumberOfUsbIfs
No unused FET found.

$mspdebug uif  
MSPDebug version 0.22 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2013 Daniel Beer <dlbeer@gmail.com>
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

usbutil: unable to find a device matching 0451:f430

I tried specifying the USB device by adding -U 250:006 but no improvement. Does mspdebug v 0.22 not work with the MSP-FET? Is this a libmsp430.so issue? I was using the one supplied with the latest version of Energia (E0013).

3) If I run CCS6 under VirtualBox, things sort of work. When I start a debug session, I get a message

"Error initializing emulator: