libvirt users - Dec 2010 - using virDomainMigrateSetMaxDowntime

I would like to use the virDomainMigrateSetMaxDowntime but I'm a bit
confused about how to use it.

If I try to set the downtime before I call domain.migrate(), I get the
error "domain is not being migrated". But I cannot call it afterwards
because domain.migrate() does not return until the migration has
completed.

Am I meant to put the call to domain.migrate() into a separate thread of
control, and then call SetMaxDowntime from my main thread after the
migration has begun? How do I even know if the migration has begun?

Thanks!
--Igor

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL:
<http://listman.redhat.com/archives/libvirt-users/attachments/20101217/77b3de06/attachment.sig>

? 2010?12?17? 16:34, Igor Serebryany ??:
> I would like to use the virDomainMigrateSetMaxDowntime but I'm a bit
> confused about how to use it.
> 
> If I try to set the downtime before I call domain.migrate(), I get the
> error "domain is not being migrated". But I cannot call it
afterwards
> because domain.migrate() does not return until the migration has
> completed.
the API is intended to prevent the migration from lasting forever if
the memory of source domain is dirtying so quickly that QEMU does
not have time todo the final completion switchover, but not to
guarantee the migration will be finished more quickly.

so yes, domain.migration will not return till it's finished.

- Osier