Closed symgryph closed 9 years ago
looks like veewee was not bale to find one of this paths:
/Library/Application Support/VMware Fusion/vmrun
/Applications/VMware Fusion.app/Contents/Library/vmrun
/usr/local/bin/vmrun
in what path is your Fusion installed? can you find it with:
which vmrun
Most of the files live in :
/Applications/"VMware Fusion.app"/Contents/Library/
These days.
On Mon, Dec 29, 2014 at 1:08 PM, Michal Papis notifications@github.com wrote:
looks like veewee was not bale to find one of this paths:
/Library/Application Support/VMware Fusion/vmrun /Applications/VMware Fusion.app/Contents/Library/vmrun /usr/local/bin/vmrun
in what path is your Fusion installed? can you find it with:
which vmrun
— Reply to this email directly or view it on GitHub https://github.com/jedi4ever/veewee/issues/1023#issuecomment-68281463.
Two Wheels Good, Four Wheels Bad
I did symlink a bunch of them(after your advice) but still get this even with all binaries in this location : I also did a 'which vmrun' and nothing came up.
/usr/local/lib/ruby/gems/2.1.0/gems/fission-0.5.0/lib/fission/vm.rb:528:in `all_running': uninitialized constant Fission::Action (NameError)
from /usr/local/lib/ruby/gems/2.1.0/gems/fission-0.5.0/lib/fission/vm.rb:405:in `running?'
from /usr/local/lib/ruby/gems/2.1.0/gems/fission-0.5.0/lib/fission/vm.rb:326:in `state'
from /Users/tjmunn/veewee/lib/veewee/provider/vmfusion/box/destroy.rb:11:in `destroy'
from /Users/tjmunn/veewee/lib/veewee/provider/core/box/build.rb:28:in `kickstart'
from /Users/tjmunn/veewee/lib/veewee/provider/core/box/build.rb:113:in `build'
from /Users/tjmunn/veewee/lib/veewee/provider/vmfusion/box/build.rb:9:in `build'
from /Users/tjmunn/veewee/lib/veewee/command/fusion.rb:23:in `build'
from /usr/local/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
from /usr/local/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
from /usr/local/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
from /usr/local/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/invocation.rb:115:in `invoke'
from /usr/local/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor.rb:235:in `block in subcommand'
from /usr/local/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
from /usr/local/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
from /usr/local/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
from /usr/local/lib/ruby/gems/2.1.0/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
from /Users/tjmunn/veewee/bin/veewee:24:in `<top (required)>'
from /usr/local/lib/ruby/gems/2.1.0/bin/veewee:23:in `load'
from /usr/local/lib/ruby/gems/2.1.0/bin/veewee:23:in `
On Tue, Dec 30, 2014 at 7:03 PM, Thomas Munn symgryph@gmail.com wrote:
Most of the files live in :
/Applications/"VMware Fusion.app"/Contents/Library/
These days.
On Mon, Dec 29, 2014 at 1:08 PM, Michal Papis notifications@github.com wrote:
looks like veewee was not bale to find one of this paths:
/Library/Application Support/VMware Fusion/vmrun /Applications/VMware Fusion.app/Contents/Library/vmrun /usr/local/bin/vmrun
in what path is your Fusion installed? can you find it with:
which vmrun
— Reply to this email directly or view it on GitHub https://github.com/jedi4ever/veewee/issues/1023#issuecomment-68281463.
Two Wheels Good, Four Wheels Bad
Two Wheels Good, Four Wheels Bad
sounds like a bug in fission
- I will investigate soon, but it's low on my priority list, please feel free to ping me in two weeks if there is no solution for it yet
Hi, same symptoms here. Had you any chance to look at the issue?
I never got it to work. Seems like 7.0 or 7.1 don't process correctly. I did do some sym linking but never got it to work.
Sent from my iPad
On Feb 12, 2015, at 22:54, kral2 notifications@github.com wrote:
Hi, same symptoms here. Had you any chance to look at the issue?
— Reply to this email directly or view it on GitHub.
Still doesn't work. No idea why.
Sent from my iPad
On Feb 12, 2015, at 22:54, kral2 notifications@github.com wrote:
Hi, same symptoms here. Had you any chance to look at the issue?
— Reply to this email directly or view it on GitHub.
Just noticed that I am getting the 'fission' error with the currentest. Should I try an earlier version like stable?
I do admit that packer seems to work fine with fusion. I guess I will just use that.
I think that this is problem about fission gem.
I have no idea how to fix. Is it a sep (somebody else's problem) field situation?
Sent from my iPad
On Apr 11, 2015, at 22:28, Naoya Nakazawa notifications@github.com wrote:
I think that this is problem about fission gem.
— Reply to this email directly or view it on GitHub.
@symgryph Hi, I fix a this problem. My PR is #1054.
Please try it, Thanks.
fixed with #1054 - please let me know if not
Just installed. Works great!
Sent from my iPad
On Apr 16, 2015, at 19:56, Michal Papis notifications@github.com wrote:
Closed #1023.
— Reply to this email directly or view it on GitHub.
It worked! Thanks!
Sent from my iPad
On Apr 12, 2015, at 02:51, Naoya Nakazawa notifications@github.com wrote:
@symgryph Hi, I fix a this problem. My PR is #1054.
Please try it, Thanks.
— Reply to this email directly or view it on GitHub.