4ed18df9df
Implement support for a "file:" uri so that a migration can be initiated directly to a file from QEMU. Unlike other migration protocol backends, the 'file' protocol cannot honour non-blocking mode. POSIX file/block storage will always report ready to read/write, regardless of how slow the underlying storage will be at servicing the request. For outgoing migration this limitation is not a serious problem as the migration data transfer always happens in a dedicated thread. It may, however, result in delays in honouring a request to cancel the migration operation. Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
24 lines
548 B
C
24 lines
548 B
C
#include "qemu/osdep.h"
|
|
#include "channel.h"
|
|
#include "io/channel-file.h"
|
|
#include "file.h"
|
|
#include "qemu/error-report.h"
|
|
|
|
|
|
void file_start_outgoing_migration(MigrationState *s, const char *fname, Error **errp)
|
|
{
|
|
QIOChannelFile *ioc;
|
|
|
|
ioc = qio_channel_file_new_path(fname, O_CREAT|O_TRUNC|O_WRONLY, 0660, errp);
|
|
if (!ioc) {
|
|
error_report("Error creating a channel");
|
|
return;
|
|
}
|
|
|
|
qio_channel_set_name(QIO_CHANNEL(ioc), "migration-file-outgoing");
|
|
migration_channel_connect(s, QIO_CHANNEL(ioc), NULL, NULL);
|
|
object_unref(OBJECT(ioc));
|
|
}
|
|
|
|
|