qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] migration: add a MAINTAINERS entry for migratio


From: Anthony Liguori
Subject: Re: [Qemu-devel] [PATCH] migration: add a MAINTAINERS entry for migration
Date: Tue, 15 Nov 2011 07:45:30 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.21) Gecko/20110831 Lightning/1.0b2 Thunderbird/3.1.13

On 11/15/2011 02:32 AM, Stefan Hajnoczi wrote:
On Mon, Nov 14, 2011 at 03:08:25PM -0600, Anthony Liguori wrote:
On 11/14/2011 11:40 AM, Juan Quintela wrote:
Anthony Liguori<address@hidden>   wrote:
I think this is an accurate reflection of the state of migration today.  This
is the second release in a row where we're scrambling to fix a critical issue
in migration.

We need to make our mind about it.

Ultimately, we need to make migration a priority.  That's what I'm
trying to do here.

The first step is to be open about the state of migration today.  I
personally don't have the bandwidth to invest a lot of effort in
migration, but I can invest time in trying to find more people to
work on migration, and help put together a proper roadmap.

It would help to have a migration wiki page or document that explains
the implications of migration on QEMU code - what to look out for in
device emulation code.

Although regular QEMU contributors may know the background on
migration/save/load, it would be not only helpful for new contributors
but also a good refresher for those of us who have picked up the
assumptions around migration piecewise.

I think a good document would raise migration awareness and help us
review new patches with an eye towards correct migration behavior.

The rules need to be laid down by someone who understands migration
quite well.

100% agreed.

I'll volunteer to start by taking the storage requirements wiki page, converting it to markdown, and adding it to docs/migration

Regards,

Anthony Liguori


Stefan





reply via email to

[Prev in Thread] Current Thread [Next in Thread]