> Hmm, I think we need the two flags. Although it is little hard to do it.
> Because the vm can't
> do something like hotplug vcpu or device during migrate. But for now qemu
> don't guarantee it(in my reading).
> So we should change the vm state RUN_STATE_RUNNING to RUN_STATE_MIGRATE when
> mig
On 2014/5/22 19:21, Sanidhya Kashyap wrote:
> On Wed, May 21, 2014 at 12:15 PM, ChenLiang wrote:
>> On 2014/5/21 12:56, Sanidhya Kashyap wrote:
>>
>>> On Wed, May 21, 2014 at 9:43 AM, ChenLiang wrote:
Hi,
Nice job. We should avoid running migration_thread and
bitmap_logging_threa
On Wed, May 21, 2014 at 12:15 PM, ChenLiang wrote:
> On 2014/5/21 12:56, Sanidhya Kashyap wrote:
>
>> On Wed, May 21, 2014 at 9:43 AM, ChenLiang wrote:
>>> Hi,
>>> Nice job. We should avoid running migration_thread and
>>> bitmap_logging_thread simultaneously.
>>>
>> Any particular suggestion to
>
> We can do it like this:
> https://lists.gnu.org/archive/html/qemu-devel/2014-04/msg02185.html
>
Thanks.
If we are using only one of the threads, then I think we do not
require the splitting of the dirty bitmap (
https://lists.gnu.org/archive/html/qemu-devel/2014-05/msg04041.html ).
I can dire
On 2014/5/21 12:56, Sanidhya Kashyap wrote:
> On Wed, May 21, 2014 at 9:43 AM, ChenLiang wrote:
>> Hi,
>> Nice job. We should avoid running migration_thread and bitmap_logging_thread
>> simultaneously.
>>
> Any particular suggestion to avoid running simultaneous execution of
> the threads?
>
>
On Wed, May 21, 2014 at 9:43 AM, ChenLiang wrote:
> Hi,
> Nice job. We should avoid running migration_thread and bitmap_logging_thread
> simultaneously.
>
Any particular suggestion to avoid running simultaneous execution of
the threads?
--
Sanidhya
Hi,
Nice job. We should avoid running migration_thread and bitmap_logging_thread
simultaneously.
Best regards:
ChenLiang
> Hi,
>
> This is the first part of my gsoc work.
>
> Following patches add the support of dirty bitmap logging and dumping
> to a specified file. These patches provide the
