On 09/20/2012 02:54 PM, Michal Privoznik wrote:
> On 20.09.2012 10:58, Martin Kletzander wrote:
>> Sometimes when guest machine crashes, coredump can get huge due to the
>> guest memory. This can be limited using madvise(2) system call and is
>> being used in QEMU hypervisor. This patch adds an opt
On 20.09.2012 10:58, Martin Kletzander wrote:
> Sometimes when guest machine crashes, coredump can get huge due to the
> guest memory. This can be limited using madvise(2) system call and is
> being used in QEMU hypervisor. This patch adds an option for configuring
> that in the domain XML and rela
On Thu, Sep 20, 2012 at 11:54:06AM +0200, Martin Kletzander wrote:
> On 09/20/2012 11:32 AM, Daniel P. Berrange wrote:
> > On Thu, Sep 20, 2012 at 10:58:13AM +0200, Martin Kletzander wrote:
> >> Sometimes when guest machine crashes, coredump can get huge due to the
> >> guest memory. This can be li
On 09/20/2012 11:32 AM, Daniel P. Berrange wrote:
> On Thu, Sep 20, 2012 at 10:58:13AM +0200, Martin Kletzander wrote:
>> Sometimes when guest machine crashes, coredump can get huge due to the
>> guest memory. This can be limited using madvise(2) system call and is
>> being used in QEMU hypervisor.
On Thu, Sep 20, 2012 at 10:58:13AM +0200, Martin Kletzander wrote:
> Sometimes when guest machine crashes, coredump can get huge due to the
> guest memory. This can be limited using madvise(2) system call and is
> being used in QEMU hypervisor. This patch adds an option for configuring
> that in th
Sometimes when guest machine crashes, coredump can get huge due to the
guest memory. This can be limited using madvise(2) system call and is
being used in QEMU hypervisor. This patch adds an option for configuring
that in the domain XML and related documentation.
---
docs/formatdomain.html.in
