Hi, Did anyone successfully "vagrant up" bento/centos-6.7-i386 on Windows server enterprise without hyper-v system ( service pack 2)? Any help will be very appreciated!
Thanks, On Friday, April 22, 2016 at 5:25:01 PM UTC-4, Irene wrote: > Thanks very much for your help! > > Yes, I booted the machine after installed vagrant. I tried to run vagrant > up as a normal user or Administrator. Both are failed for Centos 6.7 from > Windows console. > > vagrant version: > Installed Version: 1.8.1 > > Latest Version: 1.8.1 > > > vagrant plugin list: > > vagrant-share (1.1.5, system) > > vagrant-vbguest (0.11.0) > > > > Following the steps you provided, run vagrant up under the precise32. It > seemed work. I saved the last lines from the screen in the attached file > "precise32_screen.log", and some output redirect to "precise32.log". > > > But run vagrant up for "bento/centos-6.7-i386", it failed. I also saved > last lines of the screen in the attached file "centos67-screen.log", and > some output redirect to "centos67.log". I also attached the "VagrantFile" > for Centos6.7. > > I have no idea why Centos 6.7 VM boot failed. > > Thanks, > Irene > > > On Monday, April 18, 2016 at 4:39:27 PM UTC-4, Alvaro Miranda Aguilera > wrote: > >> >> On Tue, Apr 19, 2016 at 3:21 AM, Irene <[email protected]> wrote: >> >>> C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/socket.rb:60:in >>> `connect_nonblock': Invalid argument - connect(2) for 127.0.0.1:2222 >>> (Errno::EINVAL) >>> >> >> Hello, >> >> Haven't seen that error before, so lets dig on the usual suspects. >> >> 1. You are in the current version of Vagrant. 1.8.x >> 2. You did reboot after the install. >> 3. You are running this as your normal user. >> >> >> Can you provide the following output. >> >> vagrant version >> vagrant plugin list >> >> mkdir precise32 >> cd precise32 >> vagrant init -m hashicorp/precise32 >> set VAGRANT_LOG=debug >> vagrant up >> >> >> Thanks! >> alvaro. >> > -- 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/7ba5c008-a98e-452f-9fa9-f06d89084e5d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
