Understood. I only tried the old UI because the instance deployment failed under the new UI and there wasn't a specific error thrown to hint at an issue.
I'll try again today and dig through the logs and come back with findings. MC -----Original Message----- From: Andrija Panic <andrija.pa...@gmail.com> Sent: Thursday, May 20, 2021 5:47 PM To: users <users@cloudstack.apache.org> 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 that is being used/throwing an error here) Get over the old UI, I know there are emotional connections (for me at least) and use just the new UI :) Best, On Thu, 20 May 2021 at 22:57, Corey, Mike <mike.co...@sap.com.invalid> wrote: > 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 what is > defined in the template." > > > > I thought it was the global setting vmware.root.disk.controller – I had it > as osdefault (failed) scsi (failed) and blank (failed) – so I’m not sure > where or what is triggering the error/failure. > > > > Many thanks! > > Mike > > > > > > > > > > *Mike Corey* > > > Technology Senior Consultant, IT CS CTW Operation & Virtualization Service > US > > > *SAP AMERICA, INC.* 3999 West Chester Pike, Newtown Square, 19073 United > States > > > T +1 610 661 0905, M +1 484 274 2658, E mike.co...@sap.com > > > > > > > -- Andrija Panić