Re: Unable to start a HVM VM with more than 2 volumes attached using XenServer 6.5 and ACS 4.7.1

[Sudhansu Sahu]

I will close CLOUDSTACK-9367 as duplicate of CLOUDSTACK-9363.

On 22/04/16 8:06 pm, "Simon Godard"  wrote:

>Hi Sudhansu,
>
>Thanks! The fix doesn’t appear to be in the master branch or the 4.7.x
>branch. I had created the following bug yesterday:
>https://issues.apache.org/jira/browse/CLOUDSTACK-9363, but I just noticed
>you created https://issues.apache.org/jira/browse/CLOUDSTACK-9367.
>-- 
>Simon
>
>> On Apr 22, 2016, at 05:56, Sudhansu Sahu 
>>wrote:
>> 
>> Hi Simon,
>> 
>> We have faced similar issue in past. I think there is fix available for
>> this.
>> Let me check if its fixed in ACS, if not I will create a pull request
>>for
>> this.
>> 
>> Thanks
>> Sudhansu
>> 
>> On 21/04/16 6:06 pm, "Koushik Das" >> wrote:
>> 
>>> Once the VM is in running state, is "allowed devices" showing proper
>>> list? After that if auto detect is working properly then maybe the
>>>issue
>>> is somewhere else.
>>> 
>>> -Koushik
>>> 
>>> 
>>> From: Simon Godard 
>>> Sent: Thursday, April 21, 2016 12:41 AM
>>> To: CloudStack Users Mailing list
>>> Subject: Re: Unable to start a HVM VM with more than 2 volumes attached
>>> using XenServer 6.5 and ACS 4.7.1
>>> 
>>> After more investigation, I can confirm that the problem is only for
>>>HVM.
>>> I tried with a PV vm and everything is fine.
>>> 
>>> For some reason, performing the call: VM.get_allowed_VBD_devices on a
>>>HVM
>>> while the VM is still in starting state only returns a subset of device
>>> Ids: [1, 2] instead of [1,2,3,Š,15] on PV. The logic then reverts to
>>> Œautodetect¹ which also seems invalid for a HVM VM.
>>> 
>>> --
>>> Simon
>>> 
 On Apr 20, 2016, at 08:20, Simon Godard  wrote:
 
 Hi,
 
 We are getting a weird error when trying to start a VM (based on a HVM
 template) when attaching more than 2 volumes. We are using XenServer
6.5
 and CloudStack 4.7.1. Here are the logs:
 
 ACS
 Unable to start i-152-612-VM due to
 The device name is invalid
at com.xensource.xenapi.Types.checkResponse(Types.java:1169)
at com.xensource.xenapi.Connection.dispatch(Connection.java:395)
at
 
com.cloud.hypervisor.xenserver.resource.XenServerConnectionPool$XenServ
er
 Connection.dispatch(XenServerConnectionPool.java:457)
at com.xensource.xenapi.VBD.create(VBD.java:322)
at
 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.createVbd(Ci
tr
 ixResourceBase.java:1148)
at
 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixStartComm
an
 dWrapper.execute(CitrixStartCommandWrapper.java:119)
at
 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixStartComm
an
 dWrapper.execute(CitrixStartCommandWrapper.java:53)
at
 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixRequestWr
ap
 per.execute(CitrixRequestWrapper.java:122)
at
 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.executeReque
st
 (CitrixResourceBase.java:1678)
 
 XenServer
 Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
 :::80|VBD.create R:3c596e35d366|audit] VBD.create: VM =
 '23da57b8-cc94-3edd-66af-97397c1e9f89 (i-152-614-VM)'; VDI = 'invalid'
 Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
 :::80|VBD.create R:3c596e35d366|xapi] Checking whether there's a
migrate
 in progress...
 Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
 :::80|VBD.create R:3c596e35d366|xapi] VBD.create (device = 3; uuid =
 d32bd2fb-68d9-a20b-3632-43c5cffd5ca1; ref =
 OpaqueRef:d5d36ea6-2b79-2efd-c2ad-27403ffbdbf8)
 Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18677027 UNIX
 /var/xapi/xapi||dummytaskhelper] task dispatch:SR.get_other_config
 D:764bb880e1f7 created by task D:9e603ca8e24b
 Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18677028 UNIX
 /var/xapi/xapi||dummytaskhelper] task dispatch:SR.get_sm_config
 D:b30be613f286 created by task D:9e603ca8e24b
 Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
 :::80|VM.get_allowed_VBD_devices D:65d1aeb0e377|audit]
 VM.get_allowed_VBD_devices: VM = '23da57b8-cc94-3edd-66af-97397c1e9f89
 (i-152-614-VM)'
 Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
 :::80|VBD.create R:f5513cd51b7d|audit] VBD.create: VM =
 '23da57b8-cc94-3edd-66af-97397c1e9f89 (i-152-614-VM)'; VDI =
 '7c882c4f-eaed-49c9-952d-53f2db998ecd'
 Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
 :::80|VBD.create R:f5513cd51b7d|xapi] Checking whether there's a
migrate
 in progress...
 Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
 :::80|VBD.create R:f5513cd51b7d|xapi] VBD.create (device = 2; uuid =
 b83f7

Re: Unable to start a HVM VM with more than 2 volumes attached using XenServer 6.5 and ACS 4.7.1

[Simon Godard]

Hi Sudhansu,

Thanks! The fix doesn’t appear to be in the master branch or the 4.7.x branch. 
I had created the following bug yesterday: 
https://issues.apache.org/jira/browse/CLOUDSTACK-9363, but I just noticed you 
created https://issues.apache.org/jira/browse/CLOUDSTACK-9367.
-- 
Simon

> On Apr 22, 2016, at 05:56, Sudhansu Sahu  wrote:
> 
> Hi Simon,
> 
> We have faced similar issue in past. I think there is fix available for
> this.
> Let me check if its fixed in ACS, if not I will create a pull request for
> this.
> 
> Thanks
> Sudhansu
> 
> On 21/04/16 6:06 pm, "Koushik Das"  > wrote:
> 
>> Once the VM is in running state, is "allowed devices" showing proper
>> list? After that if auto detect is working properly then maybe the issue
>> is somewhere else.
>> 
>> -Koushik
>> 
>> 
>> From: Simon Godard 
>> Sent: Thursday, April 21, 2016 12:41 AM
>> To: CloudStack Users Mailing list
>> Subject: Re: Unable to start a HVM VM with more than 2 volumes attached
>> using XenServer 6.5 and ACS 4.7.1
>> 
>> After more investigation, I can confirm that the problem is only for HVM.
>> I tried with a PV vm and everything is fine.
>> 
>> For some reason, performing the call: VM.get_allowed_VBD_devices on a HVM
>> while the VM is still in starting state only returns a subset of device
>> Ids: [1, 2] instead of [1,2,3,Š,15] on PV. The logic then reverts to
>> Œautodetect¹ which also seems invalid for a HVM VM.
>> 
>> --
>> Simon
>> 
>>> On Apr 20, 2016, at 08:20, Simon Godard  wrote:
>>> 
>>> Hi,
>>> 
>>> We are getting a weird error when trying to start a VM (based on a HVM
>>> template) when attaching more than 2 volumes. We are using XenServer 6.5
>>> and CloudStack 4.7.1. Here are the logs:
>>> 
>>> ACS
>>> Unable to start i-152-612-VM due to
>>> The device name is invalid
>>>at com.xensource.xenapi.Types.checkResponse(Types.java:1169)
>>>at com.xensource.xenapi.Connection.dispatch(Connection.java:395)
>>>at
>>> com.cloud.hypervisor.xenserver.resource.XenServerConnectionPool$XenServer
>>> Connection.dispatch(XenServerConnectionPool.java:457)
>>>at com.xensource.xenapi.VBD.create(VBD.java:322)
>>>at
>>> com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.createVbd(Citr
>>> ixResourceBase.java:1148)
>>>at
>>> com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixStartComman
>>> dWrapper.execute(CitrixStartCommandWrapper.java:119)
>>>at
>>> com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixStartComman
>>> dWrapper.execute(CitrixStartCommandWrapper.java:53)
>>>at
>>> com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixRequestWrap
>>> per.execute(CitrixRequestWrapper.java:122)
>>>at
>>> com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.executeRequest
>>> (CitrixResourceBase.java:1678)
>>> 
>>> XenServer
>>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>> :::80|VBD.create R:3c596e35d366|audit] VBD.create: VM =
>>> '23da57b8-cc94-3edd-66af-97397c1e9f89 (i-152-614-VM)'; VDI = 'invalid'
>>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>> :::80|VBD.create R:3c596e35d366|xapi] Checking whether there's a migrate
>>> in progress...
>>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>> :::80|VBD.create R:3c596e35d366|xapi] VBD.create (device = 3; uuid =
>>> d32bd2fb-68d9-a20b-3632-43c5cffd5ca1; ref =
>>> OpaqueRef:d5d36ea6-2b79-2efd-c2ad-27403ffbdbf8)
>>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18677027 UNIX
>>> /var/xapi/xapi||dummytaskhelper] task dispatch:SR.get_other_config
>>> D:764bb880e1f7 created by task D:9e603ca8e24b
>>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18677028 UNIX
>>> /var/xapi/xapi||dummytaskhelper] task dispatch:SR.get_sm_config
>>> D:b30be613f286 created by task D:9e603ca8e24b
>>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>> :::80|VM.get_allowed_VBD_devices D:65d1aeb0e377|audit]
>>> VM.get_allowed_VBD_devices: VM = '23da57b8-cc94-3edd-66af-97397c1e9f89
>>> (i-152-614-VM)'
>>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>> :::80|VBD.create R:f5513cd51b7d|audit] VBD.create: VM =
>>> '23da57b8-cc94-3edd-66af-97397c1e9f89 (i-152-614-VM)'; VDI =
>>> '7c882c4f-eaed-49c9-952d-53f2db998ecd'
>>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>> :::80|VBD.create R:f5513cd51b7d|xapi] Checking whether there's a migrate
>>> in progress...
>>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>> :::80|VBD.create R:f5513cd51b7d|xapi] VBD.create (device = 2; uuid =
>>> b83f771a-c796-8f5b-26de-fb648327e305; ref =
>>> OpaqueRef:f147-8d60-52b6-8041-72cf95fa7f44)
>>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>> :::80|VM.get_allowed_VBD_devices D:c180118513de|audit]
>>> VM.get_allowed_VBD_devices: VM = '23da57b8-cc94-3edd-66af-97397c1e9f89
>>>

Re: Error: "Unable to add host"

[Cayetano Rodríguez]

Now it shows the kvm_intel line

[root@srvr1 ~]# lsmod | grep kvm
kvm_intel  55624  0
kvm   341551  1 kvm_intel

2016-04-22 6:12 GMT+02:00 Pavan Bandarupally <
pavan.bandarupa...@accelerite.com>:

> What did the lsmod | grep kvm output after enabling virtualization ? Did
> it show kvm_intel this time ? If it hasn't can you try installing kvm-qemu
> package and give it a try ?
>
> -Original Message-
> From: Cayetano Rodríguez [mailto:tfg.cloudcomput...@gmail.com]
> Sent: Thursday, April 21, 2016 11:56 PM
> To: users@cloudstack.apache.org
> Subject: Re: Error: "Unable to add host"
>
> It wasn't enabled but I enabled the virtualization in the BIOS and I still
> can't add a host
>
> El lunes, 18 de abril de 2016, Pavan Bandarupally <
> pavan.bandarupa...@accelerite.com> escribió:
>
> > Is Virtualization enabled in the BIOS for the machine ?
> >
> > -Original Message-
> > From: Cayetano Rodríguez [mailto:tfg.cloudcomput...@gmail.com
> > ]
> > Sent: Friday, April 15, 2016 8:05 PM
> > To: users@cloudstack.apache.org 
> > Subject: Re: Error: "Unable to add host"
> >
> > Yes, I'm trying to setup everything on a single machine. I followed
> > that guide and now I've checked all steps in the KVM section. When I
> execute  "
> > lsmod | grep kvm "
> >  I get the following output:
> > [root@srvr1 ~]# lsmod | grep kvm
> > kvm   341551  0
> >
> > In the guide it appears in the output another line (kvm_intel), am I
> > doing something wrong so that line doesn't appear?
> >
> > Thank you
> >
> > 2016-04-15 4:06 GMT+02:00 Pavan Bandarupally <
> > pavan.bandarupa...@accelerite.com >:
> >
> > > If you have resources, it is recommended to have management server
> > > and host on separate machines. But just to troubleshoot your
> > > environment you can check the below link and see if things work.
> > >
> > > From my understanding you are trying to setup everything (
> > > management server and hotst) on a single machine. The error you face
> > > is generally seen if the hypervisor host doesn't have KVM agent
> > > installed properly (I might be wrong here). Can you please go
> > > through the below link and make sure that you have followed all the
> > > required steps (for KVM installation ) and confirm if KVM is
> > > properly installed (say by checking
> > lsmod | grep kvm ) ?
> > >
> > >
> > > http://docs.cloudstack.apache.org/projects/cloudstack-installation/e
> > > n/
> > > 4.6/qig.html
> > >
> > > Regards,
> > > Pavan
> > >
> > >
> > > -Original Message-
> > > From: Cayetano Rodríguez [mailto:tfg.cloudcomput...@gmail.com
> > ]
> > > Sent: Friday, April 15, 2016 6:08 AM
> > > To: users@cloudstack.apache.org 
> > > Subject: Re: Error: "Unable to add host"
> > >
> > > The managenent ip address is the same as the host ip address, and
> > > the same as the machine that I'm using...
> > > I've done this because I've followed the Quick Installation Guide
> > > that is focused on doing everything in the same machine, and this
> > > guide specifies to use the same ip addresses in managenent server
> > > and the
> > first host.
> > >
> > > I am interested in getting started on CloudStack doing this "trial"
> > > installation, so I don't need lots of resources (and actually don't
> > > have them at this moment). For this reason I think doing everything
> > > in the same machine is the best option for me.
> > >
> > > If you could help me doing this that would be great, or if it's not
> > > possible and you think it's better and easier separating the
> > > management server and host, I could look for another machine to use.
> > >
> > > Thank you very much.
> > >
> > > El jueves, 14 de abril de 2016, Simon Weller  > > escribió:
> > >
> > > > Can you ping the ip address you supplied from the management server?
> > > > Are you able to ssh into it using the credentials (from the
> > > > management
> > > > server) you're using in the Cloudstack GUI?
> > > >
> > > > ICloudstack is really designed to be deployed on separate servers,
> > > > so mixing management and hosts can complicate things a fair bit.
> > > >
> > > > - Si
> > > >
> > > >
> > > > 
> > > > From: Cayetano Rodríguez  > > >  >
> > > > Sent: Thursday, April 14, 2016 12:18 PM
> > > > To: users@cloudstack.apache.org  
> > > > Subject: Error: "Unable to add host"
> > > >
> > > > Hi everyone!
> > > >
> > > > I've followed the "Quick Installation Guide for Centos 6" guide,
> > > > to install CloudStack in one machine with Centos 6.5. I've
> > > > followed all steps and finished installing, but I get an error
> > > > while configuring it. The error appears when CloudStack is trying
> > > > to add a host. The error says: "Unable to add the host".
> > > >
> > > > I've checked /var/log/cloudstack/management/management-server.log
> > > > and this is the complete error:
> > > >
> > > >
> > > >
> > > > 2016-04-14 19:10:36,257 DEBUG [c.c.a.ApiServlet]
> > > > (catalina-exec-1:ctx-3c6

Re: Unable to start a HVM VM with more than 2 volumes attached using XenServer 6.5 and ACS 4.7.1

[Sudhansu Sahu]

Hi Simon,

We have faced similar issue in past. I think there is fix available for
this.
Let me check if its fixed in ACS, if not I will create a pull request for
this.

Thanks
Sudhansu

On 21/04/16 6:06 pm, "Koushik Das"  wrote:

>Once the VM is in running state, is "allowed devices" showing proper
>list? After that if auto detect is working properly then maybe the issue
>is somewhere else.
>
>-Koushik
>
>
>From: Simon Godard 
>Sent: Thursday, April 21, 2016 12:41 AM
>To: CloudStack Users Mailing list
>Subject: Re: Unable to start a HVM VM with more than 2 volumes attached
>using XenServer 6.5 and ACS 4.7.1
>
>After more investigation, I can confirm that the problem is only for HVM.
>I tried with a PV vm and everything is fine.
>
>For some reason, performing the call: VM.get_allowed_VBD_devices on a HVM
>while the VM is still in starting state only returns a subset of device
>Ids: [1, 2] instead of [1,2,3,Š,15] on PV. The logic then reverts to
>Œautodetect¹ which also seems invalid for a HVM VM.
>
>--
>Simon
>
>> On Apr 20, 2016, at 08:20, Simon Godard  wrote:
>>
>> Hi,
>>
>> We are getting a weird error when trying to start a VM (based on a HVM
>>template) when attaching more than 2 volumes. We are using XenServer 6.5
>>and CloudStack 4.7.1. Here are the logs:
>>
>> ACS
>> Unable to start i-152-612-VM due to
>> The device name is invalid
>> at com.xensource.xenapi.Types.checkResponse(Types.java:1169)
>> at com.xensource.xenapi.Connection.dispatch(Connection.java:395)
>> at
>>com.cloud.hypervisor.xenserver.resource.XenServerConnectionPool$XenServer
>>Connection.dispatch(XenServerConnectionPool.java:457)
>> at com.xensource.xenapi.VBD.create(VBD.java:322)
>> at
>>com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.createVbd(Citr
>>ixResourceBase.java:1148)
>> at
>>com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixStartComman
>>dWrapper.execute(CitrixStartCommandWrapper.java:119)
>> at
>>com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixStartComman
>>dWrapper.execute(CitrixStartCommandWrapper.java:53)
>> at
>>com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixRequestWrap
>>per.execute(CitrixRequestWrapper.java:122)
>> at
>>com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.executeRequest
>>(CitrixResourceBase.java:1678)
>>
>> XenServer
>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>:::80|VBD.create R:3c596e35d366|audit] VBD.create: VM =
>>'23da57b8-cc94-3edd-66af-97397c1e9f89 (i-152-614-VM)'; VDI = 'invalid'
>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>:::80|VBD.create R:3c596e35d366|xapi] Checking whether there's a migrate
>>in progress...
>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>:::80|VBD.create R:3c596e35d366|xapi] VBD.create (device = 3; uuid =
>>d32bd2fb-68d9-a20b-3632-43c5cffd5ca1; ref =
>>OpaqueRef:d5d36ea6-2b79-2efd-c2ad-27403ffbdbf8)
>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18677027 UNIX
>>/var/xapi/xapi||dummytaskhelper] task dispatch:SR.get_other_config
>>D:764bb880e1f7 created by task D:9e603ca8e24b
>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18677028 UNIX
>>/var/xapi/xapi||dummytaskhelper] task dispatch:SR.get_sm_config
>>D:b30be613f286 created by task D:9e603ca8e24b
>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>:::80|VM.get_allowed_VBD_devices D:65d1aeb0e377|audit]
>>VM.get_allowed_VBD_devices: VM = '23da57b8-cc94-3edd-66af-97397c1e9f89
>>(i-152-614-VM)'
>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>:::80|VBD.create R:f5513cd51b7d|audit] VBD.create: VM =
>>'23da57b8-cc94-3edd-66af-97397c1e9f89 (i-152-614-VM)'; VDI =
>>'7c882c4f-eaed-49c9-952d-53f2db998ecd'
>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>:::80|VBD.create R:f5513cd51b7d|xapi] Checking whether there's a migrate
>>in progress...
>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>:::80|VBD.create R:f5513cd51b7d|xapi] VBD.create (device = 2; uuid =
>>b83f771a-c796-8f5b-26de-fb648327e305; ref =
>>OpaqueRef:f147-8d60-52b6-8041-72cf95fa7f44)
>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>:::80|VM.get_allowed_VBD_devices D:c180118513de|audit]
>>VM.get_allowed_VBD_devices: VM = '23da57b8-cc94-3edd-66af-97397c1e9f89
>>(i-152-614-VM)'
>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>:::80|VBD.create R:3a50f805fbb1|audit] VBD.create: VM =
>>'23da57b8-cc94-3edd-66af-97397c1e9f89 (i-152-614-VM)'; VDI =
>>'78ab2cc5-a7ec-4709-9556-a1d6bfbc2b65'
>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>:::80|VBD.create R:3a50f805fbb1|xapi] Checking whether there's a migrate
>>in progress...
>> Apr 19 14:00:33 cca-t2-xen01 xapi: [debug|cca-t2-xen01|18676540 INET
>>:::80|VBD.create R:3a50f805fbb1|xapi] VBD.create (device = 1; uuid =

Re: VR issue High importance

[Dag Sonstebo]

Hi Venkatesh,

changing service offering for VRs is documented in 
http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.8/systemvm.html.
 

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue






Regards,

Dag Sonstebo

dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
On 22/04/2016, 07:00, "kotipalli venkatesh"  
wrote:

>Hi All,
>
>I am creating a new custom service offering is pointed to the existing
>VR. Here my concern  is when ever we rebooted the VR its created a new
>VR with default offering, but i want with custom offering please
>suggest where do we need to change the parameters in global settings.
>
>Please help me guys.
>
>Regards,
>Venkatesh.k
>
>On 4/6/16, Sanjeev Neelarapu  wrote:
>> Hi Venkat,
>>
>> We generally see the following exception when management server is not able
>> to reach the VR:
>> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is
>> unreachable: Unable to apply userdata and password entry on router
>>
>> There might be some network glitches that caused the issue. VR reboot is not
>> the obvious solution.
>>
>> Best Regards,
>> Sanjeev N
>> Chief Product Engineer, Accelerite
>> Off: +91 40 6722 9368 | EMail: sanjeev.neelar...@accelerite.com
>>
>>
>> -Original Message-
>> From: Suresh Sadhu [mailto:suresh.sa...@accelerite.com]
>> Sent: Wednesday, April 06, 2016 6:04 PM
>> To: users@cloudstack.apache.org
>> Subject: RE: VR issue High importance
>>
>> HI Venkat,
>>
>> Which hypervisor you are using  and also check the agent log in case of
>> KVM.
>>
>> For xenserver ,check the SMlog . for  that exception it will clearly tell
>> you the reason for failure.
>>
>> Mostly it will cause t due  to problem in  ssh key file ( if  router is not
>> reachable from host) or   no space left.
>>
>> So check the  router is accessible from the host/as well  as capacity.
>>
>> Regards
>> Sadhu
>>
>>
>>
>>
>>
>>
>> -Original Message-
>> From: tejas.sh...@frontier.in [mailto:tejas.sh...@frontier.in]
>> Sent: Wednesday, April 6, 2016 5:42 PM
>> To: users@cloudstack.apache.org
>> Subject: Re: VR issue High importance
>>
>> Hello venkat,
>>
>> Just increase cpu and mem overcommitment setting in global
>> configuration.
>>
>> Thanks,
>> Tejas
>>
>> Sent from Nine
>>
>>
>> From: kotipalli venkatesh 
>> Sent: Apr 6, 2016 3:36 PM
>> To: users@cloudstack.apache.org
>> Subject: VR issue High importance
>>
>> Hi All,
>>
>> when we are trying to  spin a instance getting the error is  "Unable to
>> start a VM due to insufficient capacity" so we have checked storage and RAM
>> it's look enough room place in host.
>>
>> *And also we have checked the management server log we identified that below
>> error message :*
>>
>> 2016-04-05 06:01:35,974 INFO  [c.c.v.VirtualMachineManagerImpl]
>> (Job-Executor-114:ctx-9e73f683 ctx-419ad956) Unable to contact resource.
>> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is
>> unreachable: Unable to apply userdata and password entry on router
>>
>> In this scenario we have rebooted the respected Virtual Router(VR) and then
>> spin a instance successfully deployed.
>>
>> We are thinking that rebooted is not permanent solution andalso not good
>> habit.
>>
>> Please guys if anyone facing this situation Please share the proper solution
>> without any impact on existing instances.
>>
>> Regards,
>> Venkatesh.k
>>
>>
>>
>>
>> DISCLAIMER
>> ==
>> This e-mail may contain privileged and confidential information which is the
>> property of Accelerite, a Persistent Systems business. It is intended only
>> for the use of the individual or entity to which it is addressed. If you are
>> not the intended recipient, you are not authorized to read, retain, copy,
>> print, distribute or use this message. If you have received this
>> communication in error, please notify the sender and delete all copies of
>> this message. Accelerite, a Persistent Systems business does not accept any
>> liability for virus infected mails.
>>
>>
>>
>> DISCLAIMER
>> ==
>> This e-mail may contain privileged and confidential information which is the
>> property of Accelerite, a Persistent Systems business. It is intended only
>> for the use of the individual or entity to which it is addressed. If you are
>> not the intended recipient, you are not authorized to read, retain, copy,
>> print, distribute or use this message. If you have received this
>> communication in error, please notify the sender and delete all copies of
>> this message. Accelerite, a Persistent Systems business does not accept any
>> liability for virus infected mails.
>>