Description of problem:
1. http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/chap-Virtualization_Administration_Guide-KVM_live_migration.html
Chapter 4. KVM live migration

in sentence:
"KVM also estimates transfer speed during migration, so when the remaining amount of data to transfer will take a certain configurable period of time (10ms by default), KVM stops the original guest, transfers the remaining data, and resumes the guest on the destination host."

KVM stops the original guest -> KVM suspends the original guest

4.1. Live migration requirements

in sentence:
"Both systems must have identical network configurations. All bridging and network configurations must be exactly the same on both hosts. "
"Shared storage must mount at the same location on source and destination systems. The mounted directory name must be identical."

Now migration can succeed with different network configurations and mount dir with the help of --xml option or pre-hooks when doing migration
Even with out shared storage, migration can still succeed with --copy-storage-all when doing migration

The shared storage, identical network interface and mount dir are required necessary when use virt-manager to do migration

4.3. Shared storage example: NFS for a simple migration

in sentence:
"Warning
Whichever directory is chosen for the guests must be exactly the same on host and guest. This applies to all types of shared storage. The directory must be the same or the migration will fail."

Same as above

2. http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/chap-Virtualization_Administration_Guide-Troubleshooting.html
Chapter 22. Troubleshooting

22.6. Enabling Intel VT-x and AMD-V virtualization hardware extensions in BIOS

in sentence:
"When the machine has booted, run cat /proc/cpuinfo | grep "vmx svm". If the command outputs, the virtualization extensions are now enabled. If there is no output your system may not have the virtualization extensions or the correct BIOS setting enabled."

run cat /proc/cpuinfo |grep "vmx svm" -> run cat /proc/cpuinfo |grep -E "vmx|svm"


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: