It's possible that the guest kernel dies during migration,
this will lead in many time errors like:
Unhandled VMAddressVerificationError: Cannot verify MAC-IP address
mapping using arping: 9a:95:62:c5:0d:c0 ---> 192.168.122.68
Since in fact what happened is that the guest died, hence
it's unable to request an IP to the DHCP server.
So put this verification code in 2 places:
1) Right before a round of migration, on the source vm
2) Right after we move the internal state of the source
vm object to the clone vm object
With this, we should see more meaningful test failures.
Signed-off-by: Lucas Meneghel Rodrigues <lmr@xxxxxxxxxx>
---
client/virt/kvm_vm.py | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/client/virt/kvm_vm.py b/client/virt/kvm_vm.py
index 215687c..6747c2b 100644
--- a/client/virt/kvm_vm.py
+++ b/client/virt/kvm_vm.py
@@ -1451,6 +1451,8 @@ class VM(virt_vm.BaseVM):
return
wait_for_migration()
+ self.verify_kernel_crash()
+ self.verify_alive()
# Report migration status
if mig_succeeded():
@@ -1473,6 +1475,7 @@ class VM(virt_vm.BaseVM):
error.context("after migration")
if local:
time.sleep(1)
+ self.verify_kernel_crash()
self.verify_alive()
if local and stable_check:
--
1.7.7.3
--
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
