Hello, That is expected.
You need to have Virtualbox window closed. after the VM is provisioned, and you go to check the new VM will be there. You should't use that to get full screeen/gui access. You should use: vagrant ssh and that will connect you the VM. So at this stage I think Vagrant is working fine :) Alvaro On Thu, Dec 3, 2015 at 8:29 AM, Kiran Sharma <[email protected]> wrote: > C:\vagrant\vbox>vagrant --version > Vagrant 1.7.4 > > C:\vagrant\vbox>vagrant plugin list > vagrant-berkshelf (4.1.0) > vagrant-share (1.1.4, system) > > > ============ > > C:\vagrant>mkdir precise64 > > C:\vagrant>cd precise64 > > C:\vagrant\precise64>vagrant init -m hashicorp/precise64 > A `Vagrantfile` has been placed in this directory. You are now > ready to `vagrant up` your first virtual environment! Please read > the comments in the Vagrantfile as well as documentation on > `vagrantup.com` for more information on using Vagrant. > > C:\vagrant\precise64>vagrant up > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'hashicorp/precise64'... > ==> default: Matching MAC address for NAT networking... > ==> default: Checking if box 'hashicorp/precise64' is up to date... > ==> default: Setting the name of the VM: > precise64_default_1449083411011_2660 > ==> default: Fixed port collision for 22 => 2222. Now on port 2200. > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > ==> default: Forwarding ports... > default: 22 => 2200 (adapter 1) > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2200 > default: SSH username: vagrant > default: SSH auth method: private key > default: Warning: Connection timeout. Retrying... > default: > default: Vagrant insecure key detected. Vagrant will automatically > replace > default: this with a newly generated keypair for better security. > default: > default: Inserting generated public key within guest... > default: Removing insecure key from the guest if it's present... > default: Key inserted! Disconnecting and reconnecting using new SSH > key... > ==> default: Machine booted and ready! > ==> default: Checking for guest additions in VM... > default: The guest additions on this VM do not match the installed > version o > f > default: VirtualBox! In most cases this is fine, but in rare cases it > can > default: prevent things such as shared folders from working properly. > If you > see > default: shared folder errors, please make sure the guest additions > within t > he > default: virtual machine match the version of VirtualBox you have > installed > on > default: your host and reload your VM. > default: > default: Guest Additions Version: 4.2.0 > default: VirtualBox Version: 5.0 > ==> default: Mounting shared folders... > default: /vagrant => C:/vagrant/precise64 > ==================== > > The box is created successfully but it does not appear in the console. But > when I visited the vm directory and click on the box file, i appears on the > console. you can see that in the attached doc. > > > I created two vms yesterday in this way which you can see in the attached > doc. But this is not a problem free. It appears on the console but it fails > to start, I repeated a few time before getting it worked. Also, if I > changed the network from net to bridge, it does not boot. > > That is what exactly happened with prevision 64, the vm I just created > following your steps. > > Thanks > Kiran > > > > . > > > > On Wednesday, December 2, 2015 at 5:48:09 AM UTC-5, Alvaro Miranda > Aguilera wrote: >> >> 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) 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. 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/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. >> >> >> -- > 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/41016650-fff8-4ea1-bd77-e6322c41bcb7%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/41016650-fff8-4ea1-bd77-e6322c41bcb7%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit 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/CAHqq0exVFhED0YEh3-4zFutaMf677GRRgGNyN8bza-KO54k5WA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
