Hi Vivek, The VM did have an ISO attached for the initial install as the goal is to create a template, but I removed it once the install was complete.
I only shut the VM down after the OS had been fully installed. I confirmed that the ISO was not attached both in the CS GUI and vCenter. I could try re-attaching the ISO? Regards, Carlo. > On Jul 28, 2023, at 3:27 AM, Vivek Kumar <vivek.ku...@indiqus.com.invalid> > wrote: > > Do you have ISO attached to this VM ? If yes then can you try to unmount the > ISO from cloudstack GUI and then try to power on ? > > > > 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 28-Jul-2023, at 3:49 PM, Carlo Fernandez <cfernan...@alatar.co> wrote: >> >> Hi Vivek, >> >> Strange. My client shows they’re attached. >> >> I’ve re-attached them. >> >> Thank you again in advance! >> >> Regards, >> >> Carlo. >> >> >> On Jul 28, 2023, at 3:11 AM, Vivek Kumar <vivek.ku...@indiqus.com.invalid >> <mailto:vivek.ku...@indiqus.com.invalid>> wrote: >> >> I don’t see any logs attached to this mail, >> >> >> Vivek Kumar >> Sr. Manager - Cloud & DevOps >> TechOps | Indiqus Technologies >> >> 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/> >> >> >> >> >> >> On 28-Jul-2023, at 1:04 PM, Carlo Fernandez <cfernan...@alatar.co >> <mailto:cfernan...@alatar.co>> wrote: >> >> Hi, >> >> My apologies, forgot to include the logs. >> >> Attached. >> >> Regards, >> >> Carlo Fernandez >> >> From: Carlo Fernandez <cfernan...@alatar.co >> <mailto:cfernan...@alatar.co><mailto:cfernan...@alatar.co>> >> Date: Friday, July 28, 2023 at 12:32 AM >> To: users@cloudstack.apache.org >> <mailto:users@cloudstack.apache.org><mailto:users@cloudstack.apache.org> >> <users@cloudstack.apache.org >> <mailto:users@cloudstack.apache.org><mailto:users@cloudstack.apache.org>> >> Subject: Re: Stopped Instances Can’t Start Back Up >> >> Hi Vivek, >> >> Thanks for your prompt response! >> >> The error the GUI shows is “VM-799f45df-2e11-41ca-b866-445c3e7101ce) Unable >> to start a VM [799f45df-2e11-41ca-b866-445c3e7101ce] due to [Unable to >> create a deployment for VM instance >> {"id":35,"instanceName":"i-2-35-VM","type":"User","uuid":"799f45df-2e11-41ca-b866-445c3e7101ce"}].” >> >> This is exactly what is shown in the logs. vCenter also shows a log saying “ >> Invalid configuration for device '1'.” Which also shows up in the logs. >> >> I am running CloudStack 4.18.0.0 on Ubuntu 22.04 Jammy btw. >> >> I have also attached a document with the snippet of logs that show the error. >> >> Thanks again for your advice and help! >> >> Thanks, >> >> Carlo Fernandez. >> >> From: Vivek Kumar <vivek.ku...@indiqus.com.INVALID >> <mailto:vivek.ku...@indiqus.com.INVALID><mailto:vivek.ku...@indiqus.com.INVALID>> >> Date: Thursday, July 27, 2023 at 11:41 PM >> To: users@cloudstack.apache.org >> <mailto:users@cloudstack.apache.org><mailto:users@cloudstack.apache.org> >> <users@cloudstack.apache.org >> <mailto:users@cloudstack.apache.org><mailto:users@cloudstack.apache.org>> >> Subject: Re: Stopped Instances Can’t Start Back Up >> Hello, >> >> What are you observing in the logs, logs may tell you the exact reason. >> Paste your logs here at the time when you start the instance, then we might >> be able to find the cause. >> >> >> >> 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/> >> <http://www.indiqus.com/><http://www.indiqus.com <http://www.indiqus.com/> >> <http://www.indiqus.com/>> <https://www.indiqus.com/> >> >> >> >> >> On 28-Jul-2023, at 12:07 PM, Carlo Fernandez <cfernan...@alatar.co >> <mailto:cfernan...@alatar.co> <mailto:cfernan...@alatar.co>> wrote: >> >> Hi Guys, >> >> I've deployed CloudStack on a vSphere cluster (2 hosts running 7.0.3, >> vCenter 7.0.3). >> >> I can deploy instances without issues. However, I've thus far been unable to >> start any instance I stop back up. >> >> On vCenter, I can see that once I try to start the instance back up, its >> root hard disk disappears. I can re-attach it manually but trying to start >> it back up from the CS GUI just makes it disappear again. >> >> I have configured both local and remote storage (NFS, TrueNAS) for primary >> storage, and I have remote storage for secondary storage. Both have plenty >> of room for the VM. >> >> Please let me know what kind of logs you will need to provide assistance; >> I'm new to CS so I'm not sure exactly where to go looking. >> >> >> I appreciate your help! >> >> >> Thanks, >> Carlo Fernandez >> >> >> -- >> 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. >> >> >> -- >> 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. >> <CS-log-snippet.txt> > > > -- > 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.
