Hello Kiran, If we start fresh, the user experience should be nice. Windows have some issues some times.
vagrant version vagrant plugin list Current version is 1.7.4 And the only plugin installed by default is vagrant-share from there, as your normal user you can do mkdir precise64 cd precise64 vagrant init -m hashicorp/precise64 vagrant up the -m is for a minimal Vagranfile. IF you get issues with that simple setup, Can I have the following please: set VAGRANT_LOG=debug vagrant up and share a gist (gist.github.com <http://gist.github.com/>) of the log generated? and a description on what’s failing. Since I get the idea what was failing is fixed. Thanks Alvaro. > On 2/12/2015, at 1:41 PM, Kiran Sharma <[email protected]> wrote: > > I am not sure about prevision64 box, but other two boxes I used, both have > guest addition installed. > > CentOS 7 x64 (Minimal, Shrinked, Guest Additions 4.3.26) (Monthly updates) > VirtualBox > Copy > https://github.com/holms/vagrant-centos7-box/releases/download/7.1.1503.001/CentOS-7.1.1503-x86_64-netboot.box > 437 > CentOS 7.1 x64 (Minimal, Puppet 4.2.3, Guest Additions 4.3.30)[notes > <https://github.com/CommanderK5/packer-centos-template>] > VirtualBox > Copy > https://github.com/CommanderK5/packer-centos-template/releases/download/0.7.1/vagrant-centos-7.1.box > 576 > > Also, I have VBoxGuestAdditions.iso in my virtualbox directory. > > ------------------- > C:\vagrant\vbox>dir "\Program Files\Oracle\VirtualBox"\*.iso > Volume in drive C is OSDisk > Volume Serial Number is 1E1D-0BBC > > Directory of C:\Program Files\Oracle\VirtualBox > 11/10/2015 06:02 PM 59,002,880 VBoxGuestAdditions.iso > 1 File(s) 59,002,880 bytes > 0 Dir(s) 340,745,592,832 bytes free > > > Also, I used these boxes previously and had no issues at all. > > As you saw, I now even have issue with prevision64 box. > > > To answer the questions you raised > > 1. The vm in fact comes up, in some occasions. in occasionally, it also > appears on vbox gui/console. So, I can not use it. > > 2. I have not deleted NAT interface. The box I used has default NAT and I am > not trying to delete it. In fact, now, I am trying to bring the vm only with > simple configure > (a) vagrant init <box>; > (b) vagrant up > > This seems the only line which is not commented in my current vagrant file > > config.vm.box = "hashicorp/precise64" > > Please let me know if you need further info. I am so annoyed with it and want > to resolved the issue. I am happy to provide any info you needed. > > > Thanks > Kiran > > > On Saturday, November 7, 2015 at 10:17:44 AM UTC-5, kiran sharma wrote: > I was able to use various features of vagrant to provision a virtualbox but I > was unable to add Vbox GuestAdditions. It fails with the following error. > > what I did? > > I downloaded plugins necessary for guestaddition --vagrant plugin install > vagrant-vbguest > > Based on what I read, we do not need to put anything on vagrantfile for > installing Vbox GuestAdditions it does automatically. So I used same > vagrantfile. > > Fom the log I can see, it tries to install Vbox GuestAdditions but it failed > > > > 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 > [i][b]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: > > /sbin/mount.vboxsf: mounting failed with the error: No such device > > > > I also found some suggestion on the net e.g > sudo ln -s /opt/VBoxGuestAdditions-4.3.10/lib/VBoxGuestAdditions > /usr/lib/VBoxGuestAdditions > > but this did not fix my issue. Appreciate any suggestion. > > > -- > This mailing list is governed under the HashiCorp Community Guidelines - > https://www.hashicorp.com/community-guidelines.html > <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 > <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 [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vagrant-up/6eae14c7-e01d-42f2-91f6-ae7824496481%40googlegroups.com > > <https://groups.google.com/d/msgid/vagrant-up/6eae14c7-e01d-42f2-91f6-ae7824496481%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/43883229-8E5A-493D-B437-536AA8E0F7F1%40gmail.com. For more options, visit https://groups.google.com/d/optout.
