search for: qemu_migr

...627bb3b The problem is, if you have two or more disks that need to be copied over to the destination, the @server_started variable is not set after the first iteration of the "for (i = 0; i < vm->def->ndisks; i++)" loop. I think this should be the fix: diff --git i/src/qemu/qemu_migration.c w/src/qemu/qemu_migration.c index 2f5d61f8e7..6f764b0c73 100644 --- i/src/qemu/qemu_migration.c +++ w/src/qemu/qemu_migration.c @@ -479,9 +479,11 @@ qemuMigrationDstStartNBDServer(virQEMUDriverPtr driver, QEMU_ASYNC_JOB_MIGRATION_IN) < 0) goto cleanup; - if (!serve...

On libvirt 6.8.0 and qemu 5.1.0, when trying to live migrate "error: internal error: Failed to reserve port" error is received and migration does not succeed: virsh # migrate cartridge qemu+tls://ratchet.lan/system --live --persistent --undefinesource --copy-storage-all --verbose error: internal error: Failed to reserve port 49153 virsh # On target host with debug logs, nothing

Hi, when a normally running VM is migrated, libvirt sends VIR_DOMAIN_EVENT_RESUMED_MIGRATED event on the destination once the migration completes. I can see that when a paused VM is migrated, libvirt sends VIR_DOMAIN_EVENT_SUSPENDED_PAUSED instead. Since there seems to be nothing migration specific about VIR_DOMAIN_EVENT_SUSPENDED_PAUSED event, my question is: Is it safe to assume on the

Hello, I'd like to live migration with snapshots. But it doesn't work. It comes out a message "cannot migrate domain with 1 snapshots" Then I try to trace the code(Libvirt 0.9.8 to 1.0.3), I find out the code in src/qemu/qemu_migration.c @ Line 1395 - 1440 (Libvirt 1.0.3) It will check the VM which has snapshots or not. I just curious about this limitation, why the VM can't live migration with snapshots? What happen if I skip this check? Does it has any suggestion way or virsh command with options to do live migratio...

...emu-system-x86_64: load of migration failed: Invalid argument This is both with UEFI and BIOS guests. I understand that newer ways of migrating non shared disks is via NBD directly with QEMU, however I am certain that this used to work before libvirt 6.0. There is a series of commits to /src/qemu/qemu_migration.c on Dec 8, 2019, could they have something to do with this? Is migration of non shared disks supported and supposed to work in tunneled mode or is it not a supported configuration and native NBD directly with QEMU should be used in all cases? Thanks in advance! Full qemu log on receiving h...

...gic block migration was deemed a > legacy feature. > > > > I understand that newer ways of migrating non shared disks is via NBD > > directly with QEMU, however I am certain > > that this used to work before libvirt 6.0. There is a series of > > commits to /src/qemu/qemu_migration.c on Dec 8, 2019, > > could they have something to do with this? > > I presume those are my commits which fix the NBD migration though. > Unfortunately they can't fix the old one. > > > Is migration of non shared disks supported and supposed to work in > > tun...

Hi Eric, Please see the blew: On Wed, Feb 11, 2015 at 3:12 PM, Eric Blake <eblake@redhat.com> wrote: > On 02/11/2015 02:07 PM, Edward Young wrote: > >>> What if this vm has a number of disk-only external snapshots? In the > >>> current version, how can live migrate this vm? > >> > >> Are the snapshots based on shared storage, or local-only

...t safe to > assume on the destination that this event signals completion of the > incoming migration (unless VIR_DOMAIN_EVENT_RESUMED_MIGRATED is received > before)? Yes. This is the code that handles the finish phase of migration: https://libvirt.org/git/?p=libvirt.git;a=blob;f=src/qemu/qemu_migration.c;h=29d228a8d9345ec8e2853571444614008a95e914;hb=HEAD#l5105 which can be read as the following pseudo code: if (postCopy) sendEvent(VIR_DOMAIN_EVENT_RESUMED_MIGRATED); if (domain.paused) sendEvent(VIR_DOMAIN_EVENT_SUSPENDED_PAUSED); Michal

...e those two. Unfortunately automagic block migration was deemed a legacy feature. > I understand that newer ways of migrating non shared disks is via NBD > directly with QEMU, however I am certain > that this used to work before libvirt 6.0. There is a series of > commits to /src/qemu/qemu_migration.c on Dec 8, 2019, > could they have something to do with this? I presume those are my commits which fix the NBD migration though. Unfortunately they can't fix the old one. > Is migration of non shared disks supported and supposed to work in > tunneled mode or is it not a support...

...you provide me an example or point me to a link > about how to use this function? It's all done under the hood as part of the implementation of 'virsh migrate --copy-source-*', if done as part of migration. But if you want to manually recreate the steps, the source code in src/qemu/qemu_migration.c shows the QMP commands used to set up the NBD server on the destination, then the mirroring is done with equivalent of the 'virsh blockcopy' command pointing to the NBD server as the destination. > > Sorry to take you so much time to answer my questions. I appreciate it >...

...you are allowed to make more than one API call, the solution is already available; maybe we should patch virsh to learn how to make the series of API calls, to automate what I will describe below. > > Then I try to trace the code(Libvirt 0.9.8 to 1.0.3), I find out the code > in src/qemu/qemu_migration.c @ Line 1395 - 1440 (Libvirt 1.0.3) It's still unimplemented at the libvirt level, even in libvirt.git. > > It will check the VM which has snapshots or not. > > I just curious about this limitation, why the VM can't live migration with > snapshots? Doing it all in on...

...st use rbd locks natively. Or, is that not implemented either? Thanks for your help. Cheers, Brian [1] <http://ceph.com/docs/master/rbd/libvirt/#configuring-the-vm> [2] <https://www.redhat.com/archives/libvirt-users/2014-January/msg00058.html> [3] <https://libvirt.org/hooks.html#qemu_migration>

...nted > either? > > Thanks for your help. > > Cheers, > Brian > > [1] <http://ceph.com/docs/master/rbd/libvirt/#configuring-the-vm> > [2] > <https://www.redhat.com/archives/libvirt-users/2014-January/msg00058.html> > [3] <https://libvirt.org/hooks.html#qemu_migration> > > > _______________________________________________ > libvirt-users mailing list > libvirt-users@redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users >

...ough it is inefficient). Please correct me if I'm wrong. Is there a way to achieve this migration via unix socket functionality this using Libvirt? Also, is there a reason why the migration uri is limited to tcp/rdma Thanks! - David [1] https://github.com/libvirt/libvirt/blob/master/src/qemu/qemu_migration.c#L2798