2009-08-05 17:24:29 +02:00
|
|
|
/*
|
2016-07-28 10:54:34 +02:00
|
|
|
* QEMU live migration via socket
|
2009-08-05 17:24:29 +02:00
|
|
|
*
|
2016-04-27 12:05:02 +02:00
|
|
|
* Copyright Red Hat, Inc. 2009-2016
|
2009-08-05 17:24:29 +02:00
|
|
|
*
|
|
|
|
* Authors:
|
|
|
|
* Chris Lalancette <clalance@redhat.com>
|
2016-04-27 12:05:02 +02:00
|
|
|
* Daniel P. Berrange <berrange@redhat.com>
|
2009-08-05 17:24:29 +02:00
|
|
|
*
|
|
|
|
* This work is licensed under the terms of the GNU GPL, version 2. See
|
|
|
|
* the COPYING file in the top-level directory.
|
|
|
|
*
|
2012-01-13 17:44:23 +01:00
|
|
|
* Contributions after 2012-01-13 are licensed under the terms of the
|
|
|
|
* GNU GPL, version 2 or (at your option) any later version.
|
2009-08-05 17:24:29 +02:00
|
|
|
*/
|
|
|
|
|
2016-01-26 19:16:54 +01:00
|
|
|
#include "qemu/osdep.h"
|
2014-03-19 14:34:28 +01:00
|
|
|
|
2009-08-05 17:24:29 +02:00
|
|
|
#include "qemu-common.h"
|
2014-03-19 14:34:28 +01:00
|
|
|
#include "qemu/error-report.h"
|
2016-04-27 12:05:02 +02:00
|
|
|
#include "qapi/error.h"
|
2012-12-17 18:19:50 +01:00
|
|
|
#include "migration/migration.h"
|
2012-10-03 14:07:31 +02:00
|
|
|
#include "migration/qemu-file.h"
|
2016-04-27 12:05:02 +02:00
|
|
|
#include "io/channel-socket.h"
|
|
|
|
#include "trace.h"
|
2009-08-05 17:24:29 +02:00
|
|
|
|
|
|
|
|
2016-04-27 12:05:04 +02:00
|
|
|
static SocketAddress *tcp_build_address(const char *host_port, Error **errp)
|
|
|
|
{
|
|
|
|
InetSocketAddress *iaddr = inet_parse(host_port, errp);
|
|
|
|
SocketAddress *saddr;
|
|
|
|
|
|
|
|
if (!iaddr) {
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
saddr = g_new0(SocketAddress, 1);
|
|
|
|
saddr->type = SOCKET_ADDRESS_KIND_INET;
|
|
|
|
saddr->u.inet.data = iaddr;
|
|
|
|
|
|
|
|
return saddr;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2016-04-27 12:05:02 +02:00
|
|
|
static SocketAddress *unix_build_address(const char *path)
|
|
|
|
{
|
|
|
|
SocketAddress *saddr;
|
|
|
|
|
|
|
|
saddr = g_new0(SocketAddress, 1);
|
|
|
|
saddr->type = SOCKET_ADDRESS_KIND_UNIX;
|
|
|
|
saddr->u.q_unix.data = g_new0(UnixSocketAddress, 1);
|
|
|
|
saddr->u.q_unix.data->path = g_strdup(path);
|
|
|
|
|
|
|
|
return saddr;
|
|
|
|
}
|
2009-08-05 17:24:29 +02:00
|
|
|
|
2016-04-27 12:05:02 +02:00
|
|
|
|
migration: add support for encrypting data with TLS
This extends the migration_set_incoming_channel and
migration_set_outgoing_channel methods so that they
will automatically wrap the QIOChannel in a
QIOChannelTLS instance if TLS credentials are configured
in the migration parameters.
This allows TLS to work for tcp, unix, fd and exec
migration protocols. It does not (currently) work for
RDMA since it does not use these APIs, but it is
unlikely that TLS would be desired with RDMA anyway
since it would degrade the performance to that seen
with TCP defeating the purpose of using RDMA.
On the target host, QEMU would be launched with a set
of TLS credentials for a server endpoint
$ qemu-system-x86_64 -monitor stdio -incoming defer \
-object tls-creds-x509,dir=/home/berrange/security/qemutls,endpoint=server,id=tls0 \
...other args...
To enable incoming TLS migration 2 monitor commands are
then used
(qemu) migrate_set_str_parameter tls-creds tls0
(qemu) migrate_incoming tcp:myhostname:9000
On the source host, QEMU is launched in a similar
manner but using client endpoint credentials
$ qemu-system-x86_64 -monitor stdio \
-object tls-creds-x509,dir=/home/berrange/security/qemutls,endpoint=client,id=tls0 \
...other args...
To enable outgoing TLS migration 2 monitor commands are
then used
(qemu) migrate_set_str_parameter tls-creds tls0
(qemu) migrate tcp:otherhostname:9000
Thanks to earlier improvements to error reporting,
TLS errors can be seen 'info migrate' when doing a
detached migration. For example:
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off x-postcopy-ram: off
Migration status: failed
total time: 0 milliseconds
error description: TLS handshake failed: The TLS connection was non-properly terminated.
Or
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off x-postcopy-ram: off
Migration status: failed
total time: 0 milliseconds
error description: Certificate does not match the hostname localhost
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1461751518-12128-27-git-send-email-berrange@redhat.com>
Signed-off-by: Amit Shah <amit.shah@redhat.com>
2016-04-27 12:05:16 +02:00
|
|
|
struct SocketConnectData {
|
|
|
|
MigrationState *s;
|
|
|
|
char *hostname;
|
|
|
|
};
|
|
|
|
|
|
|
|
static void socket_connect_data_free(void *opaque)
|
|
|
|
{
|
|
|
|
struct SocketConnectData *data = opaque;
|
|
|
|
if (!data) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
g_free(data->hostname);
|
|
|
|
g_free(data);
|
|
|
|
}
|
|
|
|
|
2016-04-27 12:05:03 +02:00
|
|
|
static void socket_outgoing_migration(Object *src,
|
|
|
|
Error *err,
|
|
|
|
gpointer opaque)
|
2009-08-05 17:24:29 +02:00
|
|
|
{
|
migration: add support for encrypting data with TLS
This extends the migration_set_incoming_channel and
migration_set_outgoing_channel methods so that they
will automatically wrap the QIOChannel in a
QIOChannelTLS instance if TLS credentials are configured
in the migration parameters.
This allows TLS to work for tcp, unix, fd and exec
migration protocols. It does not (currently) work for
RDMA since it does not use these APIs, but it is
unlikely that TLS would be desired with RDMA anyway
since it would degrade the performance to that seen
with TCP defeating the purpose of using RDMA.
On the target host, QEMU would be launched with a set
of TLS credentials for a server endpoint
$ qemu-system-x86_64 -monitor stdio -incoming defer \
-object tls-creds-x509,dir=/home/berrange/security/qemutls,endpoint=server,id=tls0 \
...other args...
To enable incoming TLS migration 2 monitor commands are
then used
(qemu) migrate_set_str_parameter tls-creds tls0
(qemu) migrate_incoming tcp:myhostname:9000
On the source host, QEMU is launched in a similar
manner but using client endpoint credentials
$ qemu-system-x86_64 -monitor stdio \
-object tls-creds-x509,dir=/home/berrange/security/qemutls,endpoint=client,id=tls0 \
...other args...
To enable outgoing TLS migration 2 monitor commands are
then used
(qemu) migrate_set_str_parameter tls-creds tls0
(qemu) migrate tcp:otherhostname:9000
Thanks to earlier improvements to error reporting,
TLS errors can be seen 'info migrate' when doing a
detached migration. For example:
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off x-postcopy-ram: off
Migration status: failed
total time: 0 milliseconds
error description: TLS handshake failed: The TLS connection was non-properly terminated.
Or
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off x-postcopy-ram: off
Migration status: failed
total time: 0 milliseconds
error description: Certificate does not match the hostname localhost
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1461751518-12128-27-git-send-email-berrange@redhat.com>
Signed-off-by: Amit Shah <amit.shah@redhat.com>
2016-04-27 12:05:16 +02:00
|
|
|
struct SocketConnectData *data = opaque;
|
2016-04-27 12:05:02 +02:00
|
|
|
QIOChannel *sioc = QIO_CHANNEL(src);
|
2009-08-05 17:24:29 +02:00
|
|
|
|
2016-04-27 12:05:02 +02:00
|
|
|
if (err) {
|
2016-04-27 12:05:03 +02:00
|
|
|
trace_migration_socket_outgoing_error(error_get_pretty(err));
|
migration: add support for encrypting data with TLS
This extends the migration_set_incoming_channel and
migration_set_outgoing_channel methods so that they
will automatically wrap the QIOChannel in a
QIOChannelTLS instance if TLS credentials are configured
in the migration parameters.
This allows TLS to work for tcp, unix, fd and exec
migration protocols. It does not (currently) work for
RDMA since it does not use these APIs, but it is
unlikely that TLS would be desired with RDMA anyway
since it would degrade the performance to that seen
with TCP defeating the purpose of using RDMA.
On the target host, QEMU would be launched with a set
of TLS credentials for a server endpoint
$ qemu-system-x86_64 -monitor stdio -incoming defer \
-object tls-creds-x509,dir=/home/berrange/security/qemutls,endpoint=server,id=tls0 \
...other args...
To enable incoming TLS migration 2 monitor commands are
then used
(qemu) migrate_set_str_parameter tls-creds tls0
(qemu) migrate_incoming tcp:myhostname:9000
On the source host, QEMU is launched in a similar
manner but using client endpoint credentials
$ qemu-system-x86_64 -monitor stdio \
-object tls-creds-x509,dir=/home/berrange/security/qemutls,endpoint=client,id=tls0 \
...other args...
To enable outgoing TLS migration 2 monitor commands are
then used
(qemu) migrate_set_str_parameter tls-creds tls0
(qemu) migrate tcp:otherhostname:9000
Thanks to earlier improvements to error reporting,
TLS errors can be seen 'info migrate' when doing a
detached migration. For example:
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off x-postcopy-ram: off
Migration status: failed
total time: 0 milliseconds
error description: TLS handshake failed: The TLS connection was non-properly terminated.
Or
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off x-postcopy-ram: off
Migration status: failed
total time: 0 milliseconds
error description: Certificate does not match the hostname localhost
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1461751518-12128-27-git-send-email-berrange@redhat.com>
Signed-off-by: Amit Shah <amit.shah@redhat.com>
2016-04-27 12:05:16 +02:00
|
|
|
data->s->to_dst_file = NULL;
|
|
|
|
migrate_fd_error(data->s, err);
|
2012-10-03 14:05:49 +02:00
|
|
|
} else {
|
migration: add support for encrypting data with TLS
This extends the migration_set_incoming_channel and
migration_set_outgoing_channel methods so that they
will automatically wrap the QIOChannel in a
QIOChannelTLS instance if TLS credentials are configured
in the migration parameters.
This allows TLS to work for tcp, unix, fd and exec
migration protocols. It does not (currently) work for
RDMA since it does not use these APIs, but it is
unlikely that TLS would be desired with RDMA anyway
since it would degrade the performance to that seen
with TCP defeating the purpose of using RDMA.
On the target host, QEMU would be launched with a set
of TLS credentials for a server endpoint
$ qemu-system-x86_64 -monitor stdio -incoming defer \
-object tls-creds-x509,dir=/home/berrange/security/qemutls,endpoint=server,id=tls0 \
...other args...
To enable incoming TLS migration 2 monitor commands are
then used
(qemu) migrate_set_str_parameter tls-creds tls0
(qemu) migrate_incoming tcp:myhostname:9000
On the source host, QEMU is launched in a similar
manner but using client endpoint credentials
$ qemu-system-x86_64 -monitor stdio \
-object tls-creds-x509,dir=/home/berrange/security/qemutls,endpoint=client,id=tls0 \
...other args...
To enable outgoing TLS migration 2 monitor commands are
then used
(qemu) migrate_set_str_parameter tls-creds tls0
(qemu) migrate tcp:otherhostname:9000
Thanks to earlier improvements to error reporting,
TLS errors can be seen 'info migrate' when doing a
detached migration. For example:
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off x-postcopy-ram: off
Migration status: failed
total time: 0 milliseconds
error description: TLS handshake failed: The TLS connection was non-properly terminated.
Or
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off x-postcopy-ram: off
Migration status: failed
total time: 0 milliseconds
error description: Certificate does not match the hostname localhost
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1461751518-12128-27-git-send-email-berrange@redhat.com>
Signed-off-by: Amit Shah <amit.shah@redhat.com>
2016-04-27 12:05:16 +02:00
|
|
|
trace_migration_socket_outgoing_connected(data->hostname);
|
2016-06-01 12:17:14 +02:00
|
|
|
migration_channel_connect(data->s, sioc, data->hostname);
|
2009-08-05 17:24:29 +02:00
|
|
|
}
|
2016-04-27 12:05:02 +02:00
|
|
|
object_unref(src);
|
2009-08-05 17:24:29 +02:00
|
|
|
}
|
|
|
|
|
2016-04-27 12:05:03 +02:00
|
|
|
static void socket_start_outgoing_migration(MigrationState *s,
|
|
|
|
SocketAddress *saddr,
|
|
|
|
Error **errp)
|
2009-08-05 17:24:29 +02:00
|
|
|
{
|
2016-04-27 12:05:03 +02:00
|
|
|
QIOChannelSocket *sioc = qio_channel_socket_new();
|
migration: add support for encrypting data with TLS
This extends the migration_set_incoming_channel and
migration_set_outgoing_channel methods so that they
will automatically wrap the QIOChannel in a
QIOChannelTLS instance if TLS credentials are configured
in the migration parameters.
This allows TLS to work for tcp, unix, fd and exec
migration protocols. It does not (currently) work for
RDMA since it does not use these APIs, but it is
unlikely that TLS would be desired with RDMA anyway
since it would degrade the performance to that seen
with TCP defeating the purpose of using RDMA.
On the target host, QEMU would be launched with a set
of TLS credentials for a server endpoint
$ qemu-system-x86_64 -monitor stdio -incoming defer \
-object tls-creds-x509,dir=/home/berrange/security/qemutls,endpoint=server,id=tls0 \
...other args...
To enable incoming TLS migration 2 monitor commands are
then used
(qemu) migrate_set_str_parameter tls-creds tls0
(qemu) migrate_incoming tcp:myhostname:9000
On the source host, QEMU is launched in a similar
manner but using client endpoint credentials
$ qemu-system-x86_64 -monitor stdio \
-object tls-creds-x509,dir=/home/berrange/security/qemutls,endpoint=client,id=tls0 \
...other args...
To enable outgoing TLS migration 2 monitor commands are
then used
(qemu) migrate_set_str_parameter tls-creds tls0
(qemu) migrate tcp:otherhostname:9000
Thanks to earlier improvements to error reporting,
TLS errors can be seen 'info migrate' when doing a
detached migration. For example:
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off x-postcopy-ram: off
Migration status: failed
total time: 0 milliseconds
error description: TLS handshake failed: The TLS connection was non-properly terminated.
Or
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off x-postcopy-ram: off
Migration status: failed
total time: 0 milliseconds
error description: Certificate does not match the hostname localhost
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1461751518-12128-27-git-send-email-berrange@redhat.com>
Signed-off-by: Amit Shah <amit.shah@redhat.com>
2016-04-27 12:05:16 +02:00
|
|
|
struct SocketConnectData *data = g_new0(struct SocketConnectData, 1);
|
2016-07-28 10:54:34 +02:00
|
|
|
|
migration: add support for encrypting data with TLS
This extends the migration_set_incoming_channel and
migration_set_outgoing_channel methods so that they
will automatically wrap the QIOChannel in a
QIOChannelTLS instance if TLS credentials are configured
in the migration parameters.
This allows TLS to work for tcp, unix, fd and exec
migration protocols. It does not (currently) work for
RDMA since it does not use these APIs, but it is
unlikely that TLS would be desired with RDMA anyway
since it would degrade the performance to that seen
with TCP defeating the purpose of using RDMA.
On the target host, QEMU would be launched with a set
of TLS credentials for a server endpoint
$ qemu-system-x86_64 -monitor stdio -incoming defer \
-object tls-creds-x509,dir=/home/berrange/security/qemutls,endpoint=server,id=tls0 \
...other args...
To enable incoming TLS migration 2 monitor commands are
then used
(qemu) migrate_set_str_parameter tls-creds tls0
(qemu) migrate_incoming tcp:myhostname:9000
On the source host, QEMU is launched in a similar
manner but using client endpoint credentials
$ qemu-system-x86_64 -monitor stdio \
-object tls-creds-x509,dir=/home/berrange/security/qemutls,endpoint=client,id=tls0 \
...other args...
To enable outgoing TLS migration 2 monitor commands are
then used
(qemu) migrate_set_str_parameter tls-creds tls0
(qemu) migrate tcp:otherhostname:9000
Thanks to earlier improvements to error reporting,
TLS errors can be seen 'info migrate' when doing a
detached migration. For example:
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off x-postcopy-ram: off
Migration status: failed
total time: 0 milliseconds
error description: TLS handshake failed: The TLS connection was non-properly terminated.
Or
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off x-postcopy-ram: off
Migration status: failed
total time: 0 milliseconds
error description: Certificate does not match the hostname localhost
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1461751518-12128-27-git-send-email-berrange@redhat.com>
Signed-off-by: Amit Shah <amit.shah@redhat.com>
2016-04-27 12:05:16 +02:00
|
|
|
data->s = s;
|
|
|
|
if (saddr->type == SOCKET_ADDRESS_KIND_INET) {
|
|
|
|
data->hostname = g_strdup(saddr->u.inet.data->host);
|
|
|
|
}
|
2016-07-28 10:54:34 +02:00
|
|
|
|
2016-04-27 12:05:02 +02:00
|
|
|
qio_channel_socket_connect_async(sioc,
|
|
|
|
saddr,
|
2016-04-27 12:05:03 +02:00
|
|
|
socket_outgoing_migration,
|
migration: add support for encrypting data with TLS
This extends the migration_set_incoming_channel and
migration_set_outgoing_channel methods so that they
will automatically wrap the QIOChannel in a
QIOChannelTLS instance if TLS credentials are configured
in the migration parameters.
This allows TLS to work for tcp, unix, fd and exec
migration protocols. It does not (currently) work for
RDMA since it does not use these APIs, but it is
unlikely that TLS would be desired with RDMA anyway
since it would degrade the performance to that seen
with TCP defeating the purpose of using RDMA.
On the target host, QEMU would be launched with a set
of TLS credentials for a server endpoint
$ qemu-system-x86_64 -monitor stdio -incoming defer \
-object tls-creds-x509,dir=/home/berrange/security/qemutls,endpoint=server,id=tls0 \
...other args...
To enable incoming TLS migration 2 monitor commands are
then used
(qemu) migrate_set_str_parameter tls-creds tls0
(qemu) migrate_incoming tcp:myhostname:9000
On the source host, QEMU is launched in a similar
manner but using client endpoint credentials
$ qemu-system-x86_64 -monitor stdio \
-object tls-creds-x509,dir=/home/berrange/security/qemutls,endpoint=client,id=tls0 \
...other args...
To enable outgoing TLS migration 2 monitor commands are
then used
(qemu) migrate_set_str_parameter tls-creds tls0
(qemu) migrate tcp:otherhostname:9000
Thanks to earlier improvements to error reporting,
TLS errors can be seen 'info migrate' when doing a
detached migration. For example:
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off x-postcopy-ram: off
Migration status: failed
total time: 0 milliseconds
error description: TLS handshake failed: The TLS connection was non-properly terminated.
Or
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off compress: off events: off x-postcopy-ram: off
Migration status: failed
total time: 0 milliseconds
error description: Certificate does not match the hostname localhost
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1461751518-12128-27-git-send-email-berrange@redhat.com>
Signed-off-by: Amit Shah <amit.shah@redhat.com>
2016-04-27 12:05:16 +02:00
|
|
|
data,
|
|
|
|
socket_connect_data_free);
|
2016-04-27 12:05:02 +02:00
|
|
|
qapi_free_SocketAddress(saddr);
|
2009-08-05 17:24:29 +02:00
|
|
|
}
|
|
|
|
|
2016-04-27 12:05:04 +02:00
|
|
|
void tcp_start_outgoing_migration(MigrationState *s,
|
|
|
|
const char *host_port,
|
|
|
|
Error **errp)
|
|
|
|
{
|
2016-09-13 11:08:41 +02:00
|
|
|
Error *err = NULL;
|
|
|
|
SocketAddress *saddr = tcp_build_address(host_port, &err);
|
|
|
|
if (!err) {
|
|
|
|
socket_start_outgoing_migration(s, saddr, &err);
|
|
|
|
}
|
|
|
|
error_propagate(errp, err);
|
2016-04-27 12:05:04 +02:00
|
|
|
}
|
|
|
|
|
2016-04-27 12:05:03 +02:00
|
|
|
void unix_start_outgoing_migration(MigrationState *s,
|
|
|
|
const char *path,
|
|
|
|
Error **errp)
|
|
|
|
{
|
|
|
|
SocketAddress *saddr = unix_build_address(path);
|
|
|
|
socket_start_outgoing_migration(s, saddr, errp);
|
|
|
|
}
|
|
|
|
|
2016-04-27 12:05:02 +02:00
|
|
|
|
2016-04-27 12:05:03 +02:00
|
|
|
static gboolean socket_accept_incoming_migration(QIOChannel *ioc,
|
|
|
|
GIOCondition condition,
|
|
|
|
gpointer opaque)
|
2009-08-05 17:24:29 +02:00
|
|
|
{
|
2016-04-27 12:05:02 +02:00
|
|
|
QIOChannelSocket *sioc;
|
|
|
|
Error *err = NULL;
|
2009-08-05 17:24:29 +02:00
|
|
|
|
2016-04-27 12:05:02 +02:00
|
|
|
sioc = qio_channel_socket_accept(QIO_CHANNEL_SOCKET(ioc),
|
|
|
|
&err);
|
|
|
|
if (!sioc) {
|
|
|
|
error_report("could not accept migration connection (%s)",
|
|
|
|
error_get_pretty(err));
|
2009-08-05 17:24:29 +02:00
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
2016-04-27 12:05:03 +02:00
|
|
|
trace_migration_socket_incoming_accepted();
|
2016-04-27 12:05:02 +02:00
|
|
|
|
2016-06-01 12:17:14 +02:00
|
|
|
migration_channel_process_incoming(migrate_get_current(),
|
|
|
|
QIO_CHANNEL(sioc));
|
2016-04-27 12:05:02 +02:00
|
|
|
object_unref(OBJECT(sioc));
|
2012-08-07 10:50:26 +02:00
|
|
|
|
2009-08-05 17:24:29 +02:00
|
|
|
out:
|
2016-04-27 12:05:02 +02:00
|
|
|
/* Close listening socket as its no longer needed */
|
|
|
|
qio_channel_close(ioc, NULL);
|
|
|
|
return FALSE; /* unregister */
|
2009-08-05 17:24:29 +02:00
|
|
|
}
|
|
|
|
|
2016-04-27 12:05:02 +02:00
|
|
|
|
2016-04-27 12:05:03 +02:00
|
|
|
static void socket_start_incoming_migration(SocketAddress *saddr,
|
|
|
|
Error **errp)
|
2009-08-05 17:24:29 +02:00
|
|
|
{
|
2016-04-27 12:05:03 +02:00
|
|
|
QIOChannelSocket *listen_ioc = qio_channel_socket_new();
|
2009-08-05 17:24:29 +02:00
|
|
|
|
2016-04-27 12:05:02 +02:00
|
|
|
if (qio_channel_socket_listen_sync(listen_ioc, saddr, errp) < 0) {
|
|
|
|
object_unref(OBJECT(listen_ioc));
|
|
|
|
qapi_free_SocketAddress(saddr);
|
2012-10-02 18:21:18 +02:00
|
|
|
return;
|
2009-08-05 17:24:29 +02:00
|
|
|
}
|
|
|
|
|
2016-04-27 12:05:02 +02:00
|
|
|
qio_channel_add_watch(QIO_CHANNEL(listen_ioc),
|
|
|
|
G_IO_IN,
|
2016-04-27 12:05:03 +02:00
|
|
|
socket_accept_incoming_migration,
|
2016-04-27 12:05:02 +02:00
|
|
|
listen_ioc,
|
|
|
|
(GDestroyNotify)object_unref);
|
|
|
|
qapi_free_SocketAddress(saddr);
|
2009-08-05 17:24:29 +02:00
|
|
|
}
|
2016-04-27 12:05:03 +02:00
|
|
|
|
2016-04-27 12:05:04 +02:00
|
|
|
void tcp_start_incoming_migration(const char *host_port, Error **errp)
|
|
|
|
{
|
2016-09-13 11:08:41 +02:00
|
|
|
Error *err = NULL;
|
|
|
|
SocketAddress *saddr = tcp_build_address(host_port, &err);
|
|
|
|
if (!err) {
|
|
|
|
socket_start_incoming_migration(saddr, &err);
|
|
|
|
}
|
|
|
|
error_propagate(errp, err);
|
2016-04-27 12:05:04 +02:00
|
|
|
}
|
|
|
|
|
2016-04-27 12:05:03 +02:00
|
|
|
void unix_start_incoming_migration(const char *path, Error **errp)
|
|
|
|
{
|
|
|
|
SocketAddress *saddr = unix_build_address(path);
|
|
|
|
socket_start_incoming_migration(saddr, errp);
|
|
|
|
}
|