On Wed, Apr 03, 2019 at 01:48:33PM -0400, Cole Robinson wrote:
> On 3/26/19 4:06 PM, Allen, John wrote:
> > For pinned vcpus, vcpupin will report inaccurate affinity values on machines
> > with high core counts (256 cores in my case). The problem is produced as
> > follows:
> >
> > $ virsh
On 3/26/19 4:06 PM, Allen, John wrote:
> For pinned vcpus, vcpupin will report inaccurate affinity values on machines
> with high core counts (256 cores in my case). The problem is produced as
> follows:
>
> $ virsh vcpupin myguest 0 4
>
> $ virsh vcpupin myguest 0
>
> VCPU CPU Affinity
>
On Fri, Mar 29, 2019 at 01:36:02PM +, Allen, John wrote:
Sent this out to the list a few days ago, but never saw it appear on the
archives. Resending--hopefully this makes it to the list.
---
For pinned vcpus, vcpupin will report inaccurate affinity values on machines
with high core counts
Sent this out to the list a few days ago, but never saw it appear on the
archives. Resending--hopefully this makes it to the list.
---
For pinned vcpus, vcpupin will report inaccurate affinity values on machines
with high core counts (256 cores in my case). The problem is produced as
follows:
$
For pinned vcpus, vcpupin will report inaccurate affinity values on machines
with high core counts (256 cores in my case). The problem is produced as
follows:
$ virsh vcpupin myguest 0 4
$ virsh vcpupin myguest 0
VCPU CPU Affinity
---
0 4,192,194,196-197
