this isnt so relevant to linux VMs as they can take all 8 sockets or cores, whichever way and use them.
The issue is with up to mid level Windows Server licensing only allows the OS to utilise 4 Sockets. The default presentation in your xen VM's is vcores not vsockets, it would make sense to standardise this the same way to kvm, or if not, create an advanced option for defining vsockets vcores and evn vthreads as allowed for by the native kvm (& xen) config parameters.
An example of where this is an issue is any physical bare metal server with more than 4 cores ( ie an 8 core, dual quad server) can happily and legally run all cores in the OS. when virtualised incorrectly, windows only uses half of these cores ( they all apper in device manager but as they are 'vsockets' it ignores anything 4+)
Please sign in to leave a comment.