On Thu, Aug 15, 2013 at 10:26:36AM +0800, Wenchao Xia wrote:
于 2013-8-14 15:53, Stefan Hajnoczi 写道:
On Wed, Aug 14, 2013 at 3:54 AM, Wenchao Xia xiaw...@linux.vnet.ibm.com
wrote:
于 2013-8-13 16:21, Stefan Hajnoczi 写道:
On Tue, Aug 13, 2013 at 4:53 AM, Wenchao Xia
于 2013-8-15 15:49, Stefan Hajnoczi 写道:
On Thu, Aug 15, 2013 at 10:26:36AM +0800, Wenchao Xia wrote:
于 2013-8-14 15:53, Stefan Hajnoczi 写道:
On Wed, Aug 14, 2013 at 3:54 AM, Wenchao Xia xiaw...@linux.vnet.ibm.com wrote:
于 2013-8-13 16:21, Stefan Hajnoczi 写道:
On Tue, Aug 13, 2013 at 4:53 AM,
On Wed, Aug 14, 2013 at 3:54 AM, Wenchao Xia xiaw...@linux.vnet.ibm.com wrote:
于 2013-8-13 16:21, Stefan Hajnoczi 写道:
On Tue, Aug 13, 2013 at 4:53 AM, Wenchao Xia xiaw...@linux.vnet.ibm.com
wrote:
于 2013-8-12 19:33, Stefan Hajnoczi 写道:
On Mon, Aug 12, 2013 at 12:26 PM, Alex Bligh
On 14 Aug 2013, at 08:53, Stefan Hajnoczi wrote:
The fork child can minimize the chance of out-of-memory by using
madvise(MADV_DONTNEED) after pages have been written out.
This may also be helpful (last clause) before starting writing.
MADV_SEQUENTIAL
Expect page
于 2013-8-14 15:53, Stefan Hajnoczi 写道:
On Wed, Aug 14, 2013 at 3:54 AM, Wenchao Xia xiaw...@linux.vnet.ibm.com
wrote:
于 2013-8-13 16:21, Stefan Hajnoczi 写道:
On Tue, Aug 13, 2013 at 4:53 AM, Wenchao Xia xiaw...@linux.vnet.ibm.com
wrote:
于 2013-8-12 19:33, Stefan Hajnoczi 写道:
On Mon, Aug
On Tue, Aug 13, 2013 at 4:53 AM, Wenchao Xia xiaw...@linux.vnet.ibm.com wrote:
于 2013-8-12 19:33, Stefan Hajnoczi 写道:
On Mon, Aug 12, 2013 at 12:26 PM, Alex Bligh a...@alex.org.uk wrote:
--On 12 August 2013 11:59:03 +0200 Stefan Hajnoczi stefa...@gmail.com
wrote:
The idea that was
于 2013-8-13 16:21, Stefan Hajnoczi 写道:
On Tue, Aug 13, 2013 at 4:53 AM, Wenchao Xia xiaw...@linux.vnet.ibm.com wrote:
于 2013-8-12 19:33, Stefan Hajnoczi 写道:
On Mon, Aug 12, 2013 at 12:26 PM, Alex Bligh a...@alex.org.uk wrote:
--On 12 August 2013 11:59:03 +0200 Stefan Hajnoczi
On Fri, Aug 09, 2013 at 10:20:49AM +, Chijianchun wrote:
Now in KVM, when RAM snapshot, vcpus needs stopped, it is Unfriendly
restrictions to users.
Are there plans to achieve ram live Snapshot feature?
in my mind, Snapshots can not occupy additional too much memory, So when
--On 12 August 2013 11:59:03 +0200 Stefan Hajnoczi stefa...@gmail.com
wrote:
The idea that was discussed on qemu-de...@nongnu.org uses fork(2) to
capture the state of guest RAM and then send it back to the parent
process. The guest is only paused for a brief instant during fork(2)
and can
On Mon, Aug 12, 2013 at 12:26 PM, Alex Bligh a...@alex.org.uk wrote:
--On 12 August 2013 11:59:03 +0200 Stefan Hajnoczi stefa...@gmail.com
wrote:
The idea that was discussed on qemu-de...@nongnu.org uses fork(2) to
capture the state of guest RAM and then send it back to the parent
process.
于 2013-8-12 19:33, Stefan Hajnoczi 写道:
On Mon, Aug 12, 2013 at 12:26 PM, Alex Bligh a...@alex.org.uk wrote:
--On 12 August 2013 11:59:03 +0200 Stefan Hajnoczi stefa...@gmail.com
wrote:
The idea that was discussed on qemu-de...@nongnu.org uses fork(2) to
capture the state of guest RAM and then
Il 09/08/2013 12:20, Chijianchun ha scritto:
Now in KVM, when RAM snapshot, vcpus needs stopped, it is Unfriendly
restrictions to users.
Are there plans to achieve ram live Snapshot feature?
in my mind, Snapshots can not occupy additional too much memory, So when
the memory needs
Chijianchun chijianc...@huawei.com writes:
Now in KVM, when RAM snapshot, vcpus needs stopped, it is Unfriendly
restrictions to users.
Are there plans to achieve ram live Snapshot feature?
I think you mean a live version of the savevm command.
You can approximate live migrating to a file
On 08/09/2013 09:45 AM, Anthony Liguori wrote:
Chijianchun chijianc...@huawei.com writes:
Now in KVM, when RAM snapshot, vcpus needs stopped, it is Unfriendly
restrictions to users.
Are there plans to achieve ram live Snapshot feature?
I think you mean a live version of the savevm
14 matches
Mail list logo
