From: zhanghailiang <zhang.zhanghailiang@huawei.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: imammedo@redhat.com, qemu-devel@nongnu.org, peter.huangpeng@huawei.com
Subject: Re: [Qemu-devel] [PATCH v2 0/3] fix bug about balloon working incorrectly when hotplug memeory
Date: Mon, 17 Nov 2014 20:25:14 +0800 [thread overview]
Message-ID: <5469E92A.7000405@huawei.com> (raw)
In-Reply-To: <5469D3A4.1010901@huawei.com>
On 2014/11/17 18:53, zhanghailiang wrote:
> On 2014/11/17 18:39, Michael S. Tsirkin wrote:
>> On Mon, Nov 17, 2014 at 01:11:07PM +0800, zhanghailiang wrote:
>>> Hi,
>>>
>>> Patch 1 and 2 mainly fix bug about balloon not working correctly when we do
>>> hotplug memory. It takes 'ram_size' as VM's real RAM size which is wrong
>>> after we hotplug memory.
>>>
>>> This bug exists since we begin to support hotplug memory, and it is better
>>> to fix it.
>>>
>>> Patch 3 add some trace events, it helps debugging balloon. If it is unnecessary,
>>> pls feel free to remove it.
>>>
>>> Thanks,
>>> zhanghailiang
>>
>> What about other users of ram_size?
>> Are they all incorrect?
>>
>
> pc-dimm is only supported in x86 target now, and i am not quite sure if hotplug
> memory will break migration. I'll look into it. Thanks.
>
Hi Michael,
I have made a global search in qemu code, ram_size is used mostly for VM's
startup initialization, I think it's all OK except virtio-balloon and
function vmport_cmd_ram_size (I'm not sure about this place :( ).
But, Unfortunately, hotplug memory action breaks migration. :(
I have made a simple test about this:
Source:
# start VM
# hotplug memory:
object_add memory-backend-ram,id=ram1,size=1024M,host-nodes=0,policy=bind
device_add pc-dimm,id=dimm1,memdev=ram1
# migrate VM to Destination
Destination:
# qemu-system-x86_64: Unknown ramblock "ram1", cannot accept migration
qemu: warning: error while loading state for instance 0x0 of device 'ram'
qemu-system-x86_64: load of migration failed: Invalid argument
*further test*:
hot-add CPU also break migration and reports error in destination:
'Unknown savevm section or instance 'cpu_common' 4
qemu-system-x86_64: load of migration failed: Invalid argument'
I think we should support migration after hotplug memory/CPU action,
what's your opinion? ;)
I will try to fix these two problems.
Thanks,
zhanghailiang
>>> v2:
>>> - fix compiling break for other targets that don't support pc-dimm
>>>
>>> zhanghailiang (3):
>>> pc-dimm: add a function to calculate VM's current RAM size
>>> virtio-balloon: Fix balloon not working correctly when hotplug memory
>>> virtio-balloon: Add some trace events
>>>
>>> hw/mem/pc-dimm.c | 26 ++++++++++++++++++++++++++
>>> hw/virtio/virtio-balloon.c | 21 +++++++++++++++------
>>> include/exec/cpu-common.h | 1 +
>>> stubs/qmp_pc_dimm_device_list.c | 5 +++++
>>> trace-events | 4 ++++
>>> 5 files changed, 51 insertions(+), 6 deletions(-)
>>>
>>> --
>>> 1.7.12.4
>>>
>>
>> .
>>
>
>
>
>
>
next prev parent reply other threads:[~2014-11-17 12:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 5:11 [Qemu-devel] [PATCH v2 0/3] fix bug about balloon working incorrectly when hotplug memeory zhanghailiang
2014-11-17 5:11 ` [Qemu-devel] [PATCH v2 1/3] pc-dimm: add a function to calculate VM's current RAM size zhanghailiang
2014-11-19 9:59 ` Igor Mammedov
2014-11-19 10:32 ` Michael S. Tsirkin
2014-11-19 15:13 ` Luiz Capitulino
2014-11-19 15:52 ` Eric Blake
2014-11-19 16:06 ` Michael S. Tsirkin
2014-11-19 16:31 ` Eric Blake
2014-11-20 2:31 ` zhanghailiang
2014-11-20 9:10 ` Michael S. Tsirkin
2014-11-20 2:33 ` zhanghailiang
2014-11-17 5:11 ` [Qemu-devel] [PATCH v2 2/3] virtio-balloon: Fix balloon not working correctly when hotplug memory zhanghailiang
2014-11-17 5:11 ` [Qemu-devel] [PATCH v2 3/3] virtio-balloon: Add some trace events zhanghailiang
2014-11-17 6:07 ` [Qemu-devel] [PATCH v2 0/3] fix bug about balloon working incorrectly when hotplug memeory Michael S. Tsirkin
2014-11-17 10:39 ` Michael S. Tsirkin
2014-11-17 10:53 ` zhanghailiang
2014-11-17 12:25 ` zhanghailiang [this message]
2014-11-17 12:40 ` Michael S. Tsirkin
2014-11-18 2:50 ` zhanghailiang
2014-11-19 8:28 ` zhanghailiang
2014-11-19 10:06 ` Igor Mammedov
2015-03-03 14:04 ` Luiz Capitulino
2015-03-04 12:55 ` zhanghailiang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5469E92A.7000405@huawei.com \
--to=zhang.zhanghailiang@huawei.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.