Thanks Prasanna. It was indeed the problem with my service offerings - I had memory requirement set to 124.00 MB not below 64 MB. When I increased it to 200 MB , I don't see the problem anymore. I have always used a service offering with 124.00 MB before on Xenserver 6.0.2 and did not encounter this issue before.
-Thanks Sangeetha -----Original Message----- From: prasanna [mailto:srivatsav.prasa...@gmail.com] On Behalf Of Prasanna Santhanam Sent: Tuesday, April 16, 2013 11:58 PM To: dev@cloudstack.apache.org Subject: Re: [ACS42][QA]Issues with latest Master Build (Xenserver) On Tue, Apr 16, 2013 at 04:33:40PM -0700, Sangeetha Hariharan wrote: > I am not able to start user Vms successfully using the build from master. I > am testing with Xenserver 6.0.2 hosts. > User Vm starts successfully but it gets to stopped state after few seconds. > > deployVM reports success . But later on cluster sync sees this Vm in > stopped state and sends a StopCommand for this VM. It's not clustersync from the logs really. Something is going wrong on your xenserver. I've seen this happen when the VM deployed has mem limits outside the static-max and static-min defined by xenserver. So anything below 64MB memory starts and then stops. Not sure if that's the case with your deployed VM. -- Prasanna.,
