t;
>>
>>
>>
>>
>> -Original Message-
>> From: Corey, Mike
>> Sent: Wednesday, June 2, 2021 9:28 AM
>> To: users@cloudstack.apache.org
>> Subject: RE: VMware Instance Error
>>
>> I saw that too - but that line re
y, Mike
> Sent: Wednesday, June 2, 2021 9:28 AM
> To: users@cloudstack.apache.org
> Subject: RE: VMware Instance Error
>
> I saw that too - but that line regarding format is "ISO" for other
> deployments.
>
> E
option in the new UI under the template settings pane.
-Original Message-
From: Corey, Mike
Sent: Wednesday, June 2, 2021 9:28 AM
To: users@cloudstack.apache.org
Subject: RE: VMware Instance Error
I saw that too - but that line regarding format is "ISO" for other deployments.
E
ot;ISO","accountId":"0","hvm":"false","bootable":"false","directDownload":"false","deployAsIs":"false"}},"diskSeq":"3","type":"ISO"}],"nics":[{"de
:"ISO","accountId":"0","hvm":"false","bootable":"false"
---
Not sure why id is 0 there and the format is ISO. Are you using an ISO to
deploy the VM?
Regards,
Abhishek
____
From: Andrija Panic
Sent
> custom setting attributes on the templates?
>
> Many thanks!
>
> Mike
>
> -Original Message-
> From: Corey, Mike
> Sent: Tuesday, June 1, 2021 8:47 AM
> To: users@cloudstack.apache.org
> Subject: [CAUTION] RE: VMware Instance Error
>
> Thanks for the
setting attributes on the templates?
Many thanks!
Mike
-Original Message-
From: Corey, Mike
Sent: Tuesday, June 1, 2021 8:47 AM
To: users@cloudstack.apache.org
Subject: [CAUTION] RE: VMware Instance Error
Thanks for the reply Abhishek!
1- ACS deploys the VM from template; however, it fails
ot;,"type":"ROOT","_details":{"storageHost":"usphlcv302.phl.global.corp.sap","managed":"false","storagePort":"2049","volumeSize":"(80.00
GB)
85899345920"}},{"data":{"org.apache.cloudstack.storage.to.TemplateObjectTO&qu
e. Since
these cannot be found in the vm_instance table of ACS it logs them with this
message in DEBUG.
Hope this helps.
Regards,
Abhishek
From: Corey, Mike
Sent: 28 May 2021 20:36
To: users@cloudstack.apache.org
Subject: RE: VMware Instance Error
I'
ilable.
I hope that helps.
Regards,
Jordan
-Original Message-
From: Corey, Mike
Sent: Friday, May 28, 2021 6:07 PM
To: users@cloudstack.apache.org
Subject: RE: VMware Instance Error
[X] This message came from outside your organization
I'll update this email distro in parallel
o find matched VM in CloudStack DB. name:
ffe8ca8a-4c58-4c47-b93d-c524f90453cf
Many thanks for your eyes on this!
Mike
-Original Message-
From: Corey, Mike
Sent: Thursday, May 27, 2021 1:54 PM
To: users@cloudstack.apache.org
Subject: RE: VMware Instance Error
Still having similar issues with the
ids=&nicnetworklist[0].nic=8&nicnetworklist[0].network=62bfbed1-d07c-4886-b4f4-bf594543bb28&name=May27-CentOS-01&displayname=May27-CentOS-01&command=deployVirtualMachine&response=json
Many thanks!
-Original Message-
From: Corey, Mike
Sent: Friday, May 21, 2021 10:59 AM
To: u
mp;affinitygroupids=&nicnetworklist[0].nic=8&nicnetworklist[0].network=62bfbed1-d07c-4886-b4f4-bf594543bb28&name=CV-Test01&displayname=CV-Test01&command=deployVirtualMachine&response=json
-Original Message-
From: Corey, Mike
Sent: Friday, May 21, 2021 7:50 AM
> Sent: Thursday, May 20, 2021 5:47 PM
> To: users
> Subject: Re: VMware Instance Error
>
> Hi Mike,
>
> that is expected in the old UI - at some point, new features were (in UI)
> supported only for the new UI and not in old UI - so this failure is
> expected/fine (
nic
Sent: Thursday, May 20, 2021 5:47 PM
To: users
Subject: Re: VMware Instance Error
Hi Mike,
that is expected in the old UI - at some point, new features were (in UI)
supported only for the new UI and not in old UI - so this failure is
expected/fine (I'm aware of the specific feature tha
Hi Mike,
that is expected in the old UI - at some point, new features were (in UI)
supported only for the new UI and not in old UI - so this failure is
expected/fine (I'm aware of the specific feature that is being
used/throwing an error here)
Get over the old UI, I know there are emotional conne
I'm having a VM instance fail and I can't pinpoint the issue. Maybe someone
has seen this error below - I see it at the legacy UI and not on the new UI.
The new UI just fails the instance after the VM is created in vCenter.
"Boot type and boot mode are not supported on VMware, as we honour wha
17 matches
Mail list logo
