Update: Jeremy Hanmer said that "it looks like it's a port lookup that's failing and taking cfprefsd with it."
He's gone over my head, but I'm sure that's meaningful to someone out there ;-) d On Fri, May 4, 2012 at 12:59 PM, Duncan McGreggor <dun...@dreamhost.com> wrote: > Updates: > > * Doug Hellmann narrowed this down to the network access that was > happening with pip > * Mark McClain further narrowed it down to VirtualBox's networking: > with a NATed interface, big probs -- with a bridged interface, things > go well. > > I haven't taken the time to check this on my own system, since I've > got a working solution right now, but when I need to rebuild, I will > check. > > Mark also mentioned that VBox networking sometimes does some weird > stuff (rewriting headers or something) and that might be contributing > to the problem. > > Hope this helps, > > d > > On Fri, May 4, 2012 at 12:40 PM, Duncan McGreggor <dun...@dreamhost.com> > wrote: >> Hey folks, >> >> We're really pressed for time right now, so there are certain rabbit >> holes we can't dive down, but I wanted to bring this up in case it >> hasn't been seen yet. >> >> On Mac OS X 10.6 and 10.7, when running a 12.04 Ubuntu VM and setting >> up the dev env for Keystone, we get some madness. >> 10.6: VirtualBox instance aborts, leaving no traces of issue in >> system logs (that I could see) >> 10.7: VB dies, OS X kernel panics >> >> The second time, I watched carefully, and it happened as >> python-memcached was getting installed via pip in the .venv. >> >> "So I built a third. That burned down, fell over, then sank into the swamp." >> >> But the fourth one stayed up after I removed .venv and changed >> tools/install_venv.py to enable system site-package use. >> >> d _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp