Re: Stopped Instances Can’t Start Back Up

[Carlo Fernandez]

Gents,

Re-attaching the install ISO solves the issue.

Is this expected behaviour?

Regards,

Carlo.

> On Jul 28, 2023, at 1:58 PM, Carlo Fernandez  wrote:
> 
> Hello,
> 
> I’ve figured out that the disk for the VM that won’t start is named ROOT-37 
> on CloudStack, but it is definitely not named that in vCenter.
> 
> I spun up a VM using the built-in CentOS template, and the root disk was 
> indeed named ROOT-36 on both CloudStack and vCenter. I can stop and start 
> that instance without any issues.
> 
> Furthermore, I notice that when I shut down the VM that won’t start, its 
> network adapter and disk are removed. I also notice that there is an ISO 
> attached to the VM on vCenter, but the attached ISO is NOT the install ISO 
> for the OS.
> 
> If I remove this ISO, and manually re-attach the disk and NIC, the VM will 
> boot back into the OS without issues, and CloudStack will see this and update 
> the VM’s status accordingly. The VNC console continues to work after manually 
> reconfiguring and restarting the VM.
> 
> My guess is that the VM can’t start after being shut down via the CS GUI 
> because when it wants to find the disk again, it can’t find it as it is not 
> named as CS would have expected it to be. This is the conclusion I’ve come to 
> after testing.
> 
> Does anybody have any other guesses/advice? I’ve no idea why vCenter is not 
> naming the disk properly, or if it should even matter. Either way, CloudStack 
> is kind of unusable in this state.
> 
> As I am completely green to CS and the documentation/forums have not provided 
> any clues, I’ve got no idea where to start looking to resolve this issue. Any 
> help or advice would be highly appreciated!
> 
> Regards,
> 
> Carlo Fernandez.
> 
> From: Carlo Fernandez 
> Date: Friday, July 28, 2023 at 3:33 AM
> To: users@cloudstack.apache.org 
> Subject: Re: Stopped Instances Can’t Start Back Up
> 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  
>> 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 
>>   www.indiqus.com 
>> 
>> 
>> 
>> 
 On 28-Jul-2023, at 3:49 PM, Carlo Fernandez  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 >>> > wrote:
>>> 
>>> I don’t see any logs attached to this mail,
>>> 
>>> 
>>> Vivek Kumar
>>> Sr. Manager - Cloud & DevOps
>>> TechOps | Indiqus Technologies
>>> 
>>> vivek.ku...@indiqus.com  
>>> 
>>>  www.indiqus.com  
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
 On 28-Jul-2023, at 1:04 PM, Carlo Fernandez >>> > wrote:
>>> 
>>> Hi,
>>> 
>>> My apologies, forgot to include the logs.
>>> 
>>> Attached.
>>> 
>>> Regards,
>>> 
>>> Carlo Fernandez
>>> 
>>> From: Carlo Fernandez >> >>
>>> Date: Friday, July 28, 2023 at 12:32 AM
>>> To: 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!
>>>

Re: Stopped Instances Can’t Start Back Up

[Carlo Fernandez]

Hello,

I’ve figured out that the disk for the VM that won’t start is named ROOT-37 on 
CloudStack, but it is definitely not named that in vCenter.

I spun up a VM using the built-in CentOS template, and the root disk was indeed 
named ROOT-36 on both CloudStack and vCenter. I can stop and start that 
instance without any issues.

Furthermore, I notice that when I shut down the VM that won’t start, its 
network adapter and disk are removed. I also notice that there is an ISO 
attached to the VM on vCenter, but the attached ISO is NOT the install ISO for 
the OS.

If I remove this ISO, and manually re-attach the disk and NIC, the VM will boot 
back into the OS without issues, and CloudStack will see this and update the 
VM’s status accordingly. The VNC console continues to work after manually 
reconfiguring and restarting the VM.

My guess is that the VM can’t start after being shut down via the CS GUI 
because when it wants to find the disk again, it can’t find it as it is not 
named as CS would have expected it to be. This is the conclusion I’ve come to 
after testing.

Does anybody have any other guesses/advice? I’ve no idea why vCenter is not 
naming the disk properly, or if it should even matter. Either way, CloudStack 
is kind of unusable in this state.

As I am completely green to CS and the documentation/forums have not provided 
any clues, I’ve got no idea where to start looking to resolve this issue. Any 
help or advice would be highly appreciated!

Regards,

Carlo Fernandez.

From: Carlo Fernandez 
Date: Friday, July 28, 2023 at 3:33 AM
To: users@cloudstack.apache.org 
Subject: Re: Stopped Instances Can’t Start Back Up
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  
> 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 
>www.indiqus.com 
>
>
>
>
>> On 28-Jul-2023, at 3:49 PM, Carlo Fernandez  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 > > wrote:
>>
>> I don’t see any logs attached to this mail,
>>
>>
>> Vivek Kumar
>> Sr. Manager - Cloud & DevOps
>> TechOps | Indiqus Technologies
>>
>> vivek.ku...@indiqus.com  
>> 
>>   www.indiqus.com  
>> 
>>
>>
>>
>>
>>
>> On 28-Jul-2023, at 1:04 PM, Carlo Fernandez > > wrote:
>>
>> Hi,
>>
>> My apologies, forgot to include the logs.
>>
>> Attached.
>>
>> Regards,
>>
>> Carlo Fernandez
>>
>> From: Carlo Fernandez > >>
>> Date: Friday, July 28, 2023 at 12:32 AM
>> To: 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 > >>
>> Date: Thursday, July 27, 2023 at 11:41 PM
>> To: users@cloudstack.apache.org 
>> 

Re: CloudStack 14.18.0 Can't mount cpvm secondary storage

[Mindaugas Milinavičius]

Thank you!

On Fri, Jul 28, 2023 at 6:49 AM Jithin Raju 
wrote:

> Hi Mindaugas,
>
> CPVM doesn’t require access to secondary storage. You can avoid running
> the script ‘ssvm-check.sh’ on CPVM.
>
> -Jithin
>
> From: Mindaugas Milinavičius 
> Date: Friday, 28 July 2023 at 12:27 AM
> To: users@cloudstack.apache.org 
> Subject: CloudStack 14.18.0 Can't mount cpvm secondary storage
> Hello everyone,
>
> with ssvm - without any problem, all working good, with cpvm - can't mount
> nfs secondary storage.
>
> I tried mount manually - without problem. ping going.
>
> Anyone have this problem?
>
>
>
> root@s-8-VM:/usr/local/cloud/systemvm# ./ssvm-check.sh
> 
> First DNS server is  1.1.1.1
> PING 1.1.1.1 (1.1.1.1): 56 data bytes
> 64 bytes from 1.1.1.1: icmp_seq=0 ttl=60 time=0.933 ms
> 64 bytes from 1.1.1.1: icmp_seq=1 ttl=60 time=1.004 ms
> --- 1.1.1.1 ping statistics ---
> 2 packets transmitted, 2 packets received, 0% packet loss
> round-trip min/avg/max/stddev = 0.933/0.969/1.004/0.036 ms
> Good: Can ping DNS server
> 
> Good: DNS resolves cloudstack.apache.org
> 
> nfs is currently mounted
> Mount point is /mnt/SecStorage/a8305a6a-a24a-3d7b-875a-584b6157a348
> Good: Can write to mount point
> 
> Management server is 185.*,10.0.11.31. Checking connectivity.
> Good: Can connect to management server 185.* port 8250
> Good: Can connect to management server 10.0.11.31 port 8250
> 
> Good: Java process is running
> 
> Tests Complete. Look for ERROR or WARNING above.
> root@s-8-VM:/usr/local/cloud/systemvm#
>
>
>
>
>
> root@v-10-VM:/usr/local/cloud/systemvm# ./ssvm-check.sh
> 
> First DNS server is  1.1.1.1
> PING 1.1.1.1 (1.1.1.1): 56 data bytes
> 64 bytes from 1.1.1.1: icmp_seq=0 ttl=60 time=1.063 ms
> 64 bytes from 1.1.1.1: icmp_seq=1 ttl=60 time=0.936 ms
> --- 1.1.1.1 ping statistics ---
> 2 packets transmitted, 2 packets received, 0% packet loss
> round-trip min/avg/max/stddev = 0.936/1.000/1.063/0.064 ms
> Good: Can ping DNS server
> 
> Good: DNS resolves cloudstack.apache.org
> 
> ERROR: Storage nfs is not currently mounted
> Verifying if we can at least ping the storage
> Storage address is empty, trying to ping storage network gateway instead ()
> ping: missing host operand
> Try 'ping --help' or 'ping --usage' for more information.
> WARNING: Cannot ping nfs storage network gateway
> routing table follows
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric RefUse
> Iface
> 0.0.0.0 185.* 0.0.0.0 UG0  00 eth2
> 1.1.1.1 10.0.11.254 255.255.255.255 UGH   0  00
> eth1
> 10.0.0.010.0.11.254 255.0.0.0   UG0  00
> eth1
> 10.0.11.0   0.0.0.0 255.255.255.0   U 0  00
> eth1
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0  00
> eth0
> 172.16.0.0  10.0.11.254 255.240.0.0 UG0  00
> eth1
> 185.*   0.0.0.0 255.255.255.0   U 0  00 eth2
> 185.* 10.0.11.254 255.255.255.255 UGH   0  00 eth1
> 192.168.0.0 10.0.11.254 255.255.0.0 UG0  00
> eth1
> 
> Management server is 185.*,10.0.11.31. Checking connectivity.
> Good: Can connect to management server 185.* port 8250
> Good: Can connect to management server 10.0.11.31 port 8250
> 
> Good: Java process is running
> 
> Tests Complete. Look for ERROR or WARNING above.
> root@v-10-VM:/usr/local/cloud/systemvm#
>
>
>
>

Re: OFFICIAL ANNOUNCEMENT: CloudStack Collaboration Conference 2023 CFP and Registration Now Open!

[Wido den Hollander]

Hi,

Op 24-07-2023 om 08:53 schreef Ivet Petrova:

Hi All,

- As Gregoire has mentioned, the hotel recently rebranded - maybe the new site 
was launched 2-3 weeks ago. So the name of the hotel now is 
https://www.ihg.com/voco/hotels/us/en/clichy/parpc/hoteldetail
It is renovated and rebranded, but location is the same.


I see! The link now seems to be fine.


However, on CloudStackcollab.org the link is partially broken.

"CCC 2023 will be taking place in the Holiday Inn/VOCO Paris, Porte de 
Clichy. "


This link points to: 
"https://www.ihg.com/voco/hotels/gb/en/clichy/parpc/hoteldetailhttps://www.ihg.com/voco/hotels/gb/en/clichy/parpc/hoteldetail";


Double the URL concatted.



- I have sent an email last week to the hotel to ask for some pricing/special 
offer for our conference members. Will keep you posted as soon as I have 
details.

- Good remark for the project website. I thought we posted there, will add the 
info today.


I see it now! Shouldn't this link to https://www.cloudstackcollab.org/ ?

Because right now it goes to Hubilo directly and there isn't much 
information there.




- We will add the train info also to the website official info for travelling 
we plan to post. Megali from DIMSI’s team is helping us on these details.



Great! And indeed, from London you can very easily reach Paris via 
Eurostar. I just booked my Thalys train tickets :-)


Wido


Kind regards,


  


On 23 Jul 2023, at 20:27, Gregoire LAMODIERE 
mailto:g.lamodi...@dimsi.fr>> wrote:

Hi Wido,

Thanks for your message.
You are right, UK / EU people should consider coming to Paris by train.
The hotel is well connected to subways lines 13 and 14, and we (DIMSI) can help 
anyone to find best way to come.

About the hotel, you are right, it's been rebranded last month, and I guess 
they forgot to make a redirection from old website (HolidayInn) to new one 
(vocco).
I stayed there once since the change, and result is good, with a nice rhum bar for 
"change the world" late conversations.

As local player, we (still DIMSI team) will be happy to arrange a beer / diner 
session.
Maybe we can discuss this @Ivet Petrova and @Jamie Pell ?

Btw, very happy to welcome the community in France next november !



Gregoire LAMODIERE
Co-fondateur & Solution architect
-Message d'origine-
De : Wido den Hollander mailto:w...@widodh.nl>>
Envoyé : vendredi 21 juillet 2023 20:18
À : users@cloudstack.apache.org; Jamie Pell 
mailto:jamie.p...@shapeblue.com>>; 
market...@cloudstack.apache.org; 
d...@cloudstack.apache.org
Objet : Re: OFFICIAL ANNOUNCEMENT: CloudStack Collaboration Conference 2023 CFP 
and Registration Now Open!

Hi Ivet,

Thanks for organizing this! I was just sharing this internally with our 
colleagues throughout Europe and I noticed that the link to the hotel is 
broken. The correct URL is:
https://www.ihg.com/voco/hotels/gb/en/clichy/parpc/hoteldetail

A few things in addition:

- Is there a deal with the hotel for a fixed price for rooms?
- I don't see this event mentioned at the CloudStack main website
- Do we have anybody local who can help with finding bars for drinks?

I'd also like to make a recommendation to everybody from Europe to consider 
coming by train instead of flying. Paris is very well connected from Brussels 
(BE), Aachen (DE), Cologne (DE) and Amsterdam (NL) and ofcourse other cities in 
Paris.

'Gare du Nord' and 'Gare de Lyon' are two major train stations where high speed 
trains terminate.

Check out Google Maps or Thalys/TGV to see if coming by train makes sense. I'll 
be doing that for sure and will make sure all my other colleagues come by train 
as well.

https://en.wikipedia.org/wiki/High-speed_rail_in_Europe

See you in Paris in November!

Wido

Op 31/05/2023 om 10:48 schreef Jamie Pell:
Hi everyone,

I am pleased to share that the CloudStack Collaboration Conference 2023 
registration and call for presentations is now open! Once again, this year’s 
event will be a hybrid one, allowing community members who are not able to 
attend in-person, to join virtually.

Register for
CCC

Submit a
Talk

This year’s event will be taking place in the Holiday Inn 
Paris on 
November 23-24th.

If your company is interested in supporting the event by becoming a
sponsor, you can read the sponsorship
prospectus.

For further information regarding the event, visit the official event
website.

Kind regards,

Re: Stopped Instances Can’t Start Back Up

[Carlo Fernandez]

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  
> 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 
>www.indiqus.com 
> 
> 
> 
> 
>> On 28-Jul-2023, at 3:49 PM, Carlo Fernandez  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 > > wrote:
>> 
>> I don’t see any logs attached to this mail, 
>> 
>> 
>> Vivek Kumar
>> Sr. Manager - Cloud & DevOps
>> TechOps | Indiqus Technologies
>> 
>> vivek.ku...@indiqus.com  
>> 
>>   www.indiqus.com  
>> 
>> 
>> 
>> 
>> 
>> On 28-Jul-2023, at 1:04 PM, Carlo Fernandez > > wrote:
>> 
>> Hi,
>> 
>> My apologies, forgot to include the logs.
>> 
>> Attached.
>> 
>> Regards,
>> 
>> Carlo Fernandez
>> 
>> From: Carlo Fernandez > >
>> Date: Friday, July 28, 2023 at 12:32 AM
>> To: 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 > >
>> Date: Thursday, July 27, 2023 at 11:41 PM
>> To: 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  
>>  
>>   www.indiqus.com  
>>  
>> > 
>> 
>> 
>> 
>> 
>> On 28-Jul-2023, at 12:07 PM, Carlo Fernandez >  > 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 me

Re: Stopped Instances Can’t Start Back Up

[Vivek Kumar]

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 
www.indiqus.com 




> On 28-Jul-2023, at 3:49 PM, Carlo Fernandez  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  > wrote:
> 
> I don’t see any logs attached to this mail, 
> 
> 
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> TechOps | Indiqus Technologies
> 
> vivek.ku...@indiqus.com  
> 
>www.indiqus.com  
> 
> 
> 
> 
> 
> On 28-Jul-2023, at 1:04 PM, Carlo Fernandez  > wrote:
>  
> Hi,
>  
> My apologies, forgot to include the logs.
>  
> Attached.
>  
> Regards,
>  
> Carlo Fernandez
>  
> From: Carlo Fernandez  >
> Date: Friday, July 28, 2023 at 12:32 AM
> To: 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  >
> Date: Thursday, July 27, 2023 at 11:41 PM
> To: 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  
>  
>www.indiqus.com  
>  
> > 
>  
>  
>  
>  
> On 28-Jul-2023, at 12:07 PM, Carlo Fernandez   > 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.
>

Re: Stopped Instances Can’t Start Back Up

[Vivek Kumar]

I don’t see any logs attached to this mail, 


Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies

vivek.ku...@indiqus.com 
www.indiqus.com 




> On 28-Jul-2023, at 1:04 PM, Carlo Fernandez  wrote:
> 
> Hi,
>  
> My apologies, forgot to include the logs.
>  
> Attached.
>  
> Regards,
>  
> Carlo Fernandez
>  
> From: Carlo Fernandez mailto:cfernan...@alatar.co>>
> Date: Friday, July 28, 2023 at 12:32 AM
> To: 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  >
> Date: Thursday, July 27, 2023 at 11:41 PM
> To: 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  
> 
> www.indiqus.com  > 
> 
> 
> 
> 
> > On 28-Jul-2023, at 12:07 PM, Carlo Fernandez  > > 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.

Re: Stopped Instances Can’t Start Back Up

[Carlo Fernandez]

Hi,

My apologies, forgot to include the logs.

Attached.

Regards,

Carlo Fernandez

From: Carlo Fernandez 
Date: Friday, July 28, 2023 at 12:32 AM
To: 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 
Date: Thursday, July 27, 2023 at 11:41 PM
To: 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 
www.indiqus.com 




> On 28-Jul-2023, at 12:07 PM, Carlo Fernandez  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.

Re: Stopped Instances Can’t Start Back Up

[Carlo Fernandez]

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 
Date: Thursday, July 27, 2023 at 11:41 PM
To: 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 
www.indiqus.com 




> On 28-Jul-2023, at 12:07 PM, Carlo Fernandez  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.