Igor Mammedov wrote:
> On Thu, 23 Mar 2017 21:50:24 +0100
> Juan Quintela wrote:
>
>> Until we have reviewed what can/can't be hotplug during migration,
>> disable it. We can enable it later for the things that we know that
>> work. For instance, memory hotplug during postcopy don't work
>> cur
On Thu, 23 Mar 2017 21:50:24 +0100
Juan Quintela wrote:
> Until we have reviewed what can/can't be hotplug during migration,
> disable it. We can enable it later for the things that we know that
> work. For instance, memory hotplug during postcopy don't work
> currently.
>
> Signed-off-by: Jua
Thomas Huth wrote:
> On 23.03.2017 21:50, Juan Quintela wrote:
>> Until we have reviewed what can/can't be hotplug during migration,
>> disable it. We can enable it later for the things that we know that
>> work. For instance, memory hotplug during postcopy don't work
>> currently.
>>
>> Signed
On 23.03.2017 21:50, Juan Quintela wrote:
> Until we have reviewed what can/can't be hotplug during migration,
> disable it. We can enable it later for the things that we know that
> work. For instance, memory hotplug during postcopy don't work
> currently.
>
> Signed-off-by: Juan Quintela
> --
Until we have reviewed what can/can't be hotplug during migration,
disable it. We can enable it later for the things that we know that
work. For instance, memory hotplug during postcopy don't work
currently.
Signed-off-by: Juan Quintela
---
hw/core/qdev.c | 5 +
qdev-monitor.c | 7 ++-
