Bug #80769

virsh migrate

Added by Andri Steiner over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Target version:
-
Start date:
2017-04-09
Due date:
% Done:

0%


Description

While migration of some VMs went fine, we lost some configurations (/etc/libvirt/qemu/srvXXX.xml) on the destination node. Migrated VMs where running fine on the new node, but we lost them after a node reboot because the configuration was missing.

Tasks
- check and restore missing configuration
- check migration and adjust documentation if required

History

#1 Updated by Andri Steiner over 2 years ago

root@ms08 /home/asteiner # lvdisplay | grep "LV Name" | awk '{print $3}' | sort > lv.txt
root@ms08 /home/asteiner # virsh list --all --name | sort > virsh.txt
root@ms08 /home/asteiner # diff -u virsh.txt lv.txt
=> keine fehlenden VMs

root@ms09 /home/asteiner # lvdisplay | grep "LV Name" | awk '{print $3}' | sort > lv.txt
root@ms09 /home/asteiner # virsh list --all --name | sort > virsh.txt
root@ms09 /home/asteiner # diff -u virsh.txt lv.txt
=> srv178

#2 Updated by Andri Steiner over 2 years ago

  • srv178.xml Restore ab Backup "You are browsing backup #514, which started around 4/7 05:25 (2.2 days ago)"
  • `virsh define srv178.xml`

#3 Updated by Andri Steiner over 2 years ago

  • Status changed from New to Resolved

Options --undefinesource --persistent required, updated documentation and also added and clarified other parts of migration process

#4 Updated by Steffen Gebert over 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF