nested HVM relies heavily on the underlying HVM implementation, which
is different for Intel and AMD and therefore worth testing separately.
Currently test-amd64-amd64-qemuu-nested is not tied to any specific
vendor, split it into -amd and -intel jobs and set the host flags
appropriately.
Signed-off-by: Ian Campbell <ian.campb...@citrix.com>
Cc: "Hu, Robert" <robert...@intel.com>
---
make-flight | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/make-flight b/make-flight
index 6f462ad..6b2b3ea 100755
--- a/make-flight
+++ b/make-flight
@@ -269,7 +269,9 @@ do_hvm_debian_nested_tests () {
xen-4.3-testing) return;;
esac
- job_create_test test-$xenarch$kern-$dom0arch$qemuu_suffix-nested \
+ for cpuvendor in amd intel; do
+
+ job_create_test
test-$xenarch$kern-$dom0arch$qemuu_suffix-nested-$cpuvendor \
test-nested xl $xenarch $dom0arch $qemuu_runvar \
l1_image=$(usual_debianhvm_image amd64) \
l1_vifmodel='e1000' \
@@ -277,7 +279,9 @@ do_hvm_debian_nested_tests () {
l1_enable_nestedhvm='true' \
l2_image=$(usual_debianhvm_image amd64) \
bios=$bios \
- all_hostflags=$most_hostflags,hvm
+ all_hostflags=$most_hostflags,hvm-$cpuvendor
+
+ done
}
branch_debianhvm_arch () {
--
2.6.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
