[pve-devel] [PATCH] add numa options

[Alexandre DERUMIER]

>>So migration from a NUMA host to a non-NUMA host always fail?

I think it could work with:

source host numa:

-object memory-backend-ram,size=1024M,policy=bind,host-nodes=0,id=ram-node0
-numa node,nodeid=0,cpus=0,memdev=ram-node0
-object memory-backend-ram,size=1024M,policy=bind,host-nodes=1,id=ram-node1
-numa node,nodeid=1,cpus=1,memdev=ram-node1


target host non numa:

-numa node,nodeid=0 
-numa node,nodeid=1


Like this, we keek the numa exposed inside the guest.



only,
-object memory-backend-ram,size=1024M,policy=bind,host-nodes=1,id=ram-node1: cannot bind memory to host NUMA nodes: Invalid argument

if the host node is not numa

(can be check easily with -d /sys/devices/system/node/node$i/)







----- Mail original ----- 

De: "Dietmar Maurer" <dietmar at proxmox.com> 
À: "Alexandre DERUMIER" <aderumier at odiso.com> 
Cc: pve-devel at pve.proxmox.com 
Envoyé: Mardi 2 Décembre 2014 17:00:51 
Objet: RE: [pve-devel] [PATCH] add numa options 

> >>what happens when you migrate auch VM to a host with different NUMA 
> architecture? 
> 
> If the host have less numa nodes than vmsocket, the qemu process don't start. 
> (I have a check for this in my patch) 
> 
> AFAIK, this is the only restriction. 

So migration from a NUMA host to a non-NUMA host always fail?