Currently out of the box (binaries) Azure Stack TP2 won’t install on anything less than 12 Cores on the host server be it physical or Virtual, (Yes you can install Azure Stack in Nested Virtualization to get around the Physical Disk allocation issue, but be aware there is a Blue Screen Bug when running it so not advised.)
If you’re like me and can’t get your hands on shining new kit for a lab/testing environment and need to make do with DL380 G6’s which have 8 cores and a truck load of RAM and the required number of disk which worked fast enough for Azure Stack TP1 it doesn’t work out of the box for Azure Stack TP2, so below is the process we worked out to allow for the installation of Azure Stack TP2 on under speced system.
So you have already found the config.xml file located in c:\CloudDeployment which looks something like below, and you have already done a search on the file and found the MinimumNumberOfCoresPerMachine value and updated it to the number of cores which you have, from here you reran the PowerShell command and it failed. The next step was to search the internet and find this blog.
So now to find the real config file which is used to install the bare metal(host machine) for Azure Stack, this is located here: C:\CloudDeployment\Configuration\Roles\Infrastructure\BareMetal\OneNodeRole.xml easy right, we make the change to the MinimumNumberOfCoresPerMachine again save the file then rerun the PowerShell Command and it fails again… now this is getting annoying.
After some digging we find that during the installation of Azure Stack it creates a group of encrypted files which are located here: C:\EceStore these contain an encrypted version of the Config file from the first time you ran the PowerShell script, So we will delete this folder, and the config.xml file from C:\CloudDeployment and rerun the whole process from the start. Presto the installation process will complete this time around.