[
https://issues.apache.org/jira/browse/CLOUDSTACK-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637090#comment-13637090
]
angeline shen commented on CLOUDSTACK-101:
------------------------------------------
RHEL 6.3 (CentOS 6.3) openvswitch test configuration setup
Test scanrio 1:
After completing
http://nullworks.wordpress.com/2012/09/19/kvm-and-openvswitch-on-centos-6-3-minimal/
to setup RHEL 6.3 openvswitch, encountered following problems:
1. In this scenario, after service openvswitch start, host is still up
running but completely lost connection to network.
[root@Rack3Host16 /]# service openvswitch start
Inserting brcompat module [ OK ]
Starting ovsdb-server [ OK ]
Configuring Open vSwitch system IDs [ OK ]
Starting ovs-vswitchd [ OK ]
Starting ovs-brcompatd [ OK ]
iptables already has a rule for gre, not explicitly enabling.
[root@Rack3Host16 /]#
2. content of various files:
/etc/sysconfig/network-scripts/ifcfg-ovsbr1 :
DEVICE=ovsbr1
ONBOOT=yes
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
IPADDR=10.223.58.195
GATEWAY=10.223.58.193
NETMASK=255.255.255.0
HOTPLUG=no
ifconfig output:
em2 Link encap:Ethernet HWaddr BC:30:5B:D4:16:3D
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17 Memory:dc000000-dc012800
eth1 Link encap:Ethernet HWaddr BC:30:5B:D4:16:3C
inet addr:10.223.58.195 Bcast:10.223.58.255 Mask:255.255.255.192
inet6 addr: fc00:2::be30:5bff:fed4:163c/64 Scope:Global
inet6 addr: fe80::be30:5bff:fed4:163c/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:12169 errors:0 dropped:0 overruns:0 frame:0
TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10750397 (10.2 MiB) TX bytes:6661 (6.5 KiB)
Interrupt:16 Memory:da000000-da012800
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:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1064 (1.0 KiB) TX bytes:1064 (1.0 KiB)
ovsbr1 Link encap:Ethernet HWaddr BC:30:5B:D4:16:3C
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:11826 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10653029 (10.1 MiB) TX bytes:0 (0.0 b)
virbr0 Link encap:Ethernet HWaddr 4A:29:63:30:C6:48
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
3. traceroute no longer works
> OVS support in KVM
> ------------------
>
> Key: CLOUDSTACK-101
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-101
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM
> Affects Versions: pre-4.0.0, 4.0.0
> Reporter: Prasanna Santhanam
> Assignee: Hugo Trippaers
> Labels: kvm, ovs
> Fix For: Future
>
> Attachments: agentlog513.doc, Apache_CloudStack-4 1
> 0-Installation_Guide-en-US.pdf, cloudstack-agent-err.docx,
> cloudstack-agent-out.docx
>
>
> OVS support currently works for XenServer but not in KVM. This is to improve
> the KVM agent to support OVS which has been part of the Linux kernel mainline
> for sometime now.
> Release Planning:
> Dev list discussion: http://markmail.org/thread/x2zncdgac52essxf
> Functional Spec: unknown
> Feature Branch: unknown
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
