Why would you hardcode the addition of unrequired/unnecessary "hardware" to the VM instance? This wasn't the case for the CentOS deployment so why do it with Windows OS?
I can't say for certain, but the VM instance that ACS creates doesn't start the OS (blue screen recovery console). However, cloning from the template ACS creates in vCenter through the tradition vCenter method, the VM loads as normal. Can this be changed via a global setting or other config file edit? -----Original Message----- From: Andrija Panic <andrija.pa...@gmail.com> Sent: Saturday, July 25, 2020 2:44 PM To: users <users@cloudstack.apache.org> Subject: Re: Windows Template & Multiple SCSI Controllers Hardcoded behavior of having 4 identical controllers, with all the volumes attached to the first one. Why is this a problem for you? Best, On Fri, 24 Jul 2020, 19:55 Corey, Mike, <mike.co...@sap.com> wrote: > Hi, > > > > As I progress with my ACS & VMware setup I seem to hit a bump at every > turn. I’ve gotten to the point where I’m now able to upload a Windows 10 > template that we use in production (VMware) into ACS. However, when I > create a new instance through the GUI it is deployed with a total of 4 SCSI > controllers when it should only have ONE. > > > > What is strange is that the clone of the template that ACS copies into > vCenter only has a single SCSI controller (as expected). In fact, when I > clone a VM (traditional vCenter method) from the ACS template that was > create – that VM only has the single controller and boots to the OS fine. > > > > Any ideas are welcome as to why this behavior is occurring. > > > > 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 > > > > > > >
