[chef] Re: test-kitchen VM naming problems

[Alfredo Palhares < >]

So the problem was that vagrant is ignoring system wide gems.

I also noticed that vagrant gem would install to $HOME/.gems instead
of $HOME/.vagrant.d/gems

The workaround I did was symlink'ing $HOME/.vagrant.d/gems to 
/usr/lib/ruby/gems/1.9.1/gems

I opened a ticket[1] on kitchen since I was told on #vagrant (freenode) that 
system wide gems are
ignored by design, but please tell me if opening a bug for knife is silly 
(probably is)

[1]http://tickets.opscode.com/browse/KITCHEN-43