2013/8/3 Chiradeep Vittal
> 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 systemvm because of an unkno
gt;> debug1: SSH2_MSG_NEWKEYS sent
>> debug1: expecting SSH2_MSG_NEWKEYS
>> debug2: set_newkeys: mode 0
>> debug1: SSH2_MSG_NEWKEYS received
>> debug1: Roaming not allowed by server
>> debug1: SSH2_MSG_SERVICE_REQUEST sent
>> debug2: service_accept: ssh-userauth
i-keyex,gssapi-with-mic,publickey,keyboard-interactive,password
> debug3: authmethod_lookup publickey
> debug3: remaining preferred: keyboard-interactive,password
> debug3: authmethod_is_enabled publickey
> debug1: Next authentication method: publickey
> debug1: Offering RSA public ke
y.
Permission denied (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.
>
> Yo
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
address and hence loses the 169.254.0.0/16 route.
You can work around this by
ifconfig xapi0 (check for ipv4 address)
ip route show (check for 169.254 route)
If
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 erro
Hi All,
VR is not getting started failing the instance creation. Anywork around for
this issue?
[network.router.VirtualNetworkApplianceManagerImpl] (Job-Executor-1:job-8)
Unable to get the template/scripts version of router r-4-VM due to:
getDomRVersionCmd failed
INFO [cloud.vm.VirtualMachine
