KVM test: migration: rely on background process instead of timing
1. Run a process in the background and make sure it keeps running after
migration (similarly to guest_s4).
2. When logging in after migration allow the procedure to take up to 30s
instead of only 10s. We can afford this because if the guest reboots during
those 30s the background process will not keep running.
Signed-off-by: Michael Goldish <mgoldish@redhat.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3928 592f7852-d20e-0410-864c-8624ca9c26a4
3 files changed