Hello Oliver, You will need to study the cloud-init. It works pretty well with all below mentioned OS. You can achieve a lot more then Hostname, Password and grow partition. You should use standard partition rather than LVM and there should be no portion after the root partition. Cloud-init will auto resize the partition if it finds any free sector in backend HDD. You may also need to install few extra packages like - cloud-utils-growpart. Just have a look on the document.
However, you can achieve same with Window’s instance as well. Cloud base-init works with windows and it provides the same functionality that way cloud-init provides with Linux OS. Please find the link below - For Linux - https://cloudinit.readthedocs.io/en/latest/topics/modules.html#growpart <https://cloudinit.readthedocs.io/en/latest/topics/modules.html#growpart> For Windows - https://cloudbase-init.readthedocs.io/en/latest/config.html#cloudstack <https://cloudbase-init.readthedocs.io/en/latest/config.html#cloudstack> Vivek Kumar Sr. Manager - Cloud & DevOps TechOps | Indiqus Technologies vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com> www.indiqus.com <https://www.indiqus.com/> > On 12-Jul-2022, at 10:02 PM, Olivier GUIN <olivier.g...@ariasnet.com> wrote: > > Hello Vivek, > > Can you help me to create template with xcp-ng. > > Debian, Ubuntu and CentOS, also hostname, password, it's OK but Grow > partition not ! > > Best regards, > > Olivier > > Le 12/07/2022 à 11:10, Vivek Kumar a écrit : >> Hello Oliver, >> >> >> Can you check the path of your vhd in DB and then check on your XenServer. >> If this is giving error for ROOT disk then mention the ROOT disk name and if >> it is data disk then mention the data disk name. >> >> 1- select * from volumes where name = ‘ROOT-****’; ( Note the PATH ). >> 2- Go to your XenServer and search - xe vdi-list name-label = ‘ROOT-***’ >> >> Check if the UUID from above XenServer command is matching with the path >> from DB. If not then try to manually update the path ( Note the UUID from xe >> vdi-list command and update in the volume table for that disk ). >> >> >> >> >> Vivek Kumar >> Sr. Manager - Cloud & DevOps >> TechOps | Indiqus Technologies >> >> vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com> >> <mailto:vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com>> >> www.indiqus.com <http://www.indiqus.com/> <https://www.indiqus.com/ >> <https://www.indiqus.com/>> >> >> >> >> >>> On 12-Jul-2022, at 7:16 PM, Olivier GUIN >>> <olivier.g...@ariasnet.com.INVALID> wrote: >>> >>> New message ! >>> >>> 2022-07-12 10:39:55,634 WARN [c.c.h.x.r.CitrixResourceBase] >>> (DirectAgent-245:ctx-055d42cb) (logid:d08a2c97) Unable to start i-40-76-VM >>> due to >>> The uuid you supplied was invalid. >>> >>> 2022-07-12 10:39:55,652 WARN [c.c.h.x.r.CitrixResourceBase] >>> (DirectAgent-245:ctx-055d42cb) (logid:d08a2c97) Unable to clean up VBD due >>> to >>> You gave an invalid object reference. The object may have recently been >>> deleted. The class parameter gives the type of reference given, and the >>> handle parameter echoes the bad value given. >>> >>> ? >>> >>> Le 12/07/2022 à 09:16, Olivier GUIN a écrit : >>>> Hi there, >>>> >>>> I have a message 'Unable to start a VM due to insufficient capacity'I >>>> can't find the problem. >>>> >>>> I have this problem on only 2 VMs! >>>> >>>> 2022-07-12 09:00:10,692 ERROR [c.c.a.ApiAsyncJobDispatcher] >>>> (API-Job-Executor-29:ctx-870c9fde job-462574) (logid:760cc3b8) Unexpected >>>> exception while executing >>>> org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin >>>> com.cloud.utils.exception.CloudRuntimeException: Unable to start a VM due >>>> to insufficient capacity >>>> at >>>> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:751) >>>> at >>>> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:255) >>>> at >>>> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:214) >>>> at >>>> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:4938) >>>> at >>>> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2897) >>>> at jdk.internal.reflect.GeneratedMethodAccessor940.invoke(Unknown Source) >>>> at >>>> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>>> at java.base/java.lang.reflect.Method.invoke(Method.java:566) >>>> at >>>> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344) >>>> at >>>> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198) >>>> at >>>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) >>>> at >>>> org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:107) >>>> at >>>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175) >>>> at >>>> com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51) >>>> at >>>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175) >>>> at >>>> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97) >>>> at >>>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) >>>> at >>>> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215) >>>> at com.sun.proxy.$Proxy127.startVirtualMachine(Unknown Source) >>>> at >>>> org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:169) >>>> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:156) >>>> at >>>> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108) >>>> at >>>> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620) >>>> at >>>> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48) >>>> at >>>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55) >>>> at >>>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102) >>>> at >>>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52) >>>> at >>>> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45) >>>> at >>>> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:568) >>>> at >>>> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) >>>> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) >>>> at >>>> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) >>>> at >>>> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) >>>> at java.base/java.lang.Thread.run(Thread.java:829) >>>> Caused by: com.cloud.exception.InsufficientServerCapacityException: Unable >>>> to create a deployment for VM[User|i-40-76-VM]Scope=interface >>>> com.cloud.dc.DataCenter; id=1 >>>> at >>>> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1119) >>>> at >>>> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5502) >>>> at jdk.internal.reflect.GeneratedMethodAccessor908.invoke(Unknown Source) >>>> ... 17 more >>>> 2022-07-12 09:00:10,694 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] >>>> (API-Job-Executor-29:ctx-870c9fde job-462574) (logid:760cc3b8) Complete >>>> async job-462574, jobStatus: FAILED, resultCode: 530, result: >>>> org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":"530","errortext":"Unable >>>> to start a VM due to insufficient capacity"} >>>> >>>> Can someone help me? >>>> >>>> Best regards, >>>> Olivier -- This message is intended only for the use of the individual or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient, please delete the original message and any copy of it from your computer system. You are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited unless proper authorization has been obtained for such action. If you have received this communication in error, please notify the sender immediately. Although IndiQus attempts to sweep e-mail and attachments for viruses, it does not guarantee that both are virus-free and accepts no liability for any damage sustained as a result of viruses.
