<html><body><p><br><br><br><tt>kimchi-devel-bounces@ovirt.org wrote on 10/27/2015 12:00:03 PM:<br><br>> On 10/27/2015 11:13 AM, Frank Novak wrote:<br>> ><br>> ><br>> ><br>> ><br>> > kimchi-devel-bounces@ovirt.org wrote on 10/27/2015 08:31:49 AM:<br>> ><br>> > > Date: Mon, 26 Oct 2015 16:08:11 -0200<br>> > > From: <dhbarboza82@gmail.com><br>> > > To: Kimchi Devel <kimchi-devel@ovirt.org><br>> > > Subject: [Kimchi-devel] [PATCH 0/3] Live migration backend<br>> > > Message-ID: <1445882894-10208-1-git-send-email-dhbarboza82@gmail.com><br>> > ><br>> > > From: Daniel Henrique Barboza <dhbarboza82@gmail.com><br>> > ><br>> > > This patch series implements the first release of the Live (and cold!)<br>> > > migration in Kimchi.<br>> > ><br>> > > *** Requirements for a VM migration ***<br>> > ><br>> > > - shared storage. The disk/storage path must be the same at the origin<br>> > > and destination.<br>> > Is this a temporary restriction in kimchi?<br>> > We otherwise do support live migration w/ storage...<br>> ><br>> <br>> I guess I've expressed myself poorly there. What I meant was that the VM <br>> must be in the same<br>> storage pool at both hosts (shared storage). For example, a NFS/iSCSI <br>> storage pool that contains<br>> both the source and destination. The idea is that the migration process <br>> will only copy the VM<br>> RAM - the disks would be accessible by the VM at the destination from <br>> the same path.<br>> <br>> I am aware that there is an option to copy the storage (non-shared <br>> storage migration) but I've found<br>> out that it isn't that supported by Red Hat for example:<br>> <br>> <a href="https://access.redhat.com/solutions/60034">https://access.redhat.com/solutions/60034</a><br>> <br>> "Live migration with non-shared storage in RHEL6/RHEV3.* is a deprecated <br>> functionality, but under certain circunstances and with some <br>> limitations, it works fine. In RHEL7, this feature has been disabled."<br>> <br>> <br>> However, if some distro that Kimchi supports still have support for non <br>> shared migration, we can<br>> add this option as well.<br>> </tt><br><tt>well, PowerKVM at least does.. </tt><br><tt>I haven't checked whether Ubuntu or SLES KVM do..</tt><br><tt><br>> > ><br>> > > - password-less login<br>> > ><br>> > > - enough resorces in the destination host to allocate the VM<br>> > ><br>> > ><br>> > > Limitations of this first version and possible candidates for future <br>> > work:<br>> > ><br>> > > - do not automate the process of password-less login (but it is able to<br>> > > verify this condition)<br>> > ><br>> > > - due to the above limitation, the 'user' parameter value is only 'root'<br>> > > at this moment<br>> > ><br>> > > - do not verify the 'shared storage' condition<br>> > ><br>> > > - do not verify same hypervisor/arch conditions<br>> > ><br>> > > - the origin VM will shutdown after migration (not sure if can be <br>> > helped)<br>> > ><br>> > Ahh, shutdown where, if it was running on source, it should be running <br>> > on destination..<br>> > clearly it will not be on source anymore..<br>> ><br>> Yeah, that was my reasoning when seeing the VM shutting down <br>> automatically in the<br>> source after the migration was successful.<br>> <br>> <br>> <br>> <br>> Daniel<br>> <br>> <br></tt><br><br>Cheers,<br>Frank <BR>
</body></html>