Hi, I want to confirm the ovirt migration status. (This is available only usual version not developer version.) In my understanding, KVM supports migration, Qemu does not support migration at this moment. For this situation, ovirt for developer does not support migration. So we test migration. We need to use usual ovirt? Is this my understanding correct? +------+----+---+ +---+ | |Adm |Gst| |Gst| Qemu guest | |Node+---+--+------+ | | |Manag1|Manag2| KVM guest + +------------------+ | KVM | +-------------------------+ ==Developer version image= Ref qemu/migration.c migration.h in kvm-userspace start_migration, migrate_write, migrate_finish (which does not exist on qemu original code.) http://git.kernel.org/?p=virt/kvm/kvm-userspace.git;a=blob;f=qemu/migration.c;h=a64a28744e89e3fc3f9bb0319f2ae3e0b703b375;hb=HEAD Thanks Atsushi SAKAI
Atsushi SAKAI wrote:> Hi, > > I want to confirm the ovirt migration status. > (This is available only usual version not developer version.) > > In my understanding, > KVM supports migration, Qemu does not support migration at this moment. > For this situation, ovirt for developer does not support migration. > So we test migration. We need to use usual ovirt? > Is this my understanding correct?Well, no. Here's the deal: there is live migration code in upstream kvm userspace, but not in upstream qemu. What that means is that you can live migrate KVM guests, but you can *also* live migrate fully emulated guests, as long as you use the KVM binary to do it (which ovirt does). So you should be able to live migrate even when you are using the "fake" managed nodes. Chris Lalancette