On Thu, Oct 01, 2009 at 03:57:13PM +0200, Paolo Bonzini wrote:
> On 09/17/2009 07:25 PM, Daniel P. Berrange wrote:
> >+if (flags& VIR_MIGRATE_PEER2PEER) {
> >+if (VIR_DRV_SUPPORTS_FEATURE (domain->conn->driver, domain->conn,
> >+ VIR_DRV_FEATURE_MIG
On 09/17/2009 07:25 PM, Daniel P. Berrange wrote:
+if (flags& VIR_MIGRATE_PEER2PEER) {
+if (VIR_DRV_SUPPORTS_FEATURE (domain->conn->driver, domain->conn,
+ VIR_DRV_FEATURE_MIGRATION_P2P)) {
+char *duri = NULL;
Is there a reason why y
On Fri, Sep 25, 2009 at 02:27:23PM +0100, Daniel P. Berrange wrote:
> On Tue, Sep 22, 2009 at 02:43:20PM +0200, Daniel Veillard wrote:
> > [ Sending again due to mail output problems ]
> >
> > On Thu, Sep 17, 2009 at 06:25:01PM +0100, Daniel P. Berrange wrote:
> > > Introduces several new public A
On Tue, Sep 22, 2009 at 02:43:20PM +0200, Daniel Veillard wrote:
> [ Sending again due to mail output problems ]
>
> On Thu, Sep 17, 2009 at 06:25:01PM +0100, Daniel P. Berrange wrote:
> > Introduces several new public API options for migration
> >
> > - VIR_MIGRATE_PEER2PEER: With this flag the
[ Sending again due to mail output problems ]
On Thu, Sep 17, 2009 at 06:25:01PM +0100, Daniel P. Berrange wrote:
> Introduces several new public API options for migration
>
> - VIR_MIGRATE_PEER2PEER: With this flag the client only
>invokes the virDomainMigratePerform method, expecting
>
Introduces several new public API options for migration
- VIR_MIGRATE_PEER2PEER: With this flag the client only
invokes the virDomainMigratePerform method, expecting
the source host driver to do whatever is required to
complete the entire migration process.
- VIR_MIGRATE_TUNNELLED: With
