Yup something silly, always. Thanks for spotting that. All works so now off to build a service broker.

Yeah. Everything says “No Changes” which is expected since I just stood this all up today so it should be current. -kris

curl doesn’t appear to be in there. Here’s the route table and a wget which is the same connection refused. vagrant(a)bosh-lite:~$ !wget wget https://api.10.244.0.134.xip.io/v2/info --2015-08-25 18:28

It shows all good. I can ssh into the api machine with no problems. └─>bosh vms Acting as user 'admin' on 'Bosh Lite Director' Deployment `cf-warden' Director task 18 Task 18 done +-------------------

Seems a combination of the 215 release and the patches Vbox let’s me finally have a setup running more than ~10 minutes. So I have a clean install from this morning. Now I get a connection refused └─>

So… The E1000 emulation in vbox is being overloaded because the internal traffic for 10.244.x.x. is being routed out to the host which has to go back into the vm. From the vbox team: Now the question

Fyi for everyone. Looks like this box bug and the team is working on it with debug vbox builds. https://forums.virtualbox.org/viewtopic.php?f=2&t=67437 -kris

First I really like that 2 years means old you should tell some of my customers that ! I work at oracle so have an in with the vbox team :) They are looking at it for me now.

Thanks appears to not make a difference. I did drop the team a note so hopefully will get an answer back shortly. -kris

It is indeed the virtualbox ethernet going bad or something https://dl.dropboxusercontent.com/u/12188201/Screen%20Shot%202015-07-08%20at%2017.03.46.png <https://dl.dropboxusercontent.com/u/12188201/Sc

Here’s what just happened now testing it again. Note the times are a little longer this time so it’s not a hard 15 minutes. ┌─[13:07:09]─[klrice]─[denab214]:/scratch/klrice/workspace/bosh-lite$ └─>bos

Yup. I saw that note somewhere and did it before even starting at all. -kris

Nope vbox shows the vm still running just no longer accessible. So I do a vagrant halt / up which brings it back up and the only one from running bosh vms that is ever running is the postgres one. Thi

Right. I've done that and 15 minutes later same exact thing again -kris

I’m sure it’s something os/vbox but on two machines repeating nothing but the steps in the doc I get the same results. Here’s another example of what’s right now. I stop/start vagrant/vbox and then is

All, I’ve run the install several times now on both OEL 6.4 and Fedora 20 with virtualbox 4.3.28 w/extras ( current ) They have all very consistently stopped being able to access the network at about