[
https://issues.apache.org/jira/browse/CLOUDSTACK-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Murali Reddy resolved CLOUDSTACK-6925.
--------------------------------------
Resolution: Fixed
with this fix, there wont any logic of using dom0 VIF's.
> [OVS] get rid custom logic to create bridges on hosts in the XenServer pool
> ---------------------------------------------------------------------------
>
> Key: CLOUDSTACK-6925
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6925
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.2.0
> Reporter: Murali Reddy
> Assignee: Murali Reddy
> Priority: Critical
> Fix For: 4.4.0
>
>
> In XenServer, when we created a GRE tunnel network, they don't have a PIF
> attached it. XenServer treats network without a PIF attached as internal
> network. In a pool, XenServer internal network is visible across the hosts in
> the pool, but bridge is created only on the first host on which VIF connected
> to internal network is started. On rest of the hosts when VM is started, xapi
> fails with VM_REQUIRES_NETWORK exception. CloudStack had workaround for this
> problem where it creates a dom0 VIF connected to the network. Which plugged
> and unplugged to ensure bridge is created on all hosts in the pool. This
> approach is error prone and resulted in multiple issues.
> Recommended way by XenServer, is to mark the network other-config param
> assume_network_is_shared set to true.
> Network.other_config:assume_network_is_shared=true
> This will ensure, when a VM connected to a internal network is launched on
> any host in the pool, bridge is automatically provisioned.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
