Is the NUMA feature complete in 3.6? I see it in the UI, but got lost
looking for any documentation or examples.
David
On 02/02/2016 7:40 PM, "Yaniv Dary" <ydary(a)redhat.com> wrote:
Please look at the NUMA feature to enable you to pin a VM to a CPU
group.
Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email: ydary(a)redhat.com
IRC : ydary
On Mon, Feb 1, 2016 at 9:21 AM, David Jorm <djorm(a)iix.net> wrote:
> Hi All
>
> Thanks for the help that people have recently provided on this list.
> I'm running into another edge case that, as far as I can see, does not
> have a native solution within oVirt. I have a use case where every VM
> must have 4 pinned vCPUs, and these must map 1:1 to physical CPUs so
> that there are never two VMs contending for the same physical cores. I
> already have code in place that ensures a VM will not be created or
> started if n/4 VMs are already running on the target host, where n is
> the number of physical cores. What I need now is to ensure that
> pinning is managed so that each physical core maps 1:1 to vCPUs.
>
> Would it be possible to manage the pool of physical cores in a local
> DB, and implement a VDSM hook similar to the example on this page?
>
>
http://www.ovirt.org/VDSM-Hooks
>
> Or would there be a preferable solution?
>
> Thanks
> David
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>