Re: [Qemu-devel] Live migration + cpu/mem hotplug

2017-01-10 Thread Igor Mammedov
On Tue, 10 Jan 2017 14:28:19 +0800 Bob Chen wrote: > Answer my own question: > > The corresponding cmd-line parameter for memory hot-add by QEMU monitor is, > -object memory-backend-ram,id=mem0,size=1024M -device > pc-dimm,id=dimm0,memdev=mem0 pc-dimm should have additional property -device pc

Re: [Qemu-devel] Live migration + cpu/mem hotplug

2017-01-09 Thread Bob Chen
Answer my own question: The corresponding cmd-line parameter for memory hot-add by QEMU monitor is, -object memory-backend-ram,id=mem0,size=1024M -device pc-dimm,id=dimm0,memdev=mem0 2017-01-05 18:12 GMT+08:00 Daniel P. Berrange : > On Thu, Jan 05, 2017 at 04:27:26PM +0800, Bob Chen wrote: > > H

Re: [Qemu-devel] Live migration + cpu/mem hotplug

2017-01-05 Thread Daniel P. Berrange
On Thu, Jan 05, 2017 at 04:27:26PM +0800, Bob Chen wrote: > Hi, > > According to the docs, the destination Qemu must have the exactly same > parameters as the source one. So if the source has just finished cpu or > memory hotplug, what would the dest's parameters be like? > > Does DIMM device, or

[Qemu-devel] Live migration + cpu/mem hotplug

2017-01-05 Thread Bob Chen
Hi, According to the docs, the destination Qemu must have the exactly same parameters as the source one. So if the source has just finished cpu or memory hotplug, what would the dest's parameters be like? Does DIMM device, or logically QOM object, have to be reflected on the new command-line para