Good morning,

Yesterday I wanted to build a new 'ubuntu/trusty64' VirtualBox image using 
Vagrant.

The versions of the software I am running are:

Host Machine:   Ubuntu 14.04.2 LTS 64 bit
VirtualBox:  4.3.28
Vagrant:  1.7.2

The Vagrantfile contains the following:

Vagrant.configure(2) do |config|
  config.vm.box = "ubuntu/trusty64"
  config.vm.network "public_network"
  config.vm.hostname = "chef"
end


As you can see if it is very simple Vagrantfile, but with the network being 
set as 'public'.  When the 'vagrant up' asks for the network card to bridge 
I am selecting 'eth0'.

This is where it all goes wrong.  At the point the system states that 
'Booting VM' the host locks up and hangs.  It is not possible to 
communicate with it over the network or directly on the console as the 
keyboard and mouse do not work.  The only way out of this is to reboot the 
machine.

The VirtualBox machine will start if the network is set to private but as I 
want to be able to access it from any machine on my network I need the 
public set.

Has anyone seen this behaviour at all?  As the machine just hangs I am not 
able to get any diagnostic information and there is nothing obvious in the 
syslog.  The only strange entry I see is as follows with the ^@ which 
appear in the syslog on a forced reboot:

 10218 Jul  9 16:51:14 monkey kernel: [   54.479634] init: logstash-web 
main process ended, respawning
  10219 
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
 
       
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
 
       
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
 
       
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
 
       ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Jul  9 16:54:53 monkey rsyslogd: [origin 
software="rsyslogd" swVersion="7.4.4" x-pid="951" x-info=
"http://www.rsyslog.com";] start
  10220 Jul  9 16:54:53 monkey rsyslogd: rsyslogd's groupid changed to 103
  10221 Jul  9 16:54:53 monkey rsyslogd: rsyslogd's userid changed to 101
  10222 Jul  9 16:54:53 monkey kernel: [    0.000000] Initializing cgroup 
subsys cpuset


The hardware specifications of the machine are:

Intel(R) Core(TM) i5-3470S CPU @ 2.90GHz
16Gb RAM

Thanks in advance for any advice.

Russell

-- 
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/3897a3b5-7cfd-406b-8484-8640e9315f21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to