[
https://issues.apache.org/jira/browse/CLOUDSTACK-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637216#comment-13637216
]
Hugo Trippaers commented on CLOUDSTACK-101:
-------------------------------------------
Hey Angelina,
Did you configure the physical network adapter as a ovs bridge port?
if for example eth0 is your physical nic, you need to set
DEVICETYPE=ovs
TYPE=OVSPort
OVS_BRIDGE=ovsbr1
otherwise the physical interface will not be connected to the bridge and you
will lose connectivity.
You can check with "ovs-vsctl list-ports ovsbr1" , that command should list
your physical interface.
Feel free to ping me if you see me on IRC so i can help you directly.
> 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
