[ovs-discuss] OpenvSwitch - Issue Support Required
Jesse Gross
jesse at nicira.com
Tue Jun 4 01:36:13 UTC 2013
On Mon, Jun 3, 2013 at 4:03 AM, Moovarkku Mudhalvan
<moovarkku.mudhalvan at sifycorp.com> wrote:
> Dear OpenvSwitch Team,
>
>
>
>
>
> Greetings. I have installed CentOS 6.4 in the Blade server.
> Also installed and configured openvswitch
>
>
>
> 1. Confirmed openvswitch is installed and configured
>
>
>
> [root at clab-kvm02 ~]# lsmod |grep openvswitch
>
> openvswitch 37890 0
>
> [root at clab-kvm02 ~]# ovs-vsctl -V
>
> ovs-vsctl (Open vSwitch) 1.9.0
>
> Compiled Jun 2 2013 14:14:18
>
> [root at clab-kvm02 ~]#
>
>
>
> 2. Confirmed Switch , Interface and Port
>
>
>
> [root at clab-kvm02 network-scripts]# cat ifcfg-eth0
>
> DEVICE=eth0
>
> BOOTPROTO=none
>
> NM_CONTROLLED=no
>
> TYPE=OVSPort
>
> ONBOOT=yes
>
> IPV6INIT=no
>
> HWADDR=00:21:5A:9B:00:00
>
> DEVICETYPE=ovs
>
> OVS_BRIDGE=ovsbr0
>
>
>
> [root at clab-kvm02 network-scripts]# cat ifcfg-ovsbr0
>
> DEVICE=ovsbr0
>
> ONBOOT=yes
>
> DEVICETYPE=ovs
>
> TYPE=OVSBridge
>
> BOOTPROTO=static
>
> IPADDR=172.16.5.12
>
> GATEWAY=172.16.5.1
>
> NETMASK=255.255.255.0
>
> DNS1=172.16.5.13
>
> HOTPLUG=no
>
> [root at clab-kvm02 network-scripts]#
>
>
>
>
>
> [root at clab-kvm02 ~]# route -n
>
> Kernel IP routing table
>
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
>
> 172.16.5.0 0.0.0.0 255.255.255.0 U 0 0 0
> ovsbr0
>
> 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0
> virbr0
>
> 0.0.0.0 172.16.5.1 0.0.0.0 UG 0 0 0
> ovsbr0
>
>
>
> [root at clab-kvm02 ~]# brctl show
>
> bridge name bridge id STP enabled interfaces
>
> virbr0 8000.525400ea5aeb yes virbr0-nic
>
>
>
> [root at clab-kvm02 ~]#
>
>
>
>
>
> [root at clab-kvm02 libvirt]# ovs-vsctl show
>
> 999f5e2f-bd63-4026-8956-2b6a5c726db8
>
> Bridge "ovsbr0"
>
> Port "ovsbr0"
>
> Interface "ovsbr0"
>
> type: internal
>
> Port "eth0"
>
> Interface "eth0"
>
> ovs_version: "1.9.0"
>
>
>
>
>
> Now when I create a new virtual machine using virt-manager it is not getting
> IP and working. If any one of you have come across the same and know the
> solution please share it.
You need to do more analysis before simply posting that you cannot
receive traffic. For example, can you access the network from the
hypervisor through OVS?, what does the configuration look like when
you start the new VM?, etc.
More information about the discuss
mailing list