I have generally only seen the getDomRVersionCmd fail followed by stopping the vm if it can't ssh into the system VM to run the command. I am sure this is a general symptom of failing to set up or communicate with the virtual router rather than an actual issue related to getting the domr version.
You should see if you can ssh into the router when it's in the running state, but before cloudstack sends a stop. In the past I have accomplished this by stopping the cloud-agent before it issues a stopcommand. Which version are you running? There have been several fixes in the past month or two to try to make the cloud ssh key copy over more reliably. On Tue, Oct 16, 2012 at 9:50 AM, <cloudsta...@163.com> wrote: > i am tracing this problem. but i ask about it first. > > 1.what it use for? what kinds of data it return when launch > GetDomRVersionCmd if i write missing parts? > > now i only know when new a routerVM(which created when new a userVM) > because of missing GetDomRVersionCmd , its answer result is false , which > will lead a stopcommand sent to stop this VM, actually vm is in running > state now. > > 2. GetDomRVersionCmd is related to router or other kinds of VM? > > why secondarystorageVm and consoleVm success to deploy? > > thanks
