Hey Allison, long time no see. :) > Stefan, what's the most important thing we could do to help you help us? > I see a few threads of inquiry in the comments that trailed off:
I would say either find a way to reproduce without OpenStack or manage to get some crashdumps. The crashdumps might be simpler to prepare for and with luck we catch the issue happening on those hosts set up to crashdump. While that can be done without too much thought, being able to reproduce it locally with a minimal dependencies would allow us quicker iterations when trying fixes. also, Chris and I managed to approach the devstack setup in two different ways and maybe both of us made little mistakes there (His being more successful as I thought it to be a good idea to use a Xen guest but have not thought of whether openstack supports nested with Xen). > - abstracting Salvatore's script for high thrash rates on VM > creation/destruction and network namespace creation, to try reproducing > the issue without running openstack > - capturing crashdumps from a devstack gate run (or simulated gate run > on a local machine) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273386 Title: Neutron namespace metadata proxy triggers kernel crash on Ubuntu 12.04/3.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1273386/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
