Hello,

Facing one problem, where the IP of ovsbr0 (which is associated with eth0)
becomes unreachable when we add a port in ovsbr0. This is happening in KVM
server having default openvswitch from ubuntu package + libvirt 0.9.13.

Objective - Is to prepare a KVM server and boots up with a network having
single physical nic "eth0" which will be associated with "ovsbr0". This is
similar like Xenserver 6.0 default network. I want to add all VM vif on
this bridge so that VM gets IP from DHCP server.

Here are the steps followed to reproduce it. Problem is found in point 4
below.:

1. Configured initial KVM by following below link.
http://blog.allanglesit.com/2012/03/linux-kvm-ubuntu-12-04-with-openvswitch
/

2. The only difference is with /etc/network/interfaces where ovsbr0 is
trying to get IP from dhcp. In addition libvirt 0.9.13 is installed.

   It look like as below:

root@kvmserver:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual
up ifconfig $IFACE 0.0.0.0 up
down ifconfig $IFACE down

auto ovsbr0
iface ovsbr0 inet dhcp
    hwaddress ether fa:16:3e:66:10:02



root@kvmserver:~# ifconfig
eth0      Link encap:Ethernet  HWaddr fa:16:3e:66:10:02
          inet6 addr: fe80::f816:3eff:fe66:1002/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2798 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1193 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:200242 (200.2 KB)  TX bytes:139438 (139.4 KB)
          Interrupt:10

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:559 errors:0 dropped:0 overruns:0 frame:0
          TX packets:559 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:45648 (45.6 KB)  TX bytes:45648 (45.6 KB)

ovsbr0    Link encap:Ethernet  HWaddr fa:16:3e:66:10:02
          inet addr:XX.XX.XX.XXX Bcast:10.34.102.255  Mask:255.255.255.0
          inet6 addr: fe80::f816:3eff:fe66:1002/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1718 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1166 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:167278 (167.2 KB)  TX bytes:137368 (137.3 KB)


3. root@kvmserver:~# /etc/init.d/openvswitch-switch status
ovsdb-server is running with pid 1194
ovs-vswitchd is running with pid 1206
ovs-brcompatd is running with pid 1262

4. Now, if we start a VM which tries to add a port to ovsbr0 then the IP
of ovsbr0 is unreachable.

   Here is what is added in vm xml file:
    <interface type='bridge'>
      <mac address='52:54:00:0f:b4:7a'/>
      <source bridge='ovsbr0'/>
      <virtualport type='openvswitch'/>
      <model type='virtio'/>
     </interface>

To diagnose further, i just tried to add a port as below. p1 gets added
but the IP of ovsbr0 is unreachable now. But if i restart network using
'/etc/init.d/networking restart' then this comes normal till we add any
further port.

root@kvmserver:~# ovs-vsctl add-port ovsbr0 p1
<<<<< after this command IP of ovsbr0 not reachable. >>>>>

Any idea ?

- Arun

    


_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to