Hi,
Any update?
Thanks,
Zhang Haoyu
On 2016/8/30 12:11, Lai Jiangshan wrote:
> On Wed, Aug 10, 2016 at 5:03 PM, Juan Quintela wrote:
>> Lai Jiangshan wrote:
>>
>> Hi
>>
>> First of all, I like a lot the patchset, but I would preffer to split it
>> to find "possible" bugs along the lines, espec
On 01/12/2017 08:44 PM, Lai Jiangshan wrote:
> On Fri, Jan 13, 2017 at 3:19 AM, Jianjun Duan
> wrote:
>> I have a question related to interplay of bypassing the shared memory in
>> migration and memory hotplugging. If on the source guest a big chunk of
>> memory is plugged in, will the shared m
On Fri, Jan 13, 2017 at 3:19 AM, Jianjun Duan wrote:
> I have a question related to interplay of bypassing the shared memory in
> migration and memory hotplugging. If on the source guest a big chunk of
> memory is plugged in, will the shared memory still be mapped the same
> way on the guest? i.e,
I have a question related to interplay of bypassing the shared memory in
migration and memory hotplugging. If on the source guest a big chunk of
memory is plugged in, will the shared memory still be mapped the same
way on the guest? i.e, the mapping from guest physical address to the
host virtual a
Juan,
It looks like Lai is waiting for a reply from you on this email :).
Alex
On 08/30/2016 06:11 AM, Lai Jiangshan wrote:
On Wed, Aug 10, 2016 at 5:03 PM, Juan Quintela wrote:
Lai Jiangshan wrote:
Hi
First of all, I like a lot the patchset, but I would preffer to split it
to find "poss
On Wed, Aug 10, 2016 at 5:03 PM, Juan Quintela wrote:
> Lai Jiangshan wrote:
>
> Hi
>
> First of all, I like a lot the patchset, but I would preffer to split it
> to find "possible" bugs along the lines, especially in postcopy, but not only.
Hello, thanks for review and comments
I tried to make
Lai Jiangshan wrote:
Hi
First of all, I like a lot the patchset, but I would preffer to split it
to find "possible" bugs along the lines, especially in postcopy, but not only.
[very nice description of the patch]
Nothing to say about the QMP and shared memory detection, looks correct
to me.
>
On Wed, Aug 10, 2016 at 3:12 AM, Dr. David Alan Gilbert
wrote:
> * Lai Jiangshan (jiangshan...@gmail.com) wrote:
>> The feature vm-template makes the containers(VMs) can
>> be started in 130ms and save 80M memory for every
>> container(VM). So that the hyper containers are fast
>> and high-density
* Lai Jiangshan (jiangshan...@gmail.com) wrote:
> When the migration capability 'bypass-shared-memory'
> is set, the shared memory will be bypassed when migration.
>
> It is the key feature to enable several excellent features for
> the qemu, such as qemu-local-migration, qemu-live-update,
> extre
Hi,
Your series seems to have some coding style problems. See output below for
more information:
Message-id: 1470744604-80857-1-git-send-email-jiangshan...@gmail.com
Type: series
Subject: [Qemu-devel] [PATCH] add migration capability to bypass the shared
memory
=== TEST SCRIPT BEGIN ===
#!/bin
When the migration capability 'bypass-shared-memory'
is set, the shared memory will be bypassed when migration.
It is the key feature to enable several excellent features for
the qemu, such as qemu-local-migration, qemu-live-update,
extremely-fast-save-restore, vm-template, vm-fast-live-clone,
yet
11 matches
Mail list logo
