Kaitlin Rupert wrote:
Deepti B. Kalakeri wrote:
Verified with KVM. The test case will not pass for KVM since the guest information needs to have emulator information without which the remote migration fails. The support to pass the emulator information via VirtualSystemMigrationSettingData is not yet available.
As a workaround for verification of the tc. ------------------------------------------- 1) create a KVM VM which has the emulator information outside the tc on the comman line. 2) comment out the setup_guest() call, also comment the undefine and destroy lines at the end of the tc. 3) specify the name of the guest create in test_dom before calling local_remote_migrate().
Signed-off-by: Deepti B. Kalakeri <deeptik@linux.vnet.ibm.com>
This set looks good! I haven't had a chance to test on Xen yet. Also, if you are planning to include all of the migration types in one test, you'll want to change the test name from 06_remote_live_migration.py to something more generic.
I would prefer to have different test cases for different types, otherwise tracking the issues would be more problematic, the test case will be lengthier and complex keeping the scenarios separate gives a ready to use tc for verifying regression for different migration types if any. Thoughts ?? -- Thanks and Regards, Deepti B. Kalakeri IBM Linux Technology Center deeptik@linux.vnet.ibm.com