Hi Alvaro,

This is my full set of thing’s I worked.

I created one vagrant with ansible installed. I would like to use this for 
creating 2 more similar instances. 

For that the after created first one, and for the second one, I created


Rameshs-MacBook-Pro:vag_cent7_1 Ramesh$ vagrant package
==> default: Attempting graceful shutdown of VM...
==> default: Clearing any previously set forwarded ports...
==> default: Exporting VM...
==> default: Compressing package to: 
/Users/Ramesh/lab_ansible/vag_cent7_1/package.box

After that I created the new vagrant box


 vagrant box add --name server2 
/Users/Ramesh/lab_ansible/vag_cent7_1/package.box --provider virtualbox

Rameshs-MacBook-Pro:boxes Ramesh$ mv server2 ansible_lab 

Now I can connect without ssh password asking, but getting the shared file 
directory error.


Rameshs-MacBook-Pro:vag_cent7_2 Ramesh$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ansible_lab'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: vag_cent7_2_default_1473912787464_34053
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: No guest additions were detected on the base box for this VM! Guest
    default: additions are required for forwarded ports, shared folders, host 
only
    default: networking, and more. If SSH fails on this machine, please install
    default: the guest additions and repackage the box to continue.
    default:
    default: This is not an error message; everything may continue to work 
properly,
    default: in which case you may ignore this message.
==> default: Setting hostname...
==> default: Mounting shared folders...
    default: /vagrant => /Users/Ramesh/lab_ansible/vag_cent7_2

^R
Failed to mount folders in Linux guest. This is usually because
the "vboxsf" file system is not available. Please verify that
the guest additions are properly installed in the guest and
can work properly. The command attempted was:

mount -t vboxsf -o uid=`id -u vagrant`,gid=`getent group vagrant | cut -d: -f3` 
vagrant /vagrant
mount -t vboxsf -o uid=`id -u vagrant`,gid=`id -g vagrant` vagrant /vagrant

The error output from the last command was:

mount: unknown filesystem type 'vboxsf'

​
Help me on fixing this, as Im new to this one.

On Wednesday, 14 September 2016 12:40:44 UTC+5:30, Alvaro Miranda Aguilera 
wrote:
>
> hello
>
> you need:
>
> - a known private/pub key, not just any key.
> - The ssh is from the host to the guest, so adding a new pair 
> guest-to-guest wont help.
> - permissions need to be for all the content 0600 and folder 0700
>
> If you could run my provided script and test `vagrant ssh` it will show 
> more information.
>
> On Wed, Sep 14, 2016 at 4:34 AM, STARFISH <rame...@gmail.com <javascript:>
> > wrote:
>
>>
>> I tried the same by generating the new ssh key, and then redirect to the 
>> authorized keys, still the same error.
>>
>> ssh-keygen -t rsa -b 4096 -C "Vagrant"
>> cat vagrant.pub > ~/.ssh/authorized_keys
>> chmod 600 ~/.ssh/authorized_keys
>>
>> -- Already its owned by vagrant, so skipped this step.
>>
>> After vagrant reload, got the same error
>>
>> vagrant reload
>> ==> default: Clearing any previously set forwarded ports...
>> ==> default: Clearing any previously set network interfaces...
>> ==> default: Preparing network interfaces based on configuration...
>>     default: Adapter 1: nat
>> ==> default: Forwarding ports...
>>     default: 22 (guest) => 2222 (host) (adapter 1)
>> ==> default: Booting VM...
>> ==> default: Waiting for machine to boot. This may take a few minutes...
>>     default: SSH address: 127.0.0.1:2222
>>     default: SSH username: vagrant
>>     default: SSH auth method: private key
>>     default: Warning: Remote connection disconnect. Retrying...
>>     default: Warning: Authentication failure. Retrying...
>> ^C==> default: Waiting for cleanup before exiting...
>> Vagrant exited after cleanup due to external interrupt.
>>
>>
>> On Tuesday, 13 September 2016 23:44:40 UTC+5:30, STARFISH wrote:
>>>
>>> Hi Here,
>>>
>>> I created one vagrant file and from that I used to create the package 
>>> box. 
>>>
>>> With the help of the package box, while I try to start the another vm, 
>>> its having the below warning, its not starting.. I Have no idea how to fix 
>>> this.
>>>
>>> default: SSH username: vagrant
>>>     default: SSH auth method: private key
>>>     default: Warning: Remote connection disconnect. Retrying...
>>>     default: Warning: Authentication failure. Retrying...
>>>     default: Warning: Authentication failure. Retrying...
>>>     default: Warning: Authentication failure. Retrying...
>>>     default: Warning: Authentication failure. Retrying...
>>>     default: Warning: Authentication failure. Retrying...
>>>     default: Warning: Authentication failure. Retrying...
>>>
>>> Its started, but not connected and the vagrant ssh is not working
>>>
>>>
>>> Rameshs-MacBook-Pro:vag_cent7_2 Ramesh$ vagrant ssh
>>> Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
>>>
>>> Below is my vagrant file.
>>>
>>> Rameshs-MacBook-Pro:vag_cent7_2 Ramesh$ cat Vagrantfile
>>>
>>> Vagrant.configure(2) do |config|
>>>
>>>   config.vm.box = "/Users/Ramesh/lab_ansible/vag_cent7_1/package.box"
>>>   config.vm.hostname = "server2"
>>>
>>> end
>>>
>>> Help me on fixing this.
>>> ​
>>>
>> -- 
>> This mailing list is governed under the HashiCorp Community Guidelines - 
>> https://www.hashicorp.com/community-guidelines.html. Behavior in 
>> violation of those guidelines may result in your removal from this mailing 
>> list.
>>  
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Vagrant" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to vagrant-up+...@googlegroups.com <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/vagrant-up/c90c0328-7c23-4f04-9e53-205e89fe8ba5%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/vagrant-up/c90c0328-7c23-4f04-9e53-205e89fe8ba5%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Alvaro
> (+31)103400555
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/0776bec5-a632-4766-91e8-43ac23623bb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to