On Mon, 18 Oct 2010 00:59:20 -0400 (EDT) Jason Wang <jasowang@xxxxxxxxxx> wrote: > Hello guys: > > Any further suggestion which I need to improve those patches? > > I agree that there's no much tests need to be run is this way except > for migration. In order to validate the function of migration, many > tests need to be run in parallel with migration and this series is > just aimed at this. > > One major advantage of this is that it could greatly simplified the > test design and could reuse existed test cases without modification. > Without this, we must split the tests cases itself or split the > migration test and modification to existed code is also required. > > One major issue is that not all tests could be run in this way, tests > which needs to do monitor operation may not work well, but ususally > this kind of test is meaningless during migration. > > Another probably issue is that we can not control precisely when the > migration start, but it's not important to tests I post here because > the background tests are usually launch as a kind of stress and need > much more time than just a single migration to complete, so what we > need to do here is just let the migration run until the background > tests finish. > > The fact is that these tests work well and have find real issues with > migration. > > Any comments or suggestions? > Good to cover different aspects of live migration using KVM In cloud, When we are targetting for minimal downtime for migration, always we need to think about the performance impact of the resources and actions. we feel, its good to cover couple of below combinations. any state change of a VM + migration 1. migration + reading data from host devices like CD, USB 2. migrate +file trasfer 3. migrate + reboot 4. internet download + migration 5. guest is given shutdown command and in parallel live migration happens 6.hotplugging of nic, storage, memory, cpu + live migration Thanks Pradeep -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
