!
On Thu, Jan 23, 2014 at 11:13 AM, Travis Wilson
wrote:
> Okay, good news. I was able to get my br-tun interfaces back online and
> can confirm that we are still not crashing. I still can't get my instances
> to get IPs yet, but working to get that fixed next. Thank you.
>
&
Okay, good news. I was able to get my br-tun interfaces back online and can
confirm that we are still not crashing. I still can't get my instances to
get IPs yet, but working to get that fixed next. Thank you.
On Thu, Jan 23, 2014 at 9:27 AM, Travis Wilson wrote:
> Okay, I may have sp
wrote:
> Hmm, that's interesting. I'm glad that 1.9.3 fixed the problem
> although I didn't see any changes from 1.9 that I would expect to
> resolve this. However, 2.0 has a much simpler tunneling stack so I
> would expect that to be more reliable.
>
> On Wed,
ch simpler tunneling stack so I
> would expect that to be more reliable.
>
> On Wed, Jan 22, 2014 at 11:25 AM, Travis Wilson
> wrote:
> > Good day again Jesse.
> >
> > I wanted to provide you and the group with an update on our issue. We
> tried
> > s
the
> problem based on the instruction pointer, that would be very helpful. I
> agree that it seems unlikely that this is memory corruption.
>
> On Fri, Jan 17, 2014 at 5:51 AM, Travis Wilson
> wrote:
>
>> Good day.
>>
>> So I am working with one of our internal L
Good day.
We are new to OpenStack and Open vSwitch and have run into an issue
where when deploying a VM instance either our Compute Node or Network
Node consistently kernel panic. From what we can see on the screen
when the panics occur it appears that Open vSwitch components may be
involved but w
