I don't think there is a link local problem in Tampa. In XenSever 5.6 or XenServer 6.0, CloudStack needs to create a vif on dom0 on link local bridge and plugin the vif to dom0 to make VR migratable. That's a workaround, In Tampa XenServer team seems to try to fix this issue, with Tampa, CloudStack doesn't need to create a vif on dom0 on link local bridge.
Ahbi is working on Tampa integration, he may have more details. -Anthony > -----Original Message----- > From: Alex Huang > Sent: Wednesday, August 29, 2012 10:02 AM > To: cloudstack-dev@incubator.apache.org > Cc: Anthony Xu > Subject: RE: link local issues in xenserver 6 or Tampa? > > Darren, > > The problem is on network restarts I believe. XS 6 doesn't take into > account that there's an extra vif created by the link local. Anthony > has the details but he's away at a conference. I cced him on the > thread. > > --Alex > > > -----Original Message----- > > From: Darren Shepherd [mailto:dar...@godaddy.com] > > Sent: Wednesday, August 29, 2012 9:22 AM > > To: cloudstack-dev@incubator.apache.org > > Subject: link local issues in xenserver 6 or Tampa? > > > > I heard there might have been some issue with link local for the DomR > > working properly on XenServer 6 or possibly Tampa. Does anybody know > > what was the issue and the solution? My team at work is currently > going > > through the effort of trying to get our cloud on XenServer Tampa > release > > (obviously won't go live until its released from Citrix). > > > > Darren > > > > > >
