No Hyper-V guest OS is created equal.
So, when it comes to utilizing 1, 2, 3, or 4 virtual CPUs (vCPU), we need to be aware of what the guest OS can support natively whether it will support the installation of Integration Services.
As we have already noted, the ShadowProtect Recovery Environment will run very poorly with more than 1 vCPU assigned (previous blog post) to the VM. Once the VM is restored though, that setting can be changed. We also need to be aware of what the restored OS could support for vCPUs.
We get the following grid which will be partially hidden. It can be clicked on to reveal the full screenshot:
Here we have the grid for desktop OSs:
The final, and quite large, grid has to do with Integration Services and virtual device driver support in each of the OSs:
The above is a partial of the grid.
The reason we were looking into this in the first place was because we are standing up an Evaluation copy of SBS 2000 to look into something. We needed to confirm how many vCPUs the OS could handle.
We already knew that SP4 was required to get Integration Services to install though.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book