|
From: | Sven Vogel |
Subject: | [Qemu-stable] CentOS | OpenvSwitch problem with local bridge |
Date: | Fri, 12 Apr 2019 11:56:20 +0000 |
Hi Devs,
We use RHEL/CentOS and since QEMU Version 2.12.0 we have problems with OpenvSwitch and a local bridge.
New Version:
-----------------
OS version: 7.6.1810
kernel version: 3.10.0-957.5.1.el7.x86_64
qemu version: 2.12.0
libvirtd version: 5.0.0
openvswitch version: 2.10.1
openvswitch db version: 7.16.1
Old Version:
----------------
OS version:
7.6.1810
kernel version:
3.10.0-957.5.1.el7.x86_64
qemu version:
2.10.0-21.el7_5.7.1
libvirtd version:
5.0.0
openvswitch version:
2.10.1
openvswitch db version:
7.16.1
We use Cloudstack and the virtual router will create a vnet for internal communication on a local bridge named cloud0. They use apipa addresses.
E.g. host address on the local cloud0 bridge are 169.254.0.1 and the virtual router try to create a vnet 169.254.0.251 for communication.
2019-04-09 14:28:29,979 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null) (logid:ed7c5d2a) Executing while with timeout : 5000
2019-04-09 14:28:30,007 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null) (logid:ed7c5d2a) Execution is successful.
2019-04-09 14:28:30,007 DEBUG [resource.virtualnetwork.VirtualRoutingResource] (agentRequest-Handler-1:null) (logid:ed7c5d2a) Trying to connect to 169.254.0.251
2019-04-09 14:28:33,013 DEBUG [resource.virtualnetwork.VirtualRoutingResource] (agentRequest-Handler-1:null) (logid:ed7c5d2a) Could not connect to 169.254.0.251
2019-04-09 14:28:38,013 DEBUG [resource.virtualnetwork.VirtualRoutingResource] (agentRequest-Handler-1:null) (logid:ed7c5d2a) Trying to connect to 169.254.0.251
2019-04-09 14:28:41,020 DEBUG [resource.virtualnetwork.VirtualRoutingResource] (agentRequest-Handler-1:null) (logid:ed7c5d2a) Could not connect to 169.254.0.251
It seems the interface will not come up if we use emu 2.12.0. if we use the older version 2.10.0 we don’t have the problem.
Is there any change in the new version? I hope there is someone who can say there is a workaround…
thanks
Sven
__ EWERK-Blog | LinkedIn | Xing |
Twitter |
Facebook |
[Prev in Thread] | Current Thread | [Next in Thread] |