The script we finally used to do the actual migration svn path=/trunk/scripts/; revision=1662
Cancel the migration if there's an error in the middle svn path=/trunk/scripts/; revision=1633
Fault tolerance is a good thing - add some to the migration script svn path=/trunk/scripts/; revision=1632
make xvm-migrate-machine directly executable svn path=/trunk/scripts/; revision=1629
Take out do-not-run line - the script works, at least for a simple case svn path=/trunk/scripts/; revision=1628
Print out some debugging info about the VM getting migrated - just in case svn path=/trunk/scripts/; revision=1627
Make the xvm-migration-script actually do everything it needs to svn path=/trunk/scripts/; revision=1626
Fix typo in xvm-migrate-machine svn path=/trunk/scripts/; revision=1620
Eliminate the need for a deep copy of database objects during the migration with weird SQLAlchemy haxory. This requires the migration script to have its own unique version of the database library svn path=/trunk/scripts/; revision=1611
more detail on migration: moving db entries svn path=/trunk/scripts/; revision=1437
sketch out per-machine migration strategy svn path=/trunk/scripts/; revision=1429