On 04/03/2015 05:20 PM, zhanghailiang wrote:
> On 2015/4/3 16:51, Jason Wang wrote:
>>
>>
>> On 04/02/2015 07:52 PM, zhanghailiang wrote:
>>> On 2015/4/1 3:06, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
> On 2015/3/30 15:59, Dr. David Alan Gilbe
On 03/04/2015 03:29, Wen Congyang wrote:
>> > At this point the iovec has been destroyed.
>> >
>> > It's clearer, I think, to just use req->size in
>> > virtio_blk_complete_request (as you suggest in the comment below!). For
>> > dataplane you'll need to do the same in complete_request_vring.
>
On 2015/4/3 16:51, Jason Wang wrote:
On 04/02/2015 07:52 PM, zhanghailiang wrote:
On 2015/4/1 3:06, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
On 2015/3/30 15:59, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
On 04/03/2015 04:51 PM, Jason Wang wrote:
>
>
> On 04/02/2015 07:52 PM, zhanghailiang wrote:
>> On 2015/4/1 3:06, Dr. David Alan Gilbert wrote:
>>> * zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
On 2015/3/30 15:59, Dr. David Alan Gilbert wrote:
> * zhanghailiang (zhang.zhanghail
On 04/02/2015 07:52 PM, zhanghailiang wrote:
> On 2015/4/1 3:06, Dr. David Alan Gilbert wrote:
>> * zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
>>> On 2015/3/30 15:59, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
> On 2015/3/27 18:18, Dr
On 04/02/2015 09:17 PM, Paolo Bonzini wrote:
>
>
> On 02/04/2015 11:14, Wen Congyang wrote:
>> From ebc024702dd3147e0cbdfd173c599103dc87796c Mon Sep 17 00:00:00 2001
>> From: Wen Congyang
>> Date: Thu, 2 Apr 2015 16:28:17 +0800
>> Subject: [PATCH] fix qiov size
>>
>> Signed-off-by: Wen Congyang
On 02/04/2015 11:14, Wen Congyang wrote:
> From ebc024702dd3147e0cbdfd173c599103dc87796c Mon Sep 17 00:00:00 2001
> From: Wen Congyang
> Date: Thu, 2 Apr 2015 16:28:17 +0800
> Subject: [PATCH] fix qiov size
>
> Signed-off-by: Wen Congyang
> ---
> hw/block/virtio-blk.c | 15 ++
On 02/04/2015 13:52, zhanghailiang wrote:
> diff --git a/exec.c b/exec.c
> index 874ecfc..4b1b39b 100644
> --- a/exec.c
> +++ b/exec.c
> @@ -59,7 +59,7 @@
> //#define DEBUG_SUBPAGE
>
> #if !defined(CONFIG_USER_ONLY)
> -static bool in_migration;
> +bool in_migration;
>
> /* ram_list is read u
On 2015/4/1 3:06, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
On 2015/3/30 15:59, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
On 2015/3/27 18:18, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili
On 03/26/2015 06:29 PM, Juan Quintela wrote:
> Wen Congyang wrote:
>> On 03/25/2015 05:50 PM, Juan Quintela wrote:
>>> zhanghailiang wrote:
Hi all,
We found that, sometimes, the content of VM's memory is
inconsistent between Source side and Destination side
when we check
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
> On 2015/3/30 15:59, Dr. David Alan Gilbert wrote:
> >* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
> >>On 2015/3/27 18:18, Dr. David Alan Gilbert wrote:
> >>>* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
> On 2015/3/2
On Tue, Mar 31, 2015 at 03:54:51PM +0800, Wen Congyang wrote:
> On 03/27/2015 04:56 PM, Stefan Hajnoczi wrote:
> > On Thu, Mar 26, 2015 at 11:29:43AM +0100, Juan Quintela wrote:
> >> Wen Congyang wrote:
> >>> On 03/25/2015 05:50 PM, Juan Quintela wrote:
> zhanghailiang wrote:
> > Hi all,
On 2015/3/30 15:59, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
On 2015/3/27 18:18, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
On 2015/3/26 11:52, Li Zhijian wrote:
On 03/26/2015 11:12 AM, Wen Congyang wrote:
On 03/27/2015 04:56 PM, Stefan Hajnoczi wrote:
> On Thu, Mar 26, 2015 at 11:29:43AM +0100, Juan Quintela wrote:
>> Wen Congyang wrote:
>>> On 03/25/2015 05:50 PM, Juan Quintela wrote:
zhanghailiang wrote:
> Hi all,
>
> We found that, sometimes, the content of VM's memory is
>
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
> On 2015/3/27 18:18, Dr. David Alan Gilbert wrote:
> >* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
> >>On 2015/3/26 11:52, Li Zhijian wrote:
> >>>On 03/26/2015 11:12 AM, Wen Congyang wrote:
> On 03/25/2015 05:50 PM, Juan Quinte
On 2015/3/27 18:18, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
On 2015/3/26 11:52, Li Zhijian wrote:
On 03/26/2015 11:12 AM, Wen Congyang wrote:
On 03/25/2015 05:50 PM, Juan Quintela wrote:
zhanghailiang wrote:
Hi all,
We found that, sometimes, th
On 2015/3/27 18:51, Juan Quintela wrote:
zhanghailiang wrote:
On 2015/3/26 11:52, Li Zhijian wrote:
On 03/26/2015 11:12 AM, Wen Congyang wrote:
On 03/25/2015 05:50 PM, Juan Quintela wrote:
zhanghailiang wrote:
Hi all,
We found that, sometimes, the content of VM's memory is
inconsistent be
zhanghailiang wrote:
> On 2015/3/26 11:52, Li Zhijian wrote:
>> On 03/26/2015 11:12 AM, Wen Congyang wrote:
>>> On 03/25/2015 05:50 PM, Juan Quintela wrote:
zhanghailiang wrote:
> Hi all,
>
> We found that, sometimes, the content of VM's memory is
> inconsistent between Sourc
Wen Congyang wrote:
> On 03/27/2015 05:57 PM, Stefan Hajnoczi wrote:
You must use -drive cache=none if you want to use live migration. It
should not directly affect memory during migration though.
>>>
>>> Otherwise, what will happen? If the user doesn't use cache=none, and
>>> tries to
Wen Congyang wrote:
> On 03/27/2015 04:56 PM, Stefan Hajnoczi wrote:
>> On Thu, Mar 26, 2015 at 11:29:43AM +0100, Juan Quintela wrote:
>>> Wen Congyang wrote:
On 03/25/2015 05:50 PM, Juan Quintela wrote:
> zhanghailiang wrote:
>> Hi all,
>>
>> We found that, sometimes, the c
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
> On 2015/3/26 11:52, Li Zhijian wrote:
> >On 03/26/2015 11:12 AM, Wen Congyang wrote:
> >>On 03/25/2015 05:50 PM, Juan Quintela wrote:
> >>>zhanghailiang wrote:
> Hi all,
>
> We found that, sometimes, the content of VM's memory
On 2015/3/26 11:52, Li Zhijian wrote:
On 03/26/2015 11:12 AM, Wen Congyang wrote:
On 03/25/2015 05:50 PM, Juan Quintela wrote:
zhanghailiang wrote:
Hi all,
We found that, sometimes, the content of VM's memory is inconsistent between
Source side and Destination side
when we check it just aft
On Fri, Mar 27, 2015 at 10:05 AM, Wen Congyang wrote:
> On 03/27/2015 05:57 PM, Stefan Hajnoczi wrote:
>> On Fri, Mar 27, 2015 at 9:14 AM, Wen Congyang wrote:
>>> On 03/27/2015 04:56 PM, Stefan Hajnoczi wrote:
On Thu, Mar 26, 2015 at 11:29:43AM +0100, Juan Quintela wrote:
> Wen Congyang
On 03/27/2015 05:57 PM, Stefan Hajnoczi wrote:
> On Fri, Mar 27, 2015 at 9:14 AM, Wen Congyang wrote:
>> On 03/27/2015 04:56 PM, Stefan Hajnoczi wrote:
>>> On Thu, Mar 26, 2015 at 11:29:43AM +0100, Juan Quintela wrote:
Wen Congyang wrote:
> On 03/25/2015 05:50 PM, Juan Quintela wrote:
>>
On Fri, Mar 27, 2015 at 9:14 AM, Wen Congyang wrote:
> On 03/27/2015 04:56 PM, Stefan Hajnoczi wrote:
>> On Thu, Mar 26, 2015 at 11:29:43AM +0100, Juan Quintela wrote:
>>> Wen Congyang wrote:
On 03/25/2015 05:50 PM, Juan Quintela wrote:
> zhanghailiang wrote:
>> Hi all,
>>
>
On 03/27/2015 04:56 PM, Stefan Hajnoczi wrote:
> On Thu, Mar 26, 2015 at 11:29:43AM +0100, Juan Quintela wrote:
>> Wen Congyang wrote:
>>> On 03/25/2015 05:50 PM, Juan Quintela wrote:
zhanghailiang wrote:
> Hi all,
>
> We found that, sometimes, the content of VM's memory is
>
On Thu, Mar 26, 2015 at 11:29:43AM +0100, Juan Quintela wrote:
> Wen Congyang wrote:
> > On 03/25/2015 05:50 PM, Juan Quintela wrote:
> >> zhanghailiang wrote:
> >>> Hi all,
> >>>
> >>> We found that, sometimes, the content of VM's memory is
> >>> inconsistent between Source side and Destination
On Thu, Mar 26, 2015 at 11:29:43AM +0100, Juan Quintela wrote:
> Wen Congyang wrote:
> > On 03/25/2015 05:50 PM, Juan Quintela wrote:
> >> zhanghailiang wrote:
> >>> Hi all,
> >>>
> >>> We found that, sometimes, the content of VM's memory is
> >>> inconsistent between Source side and Destination
Wen Congyang wrote:
> On 03/25/2015 05:50 PM, Juan Quintela wrote:
>> zhanghailiang wrote:
>>> Hi all,
>>>
>>> We found that, sometimes, the content of VM's memory is
>>> inconsistent between Source side and Destination side
>>> when we check it just after finishing migration but before VM contin
On 03/26/2015 11:12 AM, Wen Congyang
wrote:
On 03/25/2015 05:50 PM, Juan Quintela wrote:
zhanghailiang wrote:
Hi all,
We found that, sometimes, the content of VM's memory is inconsistent between Source side and Destination side
On 03/25/2015 05:50 PM, Juan Quintela wrote:
> zhanghailiang wrote:
>> Hi all,
>>
>> We found that, sometimes, the content of VM's memory is inconsistent between
>> Source side and Destination side
>> when we check it just after finishing migration but before VM continue to
>> Run.
>>
>> We use
On 03/25/2015 09:12 PM, Paolo Bonzini wrote:
>
>
> On 25/03/2015 11:21, Wen Congyang wrote:
>>> What kind of load were you having when reproducing this issue?
>>> Just to confirm, you have been able to reproduce this without COLO
>>> patches, right?
>>
>> I can reproduce it without COLO patches.
On 25/03/2015 11:21, Wen Congyang wrote:
> > What kind of load were you having when reproducing this issue?
> > Just to confirm, you have been able to reproduce this without COLO
> > patches, right?
>
> I can reproduce it without COLO patches.
Thanks. Please try doing mprotect (using qemu_ram_
On 2015/3/25 19:36, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
On 2015/3/25 17:46, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
Hi all,
We found that, sometimes, the content of VM's memory is inconsistent betw
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
> On 2015/3/25 17:46, Dr. David Alan Gilbert wrote:
> >* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
> >>Hi all,
> >>
> >>We found that, sometimes, the content of VM's memory is inconsistent
> >>between Source side and Destination s
On 2015/3/25 17:50, Juan Quintela wrote:
zhanghailiang wrote:
Hi all,
We found that, sometimes, the content of VM's memory is inconsistent between
Source side and Destination side
when we check it just after finishing migration but before VM continue to Run.
We use a patch like bellow to fin
On 2015/3/25 17:46, Dr. David Alan Gilbert wrote:
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
Hi all,
We found that, sometimes, the content of VM's memory is inconsistent between
Source side and Destination side
when we check it just after finishing migration but before VM continue
On 03/25/2015 05:50 PM, Juan Quintela wrote:
> zhanghailiang wrote:
>> Hi all,
>>
>> We found that, sometimes, the content of VM's memory is inconsistent between
>> Source side and Destination side
>> when we check it just after finishing migration but before VM continue to
>> Run.
>>
>> We use
zhanghailiang wrote:
> Hi all,
>
> We found that, sometimes, the content of VM's memory is inconsistent between
> Source side and Destination side
> when we check it just after finishing migration but before VM continue to Run.
>
> We use a patch like bellow to find this issue, you can find it fr
* zhanghailiang (zhang.zhanghaili...@huawei.com) wrote:
> Hi all,
>
> We found that, sometimes, the content of VM's memory is inconsistent between
> Source side and Destination side
> when we check it just after finishing migration but before VM continue to Run.
>
> We use a patch like bellow to
Hi all,
We found that, sometimes, the content of VM's memory is inconsistent between
Source side and Destination side
when we check it just after finishing migration but before VM continue to Run.
We use a patch like bellow to find this issue, you can find it from affix,
and Steps to reproduce:
41 matches
Mail list logo
