Vagrant doesn't start

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Vagrant doesn't start

Саша Ковтуненко
vagrant up 

INFO subprocess: Starting process: ["/etc/init.d/vmware", "status"]
 INFO vmware_driver: Checking status of VMware network services...
 INFO subprocess: Starting process: ["/usr/bin/vmware-networks", "--status"]
 WARN vmware_driver: vmnet devices are NOT healthy. Attempting to fix.
 INFO vmware_driver: Stopping vmnet-* devices
 INFO subprocess: Starting process: ["/usr/bin/vmware-networks", "--stop"]
 INFO vmware_driver: Reconfiguring vmnet-* devices
 INFO subprocess: Starting process: ["/usr/bin/vmware-networks", "--configure"]
 INFO vmware_driver: Checking overall vmware service status...
 INFO subprocess: Starting process: ["/etc/init.d/vmware", "status"]
 INFO vmware_driver: Checking status of VMware network services...
 INFO subprocess: Starting process: ["/usr/bin/vmware-networks", "--status"]
The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.

Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.

Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.
 INFO global: Vagrant version: 1.2.4

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Vagrant doesn't start

Mitchell Hashimoto
More correctly: VMware doesn't start.

The most common reason for this is collisions with existing network
services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.

Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.

On Fri, Jul 26, 2013 at 8:03 AM, Саша Ковтуненко
<[hidden email]> wrote:

> vagrant up
>
> INFO subprocess: Starting process: ["/etc/init.d/vmware", "status"]
>  INFO vmware_driver: Checking status of VMware network services...
>  INFO subprocess: Starting process: ["/usr/bin/vmware-networks", "--status"]
>  WARN vmware_driver: vmnet devices are NOT healthy. Attempting to fix.
>  INFO vmware_driver: Stopping vmnet-* devices
>  INFO subprocess: Starting process: ["/usr/bin/vmware-networks", "--stop"]
>  INFO vmware_driver: Reconfiguring vmnet-* devices
>  INFO subprocess: Starting process: ["/usr/bin/vmware-networks",
> "--configure"]
>  INFO vmware_driver: Checking overall vmware service status...
>  INFO subprocess: Starting process: ["/etc/init.d/vmware", "status"]
>  INFO vmware_driver: Checking status of VMware network services...
>  INFO subprocess: Starting process: ["/usr/bin/vmware-networks", "--status"]
> The VMware "vmnet" devices are failing to start. The most common
> reason for this is collisions with existing network services. For
> example, if a hostonly network space collides with another hostonly
> network (such as with VirtualBox), it will fail to start. Likewise,
> if forwarded ports collide with other listening ports, it will
> fail to start.
>
> Vagrant does its best to fix these issues, but in some cases it
> cannot determine the root cause of these failures.
>
> Please verify you have no other colliding network services running.
> As a last resort, restarting your computer often fixes this issue.
>  INFO global: Vagrant version: 1.2.4
>
> --
> 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 [hidden email].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.