{"head":"5a1aacc1c4d15c8d674c91e6010f0023c53d735f","size":2,"push_id":44377165,"shas":[["8f977d84d8d0e8a94af6a86cdb7a04565c9e7987","6e1a438cfe5a6c9e2165665f8c2258849ccc43f0@cloud.com","bug 10579: disable pool vm sync and disable hostTrack for XenServer,\n\nstatus 10579: resolved fixed\n\nreviewed-by: alex","anthony"],["5a1aacc1c4d15c8d674c91e6010f0023c53d735f","6e1a438cfe5a6c9e2165665f8c2258849ccc43f0@cloud.com","bug 11552:\n This bug also happens in XenServer 5.6 FP1, but this issue is hidden by bug 11564.\n There are two issues here\n\n 1.  in XenServer 5.6 FP1/SP2, when a slave host is down ( NIC is unplugged), and before master detect the slave is down( it takes about 10 minutes),\n template.createClone doesn't work sometime, it complains can not contact slave host, looks like XenServer try to start VM on this slave host, we use VM.create instead, we can specify host in VM.create API, so it will not try to connect the slave\n\n 2.  in XenServer 5.6 FP1/SP2,  host tag is introduced into VDI, however in HA case, VM.reset_powerstate and VM.destory doesn't remove this host tag, when CloudStack try to start this VM on other host, XenServer complains this VDI is already used ( or mount as RW). CloudStack will manually remove the host tage in VDI in FenceCommand\n\nstatus 11552: resolved fixed","anthony"]],"ref":"refs/heads/2.2.y"}