On 2014/9/11 14:27, Michael R. Hines wrote:
On 09/11/2014 02:22 PM, Paolo Bonzini wrote:
Il 11/09/2014 03:57, Michael R. Hines ha scritto:
Why does hotplugging use a different name?
This also affects RDMA live migration - we are explicitly looking up
"pc.ram" ram blocks and pinning them for me
On 09/11/2014 02:22 PM, Paolo Bonzini wrote:
Il 11/09/2014 03:57, Michael R. Hines ha scritto:
Why does hotplugging use a different name?
This also affects RDMA live migration - we are explicitly looking up
"pc.ram" ram blocks and pinning them for memory registration with Linux.
Are we? I can
Il 11/09/2014 03:57, Michael R. Hines ha scritto:
>>
>
> Why does hotplugging use a different name?
>
> This also affects RDMA live migration - we are explicitly looking up
> "pc.ram" ram blocks and pinning them for memory registration with Linux.
Are we? I cannot see any code that special case
On 09/10/2014 05:00 PM, zhanghailiang wrote:
On 2014/9/9 11:05, Alexandre DERUMIER wrote:
Hello,
I was playing with pc-dimm hotplug, and I notice that balloning is
not working on
memory space of pc-dimm devices.
example:
qemu -m size=1024,slots=255,maxmem=15000M
#free -m : 1024M
-> qmp ba
On 2014/9/9 11:05, Alexandre DERUMIER wrote:
Hello,
I was playing with pc-dimm hotplug, and I notice that balloning is not working
on
memory space of pc-dimm devices.
example:
qemu -m size=1024,slots=255,maxmem=15000M
#free -m : 1024M
-> qmp balloon 512M
#free -m : 512M
-> hotplug pc-dimm
Hello,
I was playing with pc-dimm hotplug, and I notice that balloning is not working
on
memory space of pc-dimm devices.
example:
qemu -m size=1024,slots=255,maxmem=15000M
#free -m : 1024M
-> qmp balloon 512M
#free -m : 512M
-> hotplug pc-dimm 1G:
#free -m : 1512M
(This is the same behav
