It indeed was a non NUMA machine
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1888923
Title:
Configured Memory access latency and bandwidth not taking effect
Status in QEMU:
Invalid
Bug
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1888923
Title:
Configured Memory access latency and bandwidth not taking effect
Status in Q
On Sat, 25 Jul 2020 07:26:38 -
Vishnu Dixit <1888...@bugs.launchpad.net> wrote:
> Public bug reported:
>
> I was trying to configure latencies and bandwidths between nodes in a
> NUMA emulation using QEMU 5.0.0.
>
> Host : Ubuntu 20.04 64 bit
> Guest : Ubuntu 18.04 64 bit
>
> The machine co
I was trying to configure latencies and bandwidths between nodes in a NUMA
emulation using QEMU 5.0.0.
Host: Ubuntu 20.04 64 bit
Guest: Ubuntu 18.04 64 bit
The machine configured has 2 nodes. Each node has 2 CPUs and has been
allocated 3GB of memory. The memory access latencies and bandwidths
member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1888923
Title:
Configured Memory access latency and bandwidth not taking effect
Status in QEMU:
New
Bug description:
I was trying to configure latencies and bandwidths between nodes in a
NUMA emulation using