On 11/15/2011 03:36 AM, Kevin Wolf wrote:
Am 14.11.2011 22:08, schrieb Anthony Liguori:
On 11/14/2011 11:40 AM, Juan Quintela wrote:
Anthony Liguori 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 f
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 wrote:
I think this is an accurate reflection of the state of migration today. This
is the second release in a row whe
On 11/15/2011 10:32 AM, Stefan Hajnoczi wrote:
> 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/l
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 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 critic
Am 14.11.2011 22:08, schrieb Anthony Liguori:
> On 11/14/2011 11:40 AM, Juan Quintela wrote:
>> Anthony Liguori 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
>>> i
On 11/14/2011 11:40 AM, Juan Quintela wrote:
Anthony Liguori 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 nee
Anthony Liguori 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.
A patch to do the reopen was posted long, long ago. Code exis
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.
The first step in fixing this problem is being up front about what the current
state of the subsystem is. If we're going to tre
