Differences

This shows you the differences between two versions of the page.

--- unix:virtualization:virtlib:migrate [2022/05/19 02:09] – rodolico
+++ unix:virtualization:virtlib:migrate [2022/05/22 21:22] (current) – rodolico
@@ Line 83: / Line 83: @@
 If something breaks, fix this before you go further.
+Finally, test the virsh connection between machines. Assuming virtlib running on both machines and ssh access, this should work: <code bash>virsh -c qemu+ssh://hostname/system list</code>. This should return a list of all virtuals running on the TARGET machine.
-===== Ensure the same configuration =====
+===== Notes =====
   * Make sure you have the same bridges defined on all hypervisors, with the same names: <code bash> virsh net-list</code>
   * Make sure your paths are all the same on all hypervisors: <code bash>ls /dev/disk/by-path</code>
+  * There are several GUI and WebUI tools to do the migration, but the only one I've used (virt-manager) has some serious issues.
+    * It assumes you want to copy your block devices to the target, and fails when it tries to do it. However, I was able to shut down on one machine and start up on the second, once I had used --persistent one time to copy the config.
+    * I have some machines with the disks encrypted. The message to enter my passphrase doesn't show up on the virt-manager console screen
 ===== Test the migration =====