RE: Problem with getting SSVM running

2025-08-29 Thread Ian Tobin
gt; > Ian > > > > -Original Message- > From: Wei ZHOU > Sent: 29 August 2025 14:48 > To: users@cloudstack.apache.org > Subject: Re: Problem with getting SSVM running > > Hi, > > Are host and primary storage pool added ? > > > -Wei > > O

Re: Problem with getting SSVM running

2025-08-29 Thread Ron Gage
t: 29 August 2025 14:48 To: users@cloudstack.apache.org Subject: Re: Problem with getting SSVM running Hi, Are host and primary storage pool added ? -Wei On Fri, Aug 29, 2025 at 3:44 PM Ron Gage wrote: Hi all! I'm working with a fresh install of 4.21 on Centos 9. In a nutshell, the

Re: Problem with getting SSVM running

2025-08-29 Thread Ron Gage
Yes sir.  Both are showing green. In fact, the console proxy runs just fine. On 8/29/25 9:47 AM, Wei ZHOU wrote: Hi, Are host and primary storage pool added ? -Wei On Fri, Aug 29, 2025 at 3:44 PM Ron Gage wrote: Hi all! I'm working with a fresh install of 4.21 on Centos 9. In a nutshel

Re: Problem with getting SSVM running

2025-08-29 Thread Wei ZHOU
Hi, Are host and primary storage pool added ? -Wei On Fri, Aug 29, 2025 at 3:44 PM Ron Gage wrote: > Hi all! > > I'm working with a fresh install of 4.21 on Centos 9. In a nutshell, > the SSVM won't start. Error message found in alerts: Secondary Storage > Vm creation failure in zone [Mi-co

RE: Problem with getting SSVM running

2025-08-29 Thread Ian Tobin
Ian -Original Message- From: Wei ZHOU Sent: 29 August 2025 14:48 To: users@cloudstack.apache.org Subject: Re: Problem with getting SSVM running Hi, Are host and primary storage pool added ? -Wei On Fri, Aug 29, 2025 at 3:44 PM Ron Gage wrote: > Hi all! > > I'm working with

Problem with getting SSVM running

2025-08-29 Thread Ron Gage
Hi all! I'm working with a fresh install of 4.21 on Centos 9.  In a nutshell, the SSVM won't start.  Error message found in alerts: Secondary Storage Vm creation failure in zone [Mi-connect]. Error details: Unable to allocate capacity on zone [1] due to [null]. What did I do wrong now? Ron