Closed jhgorse closed 8 years ago
also,
→ appcatalyst vm list
Info: VMs found in '/Users/jhg/Documents/AppCatalyst'
vagrant-2aa9f6ab-7ce3-4c60-9e3c-75ef8d034473
vagrant-bcfc75ce-f212-4d2f-a3a0-9277414ceb20
→ appcatalyst vm create test123
Error: Unable to connect to VIX host: One of the parameters was invalid
Exit 255
vmware-vix-4000.log: http://hastebin.com/bateyafuha
@jhgorse it's most likely a licensing issue, see here: http://blogs.vmware.com/cloudnative/appcatalyst-update/
@frapposelli so... what is next? I would really like to continue to use VMware (I own Fusion, not Pro) to do the sorts of things that vagrant does and at the same time maintain a "free" toolchain path for others as well.
I think what is currently limiting that is the lack of the clone feature in the VIX vmrun tool for regular non-Pro Fusion.
Download the new version that @frapposelli linked to. It's the last release and works until December.
# kill old version of appcatalyst
sudo pkill appcatalyst-daemon
# download new version of appcatalyst
open http://bit.ly/getappcatalyst
@zackhsi good eye. I stopped reading at: "The technology preview for AppCatalyst will end on the 30th of June 2016."
@frapposelli what would it take to get the app-catalyst-daemon interface on VMware Fusion?
Steps I take
Note: when I first ran this, VMware Fusion was running in the background. Subsequently, it has been shut down along with its vms, yet this error persists.
Vagrant output:
-daemon log for this event (note repeats):
vmware-vix-2353.log: http://hastebin.com/wozabusija is this a license issue?