This case verifies that the guest state can be successfully transmitted to another instance. This is called migration.
How to test
- First, create guests you want to test. For broad coverage, at least one windows and one Linux guests should be tested. (Other OSes are welcome as well)
- Start running something in the guest. If you have something that stresses both the network and the disks, even better. scp'ing a file to/from the guest will do.
- take a timestamp of the system. Running the command "date" will do
- migrate the guest. You should try migrating it to localhost, as well as to a remote machine.
There are some options that are potential triggers for problems. For those, you should try starting the machine with and without them, and making sure it works for both setups
- smp: you should try UP as well as SMP guests.
- mem: you should try < 4Gb as well as > 4Gb guests (if you can)
- All tasks that you had previously started, should be still running.
- Running "date" on the migrated machine should not show any clock problems, like time going backwards (You should have approx. old_time + migration_time)
- If you are transmitting a file, you should not see a considerable decrease in the transfer rate (considering you are migrating to localhost)
- If a migration to a remote machine fails, make sure you are not seeing any firewall / selinux problems.