On 11/14/22 10:56, Anthony PERARD wrote:
On Mon, Nov 14, 2022 at 08:53:17AM -0700, Jim Fehlig wrote:
On 11/14/22 01:18, Jan Beulich wrote:
On 14.11.2022 07:43, Henry Wang wrote:
Sorry, missed Anthony (The toolstack maintainer). Also added him
to this thread.
Indeed there's nothing x86-ish in
On Mon, Nov 14, 2022 at 08:53:17AM -0700, Jim Fehlig wrote:
> On 11/14/22 01:18, Jan Beulich wrote:
> > On 14.11.2022 07:43, Henry Wang wrote:
> > > Sorry, missed Anthony (The toolstack maintainer). Also added him
> > > to this thread.
> >
> > Indeed there's nothing x86-ish in here, it's all about
On 11/14/22 01:18, Jan Beulich wrote:
On 14.11.2022 07:43, Henry Wang wrote:
Sorry, missed Anthony (The toolstack maintainer). Also added him
to this thread.
Indeed there's nothing x86-ish in here, it's all about data representation.
It merely happens to be (for now) x86-specific data which is
Hi Jan,
> -Original Message-
> From: Jan Beulich
> Subject: Re: vnuma_nodes missing pnode 0
>
> On 14.11.2022 07:43, Henry Wang wrote:
> > Sorry, missed Anthony (The toolstack maintainer). Also added him
> > to this thread.
>
> Indeed there's n
On 14.11.2022 07:43, Henry Wang wrote:
> Sorry, missed Anthony (The toolstack maintainer). Also added him
> to this thread.
Indeed there's nothing x86-ish in here, it's all about data representation.
It merely happens to be (for now) x86-specific data which is being dealt
with.
Internally I indic
Sorry, missed Anthony (The toolstack maintainer). Also added him
to this thread.
> (Add x86 maintainers for more visibility)
>
> Hi x86 maintainers,
>
> Since this report might be related with the release, if you have time,
> please have a look. Thank you very much.
>
> Kind regards,
> Henry
(Add x86 maintainers for more visibility)
Hi x86 maintainers,
Since this report might be related with the release, if you have time,
please have a look. Thank you very much.
Kind regards,
Henry
> -Original Message-
> Subject: vnuma_nodes missing pnode 0
>
> Hi All,
>
Hi All,
While fixing [1] a recent downstream libvirt build failure against 4.17 rc3, I
noticed the json representation of libxl_vnode_info omits pnode when value is 0.
The problem can be seen by starting a VM containing the following vnuma config
vnuma = [ [ "pnode=0", "size=2048", "vcpus=0",
