Hi list,
The current status is that though they look the same, CPU topology for hosts
and VMs differ.
In both you have
topology cores=N sockets=Y/
for hosts: Cores = Total cores on the host, Y=number of sockets
for VMs: Cores = Cores per socket, Y=number of sockets
This means that
On 04/30/2012 02:37 PM, Simon Grinberg wrote:
Hi list,
The current status is that though they look the same, CPU topology for hosts
and VMs differ.
In both you have
topology cores=N sockets=Y/
for hosts: Cores = Total cores on the host, Y=number of sockets
for VMs: Cores = Cores per
On 04/30/2012 02:43 PM, Dor Laor wrote:
I would go for 4 or 2
Current CPU topology for the hosts is a new commit, thus it may be
allowed to change it now since no one is using it yet. This works in
favour of 2. In any case only 3 discloses all the information in all
possible cases.
Thoughts?
On 04/30/2012 05:19 PM, Geert Jansen wrote:
If you touch any of this, please be prepared for the future:
- Use hyperthreads (exists in kvm today)
- Add numa topology for guest and the hosts
- Add Cache info (for VMs too)
- Add number of DIMMs, especially for VMs, for the upcoming memory hot
On 04/30/2012 05:19 PM, Geert Jansen wrote:
On 04/30/2012 02:43 PM, Dor Laor wrote:
I would go for 4 or 2
Current CPU topology for the hosts is a new commit, thus it may be
allowed to change it now since no one is using it yet. This works in
favour of 2. In any case only 3 discloses all the
