I'm assuming you're doing the migration from either the XenServer command line, or from XenCenter. If you do the VM migration from within CloudStack, CloudStack will create the VLAN on the target and everything will work as you expect. Here's the doc page: https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Admin_Guide/manual-live-migration.html
A word of caution about managing XenServer "objects" outside of CloudStack. CloudStack considers itself the "owner" of the objects, so if you make changes to them from outside of CloudStack, its very likely CloudStack won't know about those changes and you could run into problems. -tim On Mon, Sep 8, 2014 at 6:35 AM, Pentium100 <pentium...@gmail.com> wrote: > Hello, > > If I create a new network and start a couple of instances connected to it > and the instances all start in one host, then the network (vlan) is not > assigned on the rest of the hosts in the pool. This would not be a problem, > except that trying to migrate such a VM to another host results in a > failure because the network is not seen from the destination host. > > If I start enough instances so that both hosts have at least one running, > then migration succeeds (unless it fails for some other unknown reason). > > Is this a known bug or some configuration problem and how to fix it? > > Cloudstack version 4.4.0, XenServer version 6.2.0 >
