==> default: which network to bridge to.
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: bridged
==> default: Forwarding ports...
default: 22 => 2200 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.
If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.
The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.
As I said, the problem is not resolved. I can not create another adapter,
nor I can changed the NAT to bridge. In summary
1. creation of machine works sometime, but not always
2. the machine does not appear into virtualbox console automatically, so I
can ssh but can not stop or start
3. I can make the box appear on console by non standard way( which read
somewhere else)
4. No network change by any way, even changing the vagrantfile and
reloading it
If there is anything I can provide you, it would be happy in regards to
resolve this issue.
Thanks a lot
Kiran
On Thursday, December 3, 2015 at 3:24:39 AM UTC-5, Alvaro Miranda Aguilera
wrote:
>
> How are you doing these changes?
>
> The way of doing with Vagrant is update the Vagrantfile and then do a
> vagrant reload.
>
> Alvaro.
>
>
> On 3/12/2015, at 6:05 PM, Kiran Sharma <[email protected] <javascript:>>
> wrote:
>
> Do you mean not showing in the virtualbox console is fine? Also, I can not
> change the network adapter to bridge or add in addition to the nat which is
> created while propositioning the machine.
>
> Based on what I used to do, it is not resolved. I can only create machine
> with nat adapter nothing else. when I changed network adapter to bridge,
> and restart the interface, I got this
>
> e1000 0000:01:03.0: eth0: Detected Tx Unit Hang
> Tx Queue <0>
> TDH <bd>
> TDT <bd>
> next_to_use <bd>
> next_to_clean <73>
>
>
>
>
--
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/24c1b4a6-b383-4c73-a267-79aff4136458%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
