Hyper-V: enable instance vNUMA
Windows Hyper-V / Server 2012 introduces support for vNUMA topology into Hyper-V virtual machines. This feature improves the performance for VMs configured with large amounts of memory.
Instances will have to be enabled to use vNUMA, by setting the VirtualNumaEnabled flag to True in the Msvm_VirtualSys
A few important notes:
* Host NUMA spanning is enabled by default.
* vNUMA and Dynamic Memory cannot be used at the same time.
For more details, check the source [2].
[1] http://
[2] http://
Blueprint information
- Status:
- Complete
- Approver:
- John Garbutt
- Priority:
- Low
- Drafter:
- Claudiu Belu
- Direction:
- Approved
- Assignee:
- Claudiu Belu
- Definition:
- Approved
- Series goal:
- Accepted for ocata
- Implementation:
-
Implemented
- Milestone target:
-
ocata-3
- Started by
- Claudiu Belu
- Completed by
- Matt Riedemann
Related branches
Related bugs
Sprints
Whiteboard
I think this needs to have a spec created. The configuration of NUMA topology in the guest is only one small part of the NUMA problem. The bigger thing is the host side accounting and scheduling of NUMA resources, and it isn't clear from those MSDN links how this might end up being done for hyperv in Nova. So I'd like see an expanded proposal in a spec for this. -- danpb 22/6/2015
Gerrit topic: https:/
Addressed by: https:/
Adds Hyper-V vNUMA enable spec
Please note this blueprint will delayed until the M release if it is not in the NeedsCodeReview state (with all the code up for review) before July 16th, and merged by July 30th. We expect to re-open master for the M release in September. For more information, please see: https:/
--johnthetubaguy 15th July 2015
Unapproved for liberty due to the Non-Priority Feature Proposal Freeze. --johnthetubaguy 16th July 2015
Gerrit topic: https:/
Addressed by: https:/
Moves the Hyper-V NUMA instance spec to Mitaka
Gerrit topic: https:/
Reappvoed for mitaka --johnthetubaguy 7th October 2015
Pending Patches
==============
As there is no code up for review, removing this blueprint from mitaka, as part of the non-priority Feature Freeze. For more details please see: http://
Gerrit topic: https:/
Addressed by: https:/
Moves the Hyper-V NUMA instance spec to Newton
Addressed by: https:/
Hyper-V: Adds vNUMA implementation
We're past the non-priority feature freeze for Newton. This will have to be re-proposed for Ocata. I'd also recommend getting someone more familiar with NUMA in the libvirt driver, like sfinucan, danpb, cfriesen, etc to look at this when blueprints open up again for review in Ocata. -- mriedem 20160706
Addressed by: https:/
Reproposes the Hyper-V NUMA instance spec to Ocata
Addressed by: https:/
hyper-v: Do not allow instances with pinned CPUs to spawn
