* [Qemu-devel] VM-Migration
@ 2017-04-26 15:51 Pradeep Kiruvale
2017-04-26 16:14 ` Dr. David Alan Gilbert
0 siblings, 1 reply; 3+ messages in thread
From: Pradeep Kiruvale @ 2017-04-26 15:51 UTC (permalink / raw)
To: qemu-devel@nongnu.org Developers
Hi All,
Is it possible to enable/disable to migration features on the fly for a
qemu VM?
I mean through qmp interface kind of a interface?
I am asking this because keeping the dirty memory list, this could consume
some
compute and memory. So, the plan is to enable when the VM needs to be
migrated.
Please clarify.
Regards,
Pradeep
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] VM-Migration
2017-04-26 15:51 [Qemu-devel] VM-Migration Pradeep Kiruvale
@ 2017-04-26 16:14 ` Dr. David Alan Gilbert
2017-04-27 9:40 ` Pradeep Kiruvale
0 siblings, 1 reply; 3+ messages in thread
From: Dr. David Alan Gilbert @ 2017-04-26 16:14 UTC (permalink / raw)
To: Pradeep Kiruvale; +Cc: qemu-devel@nongnu.org Developers, quintela
* Pradeep Kiruvale (pradeepkiruvale@gmail.com) wrote:
> Hi All,
>
> Is it possible to enable/disable to migration features on the fly for a
> qemu VM?
> I mean through qmp interface kind of a interface?
>
> I am asking this because keeping the dirty memory list, this could consume
> some
> compute and memory. So, the plan is to enable when the VM needs to be
> migrated.
>
> Please clarify.
These bitmaps should already only be allocated during the migration process,
so you shouldn't be seeing any overhead during normal running.
See migration/ram.c ram_save_setup->ram_state_init which allocates
ram_bitmap and that only happens at the start of migration.
ram_state_init also calls memory_global_dirty_log_start which does
the kernel side of it.
Dave
> Regards,
> Pradeep
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] VM-Migration
2017-04-26 16:14 ` Dr. David Alan Gilbert
@ 2017-04-27 9:40 ` Pradeep Kiruvale
0 siblings, 0 replies; 3+ messages in thread
From: Pradeep Kiruvale @ 2017-04-27 9:40 UTC (permalink / raw)
To: Dr. David Alan Gilbert; +Cc: qemu-devel@nongnu.org Developers, quintela
On 26 April 2017 at 18:14, Dr. David Alan Gilbert <dgilbert@redhat.com>
wrote:
> * Pradeep Kiruvale (pradeepkiruvale@gmail.com) wrote:
> > Hi All,
> >
> > Is it possible to enable/disable to migration features on the fly for a
> > qemu VM?
> > I mean through qmp interface kind of a interface?
> >
> > I am asking this because keeping the dirty memory list, this could
> consume
> > some
> > compute and memory. So, the plan is to enable when the VM needs to be
> > migrated.
> >
> > Please clarify.
>
> These bitmaps should already only be allocated during the migration
> process,
> so you shouldn't be seeing any overhead during normal running.
>
> See migration/ram.c ram_save_setup->ram_state_init which allocates
> ram_bitmap and that only happens at the start of migration.
> ram_state_init also calls memory_global_dirty_log_start which does
> the kernel side of it.
>
>
Thanks for the clarification Dave!.
-Pradeep
Dave
>
> > Regards,
> > Pradeep
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-04-27 9:40 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-04-26 15:51 [Qemu-devel] VM-Migration Pradeep Kiruvale
2017-04-26 16:14 ` Dr. David Alan Gilbert
2017-04-27 9:40 ` Pradeep Kiruvale
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.