From de2b252df5456ed9f1a5b4f696f4ba8c8748b8a0 Mon Sep 17 00:00:00 2001 From: Dan Kenigsberg Date: Mon, 19 Oct 2009 14:53:29 +0200 Subject: [PATCH] fix virDomainMigrateToURI doc * src/libvirt.c: remove reverences to non existent dconn parameter when using that entry point. --- src/libvirt.c | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/src/libvirt.c b/src/libvirt.c index 92a1eaa010..9e8790023a 100644 --- a/src/libvirt.c +++ b/src/libvirt.c @@ -3279,7 +3279,7 @@ error: * @bandwidth: (optional) specify migration bandwidth limit in Mbps * * Migrate the domain object from its current host to the destination - * host given by dconn (a connection to the destination host). + * host given by duri. * * Flags may be one of more of the following: * VIR_MIGRATE_LIVE Do not pause the VM during migration @@ -3298,14 +3298,11 @@ error: * * If the VIR_MIGRATE_PEER2PEER flag is set, the duri parameter * must be a valid libvirt connection URI, by which the source - * libvirt driver can connect to the destination libvirt. If - * omitted, the dconn connection object will be queried for its - * current URI. + * libvirt driver can connect to the destination libvirt. * * If the VIR_MIGRATE_PEER2PEER flag is NOT set, the duri parameter * takes a hypervisor specific format. The hypervisor capabilities - * XML includes details of the support URI schemes. If omitted - * the dconn will be asked for a default URI. Not all hypervisors + * XML includes details of the support URI schemes. Not all hypervisors * will support this mode of migration, so if the VIR_MIGRATE_PEER2PEER * flag is not set, then it may be neccessary to use the alternative * virDomainMigrate API providing an explicit virConnectPtr for the -- GitLab