Hi guys~ Isn't it a problem to you guys?
And one more thing. The program architecture limits that whatever option I want to test, I always have to migrate the vm to destination and migrate it back. But what if I only want to test once? So I'm thinking maybe we can change the test flow like this: 1. construct a migrate command. 2. migrate vm to destination. 3. destroy and undefine(if necessary) vm on destination. 4. recover source host environment. How about that? Please comment, thanks! :) On 02/13/2012 05:01 PM, tangchen wrote: > Hi Chris~ > > There may be a little problem in virsh_migrate.py test. > > I did the test with the following environment: > source host: 192.168.1.40 > destination host: 192.168.1.30 > > I cancelled the test when "there" had finished, but "back" didn't start. > The second time I run the test, I got this error: > > ERROR| Start VM vm1 failed: > Command </usr/bin/virsh -c qemu+ssh://192.168.1.30/system start vm1> failed, > rc=1, Command returned non-zero exit status > * Command: > /usr/bin/virsh -c qemu+ssh://192.168.1.30/system start vm1 > Exit status: 1 > > I found that when "there" was finished, vm.connect_uri was set to > 192.168.1.30, and it remained. > So "there" and "back" must be run in pairs. > > I am wondering if this is a good idea. If there is something wrong within > "there", the environment will be changed. > And the other tests may be influenced. > > -- Best Regards, Tang chen _______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
