2013/8/3 Chiradeep Vittal chiradeep.vit...@citrix.com
On 4.1?
It's on my local branch, cloned from master but I haven't merged for
several weeks. However I concern about the reason. After re-deploying Zone,
everything is ok. Problem maybe comes from id_rsa.cloud key, which was not
patched to
...@citrix.com]
Sent: Saturday, March 30, 2013 2:07 AM
To: dev@cloudstack.apache.org
Subject: Re: Unable to start domR(VR) in devcloud using laster
4.1/master.
You should roll back your devcloud VM to the original and try again.
On DevCloud2, I notice that sometimes the xapi0 bridge
(publickey).
-Original Message-
From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
Sent: Saturday, March 30, 2013 2:07 AM
To: dev@cloudstack.apache.org
Subject: Re: Unable to start domR(VR) in devcloud using laster
4.1/master.
You should roll back your devcloud VM
...@citrix.com]
Sent: Saturday, March 30, 2013 2:07 AM
To: dev@cloudstack.apache.org
Subject: Re: Unable to start domR(VR) in devcloud using laster 4.1/master.
You should roll back your devcloud VM to the original and try again.
On DevCloud2, I notice that sometimes the xapi0 bridge loses its ip
Xen? KVM?
Generally GetDomRVersionCmd failing is only a symptom, it usually
means that cloudstack was never able to communicate with the system
vm. You would need to look at whether the VM actually started on the
host, and some of the text around when the VM was deployed to get any
meaningful
