Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



RJ>  * Params is a linked list of hypervisor-specific parameters.  Each
RJ>  * element is a virMigrateParamPtr containing the following fields:
RJ>  *   name               Parameter name being set.
RJ>  *   value              A union expressing the value.
RJ>  *     value.strv         A string value.
RJ>  *     value.longv        A long value.
RJ>  *   next               Next in linked list (or NULL for end of list).

This should allow us to pass URIs to qemu, as well.  I like it :)

RJ> +    /* Try to migrate. */
RJ> +    ddomain = conn->driver->domainMigrate (domain, dconn, flags,
RJ> +                                           dname,
RJ> +                                           hostname ? hostname : nchostname,
RJ> +                                           params);

As was previously mentioned, don't we need a call to the remote side
to let it know that the domain is coming before we start the actual
migration?  Are you expecting the driver implementation to do this?

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@xxxxxxxxxx

Attachment: pgppO2mJ7jh6M.pgp
Description: PGP signature

--
Libvir-list mailing list
Libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]