I should have enough resources. The AMD Phenom II X3 720 cpu was the OLD processor. When that processor was installed, I could assign multiple CPUs to the VM and Windows 10 would see them all. The NEW processor is an upgrade to an AMD FX-8370 which is 8 core. However, with the new CPU with 8 cores, I cannot assign more than 1 CPU to the VM without Windows throwing the error fit.
So to get this right, your using FreeNAS to host a Win10 VM?
Then you "should" be able to use up to 16 "cores".
Maybe you can find an answer here: 16. Virtual Machines — FreeNAS(R)11.2-U3 User Guide Table of Contents 16. Virtual Machines — FreeNAS(R)11.2-U3 User Guide Table of ContentsVirtual CPUs integer Number of virtual CPUs to allocate to the VM. The maximum is 16 unless limited by the host CPU. The VM operating system might also have operational or licensing restrictions on the number of CPUs.
For the newest stable version:17. Virtual Machines — FreeNAS(R)11.3-U2 User Guide Table of Contents
But that won't solve the problem of Windows 10 complaining about "multiple processor configuration not supported". As soon as I change the number of virtual CPUs to 2, Windows won't boot with that error. Linux Mint is perfectly happy to run with 2 or more virtual CPUs.
Hi,
Interesting 10 won't run on 2 core
I have to admit it wouldn't be pretty I used 10 on a dual core and it was terrible nothing left for the user most the time when 10 gets to doing it's thing checking for updates/ scanning/ loading usage/....
Finally had to go back to win-7 on that poor little low spec's dual core.
Hi there
@ThrashZone
I think Windows has a restriction on the number of processors one can use (i.e number of physical CPU's) but I'm sure number of cores and number of threads is only dependent on the number of cores in a physical processor.
For Home and Pro it's 2 physical processors, for Workstations and enterprise it's 4 and for server I'm not sure but > 4 supported.
Don't get "mixed" between the number of cores and the number of processors -- however if the virtual machine software thinks number of cores = number of processors or the hardware "confuses" the software then you might run up against the limit.
Using 2X physical XEON processors I can run up to 4 cores with Windows for Workstations on Vmware -- after that it breaks so there's something in the VMWare software that must muddle it up. The VMware software seems to think 4 cores per processor = 8 Cores and the wretched VM won't boot !!!!!! whereas it works assigning 1 pysical CPU as a vCPU and 4 cores which rather cuts down the resources I want to give the VM.
I don't use VMWare any more these days but dealing with Virtual Machines at the physical hardware level isn't an easy task.
Any good gurus out there
would appreciate a definitive answer on this one.
Cheers
jimbo
As you are not using Hyper-V, this will not be helping you at all, but at least it explains a little about virtual processors, and how number of them affects virtual machines: Hyper-V - Optimizing Virtual Machines
See Part Three in that tut. Steps 3.1are Hyper-V specific, but steps 3.3 through 3.6 are more generic.
Kari
Quote
