<html><body><p><br><br><br><tt>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.</tt><br><tt>Is this a temporary restriction in kimchi? </tt><br><tt>We otherwise do support live migration w/ storage...<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 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 helped)<br>> <br>Ahh, shutdown where, if it was running on source, it should be running on destination..</tt><br><tt>clearly it will not be on source anymore.. </tt><br><tt>> <br>> <br></tt><br><br>Cheers,<br>Frank <BR>
</body></html>