sorry. executeInSequence=false
2013/5/29 Nguyen Anh Tu <ng.t...@gmail.com> > I just changed StartCommand.java with executeInSequence=true and tested it > with Xen XCP 1.1. The speed was enhanced beatifully. > > Thanks. > > > 2013/4/5 Jeronimo Garcia <garciaj...@gmail.com> > >> https://issues.apache.org/jira/browse/CLOUDSTACK-1940 >> >> Thank you all. >> >> >> On Thu, Apr 4, 2013 at 3:15 PM, Jeronimo Garcia <garciaj...@gmail.com >> >wrote: >> >> > Hi All. >> > >> > Thanks for the help . >> > >> > I'll be trying to fill a bug about this today/tomorrow. >> > >> > Thanks Again >> > >> > >> > On Thu, Apr 4, 2013 at 3:12 PM, Chip Childers < >> chip.child...@sungard.com>wrote: >> > >> >> On Thu, Apr 04, 2013 at 01:09:00PM -0700, Alex Huang wrote: >> >> > Jeronimo, >> >> > >> >> > Do you mind filing a bug for this? >> >> > >> >> > There's some legacy with this that went all the way back to 1.0 of >> our >> >> product. Back then, multiple commands executing on the same >> hypervisor was >> >> just not very reliable. Xen 3 would sometimes brick when multiple vm >> >> commands were executed. I doubt it's necessary any more but we need >> to do >> >> some tests before we can remove this. >> >> > >> >> > I've heard of this type of requests from others as well so a bug >> would >> >> be good to track this. >> >> >> >> Yeah, Ilya and Kelcey were asking about it around VMware. >> >> >> >> >> > >> > > > > -- > > N.g.U.y.e.N.A.n.H.t.U > -- N.g.U.y.e.N.A.n.H.t.U
