On Jul 9, 2015, at 09:54, Armin Ranjbar <zoup(a)zoup.org> wrote:

hahaha :))
i think it's kernel realted, so you might want to tip them about that.


---
Armin ranjbar

On Thu, Jul 9, 2015 at 5:56 PM, kris rice <kris.rice(a)jokr.net> wrote:
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.

On Jul 9, 2015, at 02:55, Armin Ranjbar <zoup(a)zoup.org> wrote:

hmm, it's a known (but old) bug, can you try to change NIC type?
also try this on the VM:
add pcie_aspm=off to cmdline, this is supposed to disable power management features of PCI-Express components, if that didn't helped try to disable NIC TSO:
ethtool -K ethX tso off

i have also noticed that you are using OEL 6.4 and fedora20, both are pretty old (2013 i guess), can you try using a more recent (ubuntu14 lts for example) distro?


---
Armin ranjbar

On Thu, Jul 9, 2015 at 2:06 AM, kris rice <kris.rice(a)jokr.net> wrote:
Thanks appears to not make a difference. I did drop the team a note so hopefully will get an answer back shortly.
-kris

On Jul 8, 2015, at 17:25, Sabha Parameswaran <sabhap(a)pivotal.io> wrote:

can you try this:
VBoxManage modifyvm "VM name" --natdnshostresolver1 on

from: https://www.virtualbox.org/ticket/12441

On Wed, Jul 8, 2015 at 2:13 PM, kris rice <kris.rice(a)jokr.net> wrote:
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

I’ll drop the vbox team a note. Thanks the v.gui helped a ton to see this.

-kris

On Jul 8, 2015, at 16:43, Sabha <sabhap(a)pivotal.io> wrote:

So, ping to 10.244.xxx fails but ping to the 192.168.50.4 also fails?

What happens if you disconnect from external network (to avoid the
10.244...) or delete the cf deployment from bosh-lite (dont delete the
release, let it stay, just the deployment using bosh delete deployment
cf-warden and then you can redeploy again) and see if the 10.244.x is the
cause for the problem.

Also, you can probably enable vbox gui option to see if any errors are being
reported.
config.vm.provider "virtualbox" do |v|
v.gui = true
end

-Sabha



--
View this message in context: http://cf-bosh.70367.x6.nabble.com/cf-bosh-bosh-lite-cf-fails-in-15-minutes-tp412p425.html
Sent from the CF BOSH mailing list archive at Nabble.com.
_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh