On 07/11/17 17:16, Wanpeng Li wrote:
> 2017-11-07 14:12 GMT+08:00 Alexey Kardashevskiy :
>> On 07/11/17 17:02, Wanpeng Li wrote:
>>> Hi Alexey,
>>> 2017-11-07 13:46 GMT+08:00 Alexey Kardashevskiy :
On 07/11/17 01:08, Paolo Bonzini wrote:
> On 06/11/2017 13:18, Wanpeng Li wrote:
>> 2017
2017-11-07 14:12 GMT+08:00 Alexey Kardashevskiy :
> On 07/11/17 17:02, Wanpeng Li wrote:
>> Hi Alexey,
>> 2017-11-07 13:46 GMT+08:00 Alexey Kardashevskiy :
>>> On 07/11/17 01:08, Paolo Bonzini wrote:
On 06/11/2017 13:18, Wanpeng Li wrote:
> 2017-11-06 20:02 GMT+08:00 Paolo Bonzini :
>>
On 07/11/17 17:02, Wanpeng Li wrote:
> Hi Alexey,
> 2017-11-07 13:46 GMT+08:00 Alexey Kardashevskiy :
>> On 07/11/17 01:08, Paolo Bonzini wrote:
>>> On 06/11/2017 13:18, Wanpeng Li wrote:
2017-11-06 20:02 GMT+08:00 Paolo Bonzini :
> On 06/11/2017 12:59, Fam Zheng wrote:
Could you
Hi Alexey,
2017-11-07 13:46 GMT+08:00 Alexey Kardashevskiy :
> On 07/11/17 01:08, Paolo Bonzini wrote:
>> On 06/11/2017 13:18, Wanpeng Li wrote:
>>> 2017-11-06 20:02 GMT+08:00 Paolo Bonzini :
On 06/11/2017 12:59, Fam Zheng wrote:
>>> Could you point out the patchset for the fix?
>> Bet
On 07/11/17 01:08, Paolo Bonzini wrote:
> On 06/11/2017 13:18, Wanpeng Li wrote:
>> 2017-11-06 20:02 GMT+08:00 Paolo Bonzini :
>>> On 06/11/2017 12:59, Fam Zheng wrote:
>> Could you point out the patchset for the fix?
> Between 447b0d0b9ee8a0ac216c3186e0f3c427a1001f0c and
> 092aa2fc65b7
2017-11-06 22:08 GMT+08:00 Paolo Bonzini :
> On 06/11/2017 13:18, Wanpeng Li wrote:
>> 2017-11-06 20:02 GMT+08:00 Paolo Bonzini :
>>> On 06/11/2017 12:59, Fam Zheng wrote:
>> Could you point out the patchset for the fix?
> Between 447b0d0b9ee8a0ac216c3186e0f3c427a1001f0c and
> 092aa2fc6
On 06/11/2017 13:18, Wanpeng Li wrote:
> 2017-11-06 20:02 GMT+08:00 Paolo Bonzini :
>> On 06/11/2017 12:59, Fam Zheng wrote:
> Could you point out the patchset for the fix?
Between 447b0d0b9ee8a0ac216c3186e0f3c427a1001f0c and
092aa2fc65b7a35121616aad8f39d47b8f921618.
>>> Not sure how
2017-11-06 20:02 GMT+08:00 Paolo Bonzini :
> On 06/11/2017 12:59, Fam Zheng wrote:
Could you point out the patchset for the fix?
>>> Between 447b0d0b9ee8a0ac216c3186e0f3c427a1001f0c and
>>> 092aa2fc65b7a35121616aad8f39d47b8f921618.
>> Not sure how these relate to the core size, but I've tested
On 06/11/2017 12:59, Fam Zheng wrote:
>>> Could you point out the patchset for the fix?
>> Between 447b0d0b9ee8a0ac216c3186e0f3c427a1001f0c and
>> 092aa2fc65b7a35121616aad8f39d47b8f921618.
> Not sure how these relate to the core size, but I've tested upstream
> (ec7a8bf0b8f7dc7288fe8745464ee8217528
On Mon, 11/06 11:26, Paolo Bonzini wrote:
> On 06/11/2017 11:01, Wanpeng Li wrote:
> > 2017-11-06 17:41 GMT+08:00 Paolo Bonzini :
> >> On 06/11/2017 10:11, Wanpeng Li wrote:
> >>> Hi all,
> >>>
> >>> qemu core dump, max_core="unlimited", dump_guest_core=0, kill -11 pid
> >>> to generate a qemu core
On 06/11/2017 11:01, Wanpeng Li wrote:
> 2017-11-06 17:41 GMT+08:00 Paolo Bonzini :
>> On 06/11/2017 10:11, Wanpeng Li wrote:
>>> Hi all,
>>>
>>> qemu core dump, max_core="unlimited", dump_guest_core=0, kill -11 pid
>>> to generate a qemu core file, the Rss of qemu itself is ~40MB, the
>>> core fil
2017-11-06 17:41 GMT+08:00 Paolo Bonzini :
> On 06/11/2017 10:11, Wanpeng Li wrote:
>> Hi all,
>>
>> qemu core dump, max_core="unlimited", dump_guest_core=0, kill -11 pid
>> to generate a qemu core file, the Rss of qemu itself is ~40MB, the
>> core file is almost ~40MB in centos 6.x, but ~400MB in
On 06/11/2017 10:11, Wanpeng Li wrote:
> Hi all,
>
> qemu core dump, max_core="unlimited", dump_guest_core=0, kill -11 pid
> to generate a qemu core file, the Rss of qemu itself is ~40MB, the
> core file is almost ~40MB in centos 6.x, but ~400MB in cents 7.x, any
> idea?
My suspicion is the memor
Hi all,
qemu core dump, max_core="unlimited", dump_guest_core=0, kill -11 pid
to generate a qemu core file, the Rss of qemu itself is ~40MB, the
core file is almost ~40MB in centos 6.x, but ~400MB in cents 7.x, any
idea?
Regards,
Wanpeng Li
14 matches
Mail list logo