qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH] migration: adding migration to/from a file


From: Daniel P. Berrange
Subject: Re: [Qemu-devel] [PATCH] migration: adding migration to/from a file
Date: Tue, 20 Jan 2009 11:53:47 +0000
User-agent: Mutt/1.4.1i

On Tue, Jan 20, 2009 at 01:32:24PM +0200, Uri Lublin wrote:
> Anthony Liguori wrote:
> >Uri Lublin wrote:
> >>Migration to file, reuses migration-to-fd.
> >>Migration from file, uses qemu-fopen directly.
> >>
> >>The saved state-file should be used only once and removed (or used
> >>with -snapshot, or a the disk-image should be copied), as the
> >>disk image is not saved, only the VM state.
> >>
> >>Also there is not point of doing a _live_ migration to file (except
> >>for debugging migration code), so I recommend to stop the VM before 
> >>migrating its state to a file.
> >>
> >>An advantage migration-to-file over savevm/loadvm is that for the latter
> >>a qcow2 is a requirement, while the former works for any image-format.
> >>
> >>Signed-off-by: Uri Lublin <address@hidden>
> >>---
> 
> >>+
> >>+MigrationState *file_start_outgoing_migration(const char *filename,
> >>+                                              int64_t bandwidth_limit,
> >>+                                              int async)
> >>+{
> >>+    FdMigrationState *s;
> >>+    int fd;
> >>+
> >>+    s = qemu_mallocz(sizeof(*s));
> >>+    if (s == NULL) {
> >>+        perror("file_migration: qemu_mallocz failed");
> >>+        term_printf("file_migration: qemu_mallocz failed");
> >>+        goto err1;
> >>+    }
> >>+
> >>+    fd = open(filename, O_WRONLY | O_CREAT | O_TRUNC, 0600);
> >>+    if (fd < 0) {
> >>+        perror("file_migration: failed to open filename");
> >>+        term_printf("file_migration: failed to open filename %s\n", 
> >>filename);
> >>+        goto err2;
> >>+    }
> >>  
> >
> >The migration code assumes that the file descriptor used is 
> >non-blocking.  In general, open() on a file system cannot produce a 
> >non-blocking file descriptor.
> 
> I can call fcntl with F_SETFL and O_NONBLOCK.

IIRC that doesn't have any effect on plain files - they'll still potentially
block on write.

Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|




reply via email to

[Prev in Thread] Current Thread [Next in Thread]