Flavio,
Appreciate the suggestion. If it was not clear, I was attempting
packstack install originally. It configures and the OpenStack networking
related bridge interfaces. This problem first show up when
packstack/puppet tries to bring up those bridge interfaces and it keeps
happening every
On Mon, Sep 8, 2014 at 1:38 AM, S. Han wrote:
> Hi, guys.
> My name is S. Han. I am a user of OVS in XenServer.
>
>
> I would like to confirm that the following problem is solved in the latest
> OVS version (2.3.0).
>
>
> I tried running OVS 2.1.2 in XenServer 6.2. After the installation, the
> Xe
On Mon, Sep 08, 2014 at 09:34:03AM -0700, Gurucharan Shetty wrote:
> I saw something similar today. In my case, 'force-reload-kmod' would
> trigger the udev event loop. Adding HOTPLUG=no in
> /etc/sysconfig/network-scripts/ifcfg-* solved the problem for me. I do
> not know the exact sequence of eve
On Fri, Sep 05, 2014 at 01:55:08PM +0800, ychen wrote:
> Then there is another question, how can I delete a port with its name? As you
> see, in the above command, I must use the "uuid" to delete port from bridge
> table. Is there a simple way to use "select" and "mutate" to delete port with
> n
On Fri, Sep 05, 2014 at 02:17:57PM -0400, Krishna Pratap wrote:
> Could it be the case that the switch expects a controller connection to be
> present and that it waits for such a connection for a specific amount of
> time.
> If it does not get hold of an active connection, it may be going to the
>
I saw something similar today. In my case, 'force-reload-kmod' would
trigger the udev event loop. Adding HOTPLUG=no in
/etc/sysconfig/network-scripts/ifcfg-* solved the problem for me. I do
not know the exact sequence of events that makes udev act that way.
Here is one bug report where the end res
Hi, guys.
My name is S. Han. I am a user of OVS in XenServer.
I would like to confirm that the following problem is solved in the latest
OVS version (2.3.0).
I tried running OVS 2.1.2 in XenServer 6.2. After the installation, the
XenServer hosts frequently crash due to kernel panic. XenServer c
