Hi, ALL
Currently kvm hypervisor have lots of features depend on linux standard apis,
like vcpupin/mempin/processpin etc. But in the real production environment,
we need an automated resource assign and/or scheduling, is there any plan to
implement it?
resource assignment requirements like:
cpu
Hi David
Where can I get your post-copy git tree?
I wish to take a look into it first before start live-snapshot design.
Thanks.
> I'm working on post-copy at the moment, using Andrea's kernel code, using bits
> of Yamahata's code base as well; hopefully it won't be too long until we have
> so
Hi, Andrea
Where can I get the dev-git-branch?
I can use it to try the snapshot prototype coding.
Thanks.
> -Original Message-
> From: Andrea Arcangeli [mailto:aarca...@redhat.com]
> Sent: Tuesday, March 04, 2014 3:52 AM
> To: Paolo Bonzini
> Cc: Kevin Wolf; Stefan Hajn
> > Good suggestion, The latest patches of post-copy seems updated 2 years
> ago.
> > https://github.com/yamahata/qemu
>
> I'm working on post-copy at the moment, using Andrea's kernel code, using bits
> of Yamahata's code base as well; hopefully it won't be too long until we have
> something to p
> > Is there any other proposals to implement vm-snapshot?
>
> See the discussion by Paolo and Andrea about post-copy migration, which adds
> kernel memory management features for tracking userspace page faults.
> Perhaps you can use that infrastructure to trap guest writes.
>
> Stefan
I will lo
> Hi Paolo,
>
> On Mon, Mar 03, 2014 at 02:47:31PM +0100, Paolo Bonzini wrote:
> > I'm not sure what's the status of the kernel infrastructure for
> > post-copy. Andrea?
>
> sys_userfaultfd is still work in progress but it shouldn't be much work left
> to
> completion. madvise(MADV_USERFAUL
> > I think this is different in the same way that block-backup and
> > block-mirror are different. Huangpeng's proposal would let you make a
> > consistent snapshot of disks and RAM.
>
> Right. Though the point isn't about consistency (doing the disk snapshot when
> memory has converged would be
> > > Here I have another proposal, based on the live-migration scheme,
> > > add consistent memory state tracking and saving.
> > > The idea is simple:
> > > 1.First round use live-migration to save all memory to a snapshot file.
> > > 2.intercept the action of memory-modify, save old pages to a
> Yes, this is the tricky part. To be honest, I think this is the reason no
> one has
> submitted patches - it's a hard task and the win isn't that great (you can
> already migrate to file).
>
Yes, lots of places have to be considered. Though scenarios are limited, users
like
library experimen
Hi, All
I found some discussion about VM live-snapshot, but haven't seen any progress.
https://lists.gnu.org/archive/html/qemu-devel/2013-08/msg02125.html
http://markmail.org/thread/shneezha7kmtosvb#query:+page:1+mid:shneezha7kmtosvb+state:results
Here I have another proposal, based on the live-m
10 matches
Mail list logo
