Hello, I am more than happy to review and help you to get this working, and I can check the packer part if you are willing to share what you got.
Alvaro. On Sat, Mar 5, 2016 at 10:42 AM, <[email protected]> wrote: > Hello. I am having an issue that I am hoping to get assistance on, maybe > someone else has run into it, because googling for it has been hard. > > I have been using a CentOS 7 box, which I made with Packer, that regularly > has issues starting up. I am using a boilerplate Vagrantfile, with the only > meaningful addition being: > config.vm.network "private_network", ip: "172.18.7.6" > > Version: 1.7.4 > Provider: VirtualBox > Host: Suse Leap > Guest: CentOS 7 > > *Output:* > vagrant up > Please report a bug if this causes problems. > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'centos7'... > ==> default: Matching MAC address for NAT networking... > ==> default: Setting the name of the VM: centos7 > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 => 2222 (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> 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: > 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: Setting hostname... > ==> default: Configuring and enabling network interfaces... > The following SSH command responded with a non-zero exit status. > Vagrant assumes that this means the command failed! > > cat /sys/class/net/veth00d3838/address > > Stdout from the command: > > > > Stderr from the command: > > cat: /sys/class/net/veth00d3838/address: No such file or directory > > -- > 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/34c76054-6862-4d71-a809-3516e48af924%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/34c76054-6862-4d71-a809-3516e48af924%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/CAHqq0exOLLofK5CmbNTZTPSLPiuf29MX9ANdnFZ-qnyL7Z2R2Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
