[xen-unstable test] 64750: regressions - FAIL

[xen-unstable test] 64750: regressions - FAIL

[osstest service owner]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 11603 bytes --]

flight 64750 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/64750/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-i386-rumpuserxen-i386 10 guest-start           fail REGR. vs. 64035
 test-amd64-amd64-i386-pvgrub 10 guest-start               fail REGR. vs. 64035
 test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm 9 debian-hvm-install fail REGR. vs. 64035

Regressions which are regarded as allowable (not blocking):
 test-amd64-amd64-rumpuserxen-amd64 15 rumpuserxen-demo-xenstorels/xenstorels.repeat fail REGR. vs. 64035
 test-armhf-armhf-xl-rtds     11 guest-start               fail REGR. vs. 64035
 test-amd64-amd64-qemuu-nested 16 debian-hvm-install/l1/l2 fail baseline untested
 test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stop             fail like 64035
 test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail like 64035
 test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 13 guest-localmigrate fail like 64035
 test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop              fail like 64035

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-xl-pvh-amd  11 guest-start                  fail   never pass
 test-armhf-armhf-libvirt-raw  9 debian-di-install            fail   never pass
 test-armhf-armhf-libvirt-xsm 12 migrate-support-check        fail   never pass
 test-armhf-armhf-libvirt-xsm 14 guest-saverestore            fail   never pass
 test-armhf-armhf-xl-arndale  12 migrate-support-check        fail   never pass
 test-armhf-armhf-xl-arndale  13 saverestore-support-check    fail   never pass
 test-amd64-amd64-libvirt-xsm 12 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass
 test-amd64-amd64-xl-pvh-intel 11 guest-start                  fail  never pass
 test-amd64-amd64-libvirt-vhd 11 migrate-support-check        fail   never pass
 test-armhf-armhf-xl-vhd       9 debian-di-install            fail   never pass
 test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stop             fail never pass
 test-armhf-armhf-libvirt     14 guest-saverestore            fail   never pass
 test-armhf-armhf-libvirt     12 migrate-support-check        fail   never pass
 test-armhf-armhf-xl-cubietruck 12 migrate-support-check        fail never pass
 test-armhf-armhf-xl-cubietruck 13 saverestore-support-check    fail never pass
 test-armhf-armhf-xl-xsm      13 saverestore-support-check    fail   never pass
 test-armhf-armhf-xl-xsm      12 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt-xsm  12 migrate-support-check        fail   never pass
 test-armhf-armhf-xl          12 migrate-support-check        fail   never pass
 test-armhf-armhf-xl          13 saverestore-support-check    fail   never pass
 test-armhf-armhf-xl-credit2  13 saverestore-support-check    fail   never pass
 test-armhf-armhf-xl-credit2  12 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass
 test-armhf-armhf-xl-multivcpu 13 saverestore-support-check    fail  never pass
 test-armhf-armhf-xl-multivcpu 12 migrate-support-check        fail  never pass
 test-amd64-amd64-libvirt     12 migrate-support-check        fail   never pass
 test-amd64-i386-xl-qemut-win7-amd64 17 guest-stop              fail never pass
 test-armhf-armhf-libvirt-qcow2  9 debian-di-install            fail never pass
 test-amd64-i386-libvirt      12 migrate-support-check        fail   never pass

version targeted for testing:
 xen                  b9730aaae72b813f0e01124e79ccc3b25509f3d3
baseline version:
 xen                  22a1fbb575df3a3a7726cdeb5ddf19cc8f60827c

Last test of basis    64035  2015-11-10 08:01:11 Z    9 days
Failing since         64149  2015-11-11 19:15:29 Z    8 days    5 attempts
Testing same since    64750  2015-11-18 14:36:14 Z    1 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@citrix.com>
  Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>
  Bob Liu <bob.liu@oracle.com>
  David Scott <dave@recoil.org>
  Feng Wu <feng.wu@intel.com>
  Ian Campbell <ian.campbell@citrix.com>
  Ian Jackson <ian.jackson@eu.citrix.com>
  Jan Beulich <jbeulich@suse.com>
  Jim Fehlig <jfehlig@suse.com>
  Jonathan Davies <jonathan.davies@citrix.com>
  Juergen Gross <jgross@suse.com>
  Oleksandr Tyshchenko <oleksandr.tyshchenko@globallogic.com>
  Razvan Cojocaru <rcojocaru@bitdefender.com>
  Riku Voipio <riku.voipio@linaro.org>
  Roger Pau Monné <roger.pau@citrix.com>
  Shannon Zhao <shannon.zhao@linaro.org>
  Simon Rowe <simon.rowe@eu.citrix.com>
  Stefano Stabellini <stefano.stabellini@eu.citrix.com>
  Wei Liu <wei.liu2@citrix.com>

jobs:
 build-amd64-xsm                                              pass
 build-armhf-xsm                                              pass
 build-i386-xsm                                               pass
 build-amd64                                                  pass
 build-armhf                                                  pass
 build-i386                                                   pass
 build-amd64-libvirt                                          pass
 build-armhf-libvirt                                          pass
 build-i386-libvirt                                           pass
 build-amd64-oldkern                                          pass
 build-i386-oldkern                                           pass
 build-amd64-prev                                             pass
 build-i386-prev                                              pass
 build-amd64-pvops                                            pass
 build-armhf-pvops                                            pass
 build-i386-pvops                                             pass
 build-amd64-rumpuserxen                                      pass
 build-i386-rumpuserxen                                       pass
 test-amd64-amd64-xl                                          pass
 test-armhf-armhf-xl                                          pass
 test-amd64-i386-xl                                           pass
 test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm                fail
 test-amd64-i386-xl-qemut-debianhvm-amd64-xsm                 pass
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm           pass
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm            pass
 test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm                pass
 test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm                 pass
 test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm        fail
 test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm         fail
 test-amd64-amd64-libvirt-xsm                                 pass
 test-armhf-armhf-libvirt-xsm                                 fail
 test-amd64-i386-libvirt-xsm                                  pass
 test-amd64-amd64-xl-xsm                                      pass
 test-armhf-armhf-xl-xsm                                      pass
 test-amd64-i386-xl-xsm                                       pass
 test-amd64-amd64-xl-pvh-amd                                  fail
 test-amd64-i386-qemut-rhel6hvm-amd                           pass
 test-amd64-i386-qemuu-rhel6hvm-amd                           pass
 test-amd64-amd64-xl-qemut-debianhvm-amd64                    pass
 test-amd64-i386-xl-qemut-debianhvm-amd64                     pass
 test-amd64-amd64-xl-qemuu-debianhvm-amd64                    pass
 test-amd64-i386-xl-qemuu-debianhvm-amd64                     pass
 test-amd64-i386-freebsd10-amd64                              pass
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         pass
 test-amd64-i386-xl-qemuu-ovmf-amd64                          pass
 test-amd64-amd64-rumpuserxen-amd64                           fail
 test-amd64-amd64-xl-qemut-win7-amd64                         fail
 test-amd64-i386-xl-qemut-win7-amd64                          fail
 test-amd64-amd64-xl-qemuu-win7-amd64                         fail
 test-amd64-i386-xl-qemuu-win7-amd64                          fail
 test-armhf-armhf-xl-arndale                                  pass
 test-amd64-amd64-xl-credit2                                  pass
 test-armhf-armhf-xl-credit2                                  pass
 test-armhf-armhf-xl-cubietruck                               pass
 test-amd64-i386-freebsd10-i386                               pass
 test-amd64-i386-rumpuserxen-i386                             fail
 test-amd64-amd64-xl-pvh-intel                                fail
 test-amd64-i386-qemut-rhel6hvm-intel                         pass
 test-amd64-i386-qemuu-rhel6hvm-intel                         pass
 test-amd64-amd64-libvirt                                     pass
 test-armhf-armhf-libvirt                                     fail
 test-amd64-i386-libvirt                                      pass
 test-amd64-amd64-migrupgrade                                 pass
 test-amd64-i386-migrupgrade                                  pass
 test-amd64-amd64-xl-multivcpu                                pass
 test-armhf-armhf-xl-multivcpu                                pass
 test-amd64-amd64-qemuu-nested                                fail
 test-amd64-amd64-pair                                        pass
 test-amd64-i386-pair                                         pass
 test-amd64-amd64-libvirt-pair                                pass
 test-amd64-i386-libvirt-pair                                 pass
 test-amd64-amd64-amd64-pvgrub                                pass
 test-amd64-amd64-i386-pvgrub                                 fail
 test-amd64-amd64-pygrub                                      pass
 test-armhf-armhf-libvirt-qcow2                               fail
 test-amd64-amd64-xl-qcow2                                    pass
 test-armhf-armhf-libvirt-raw                                 fail
 test-amd64-i386-xl-raw                                       pass
 test-amd64-amd64-xl-rtds                                     pass
 test-armhf-armhf-xl-rtds                                     fail
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1                     pass
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1                     pass
 test-amd64-amd64-libvirt-vhd                                 pass
 test-armhf-armhf-xl-vhd                                      fail
 test-amd64-amd64-xl-qemut-winxpsp3                           pass
 test-amd64-i386-xl-qemut-winxpsp3                            pass
 test-amd64-amd64-xl-qemuu-winxpsp3                           pass
 test-amd64-i386-xl-qemuu-winxpsp3                            pass


------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images

Logs, config files, etc. are available at
    http://logs.test-lab.xenproject.org/osstest/logs

Explanation of these reports, and of osstest in general, is at
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master

Test harness code can be found at
    http://xenbits.xen.org/gitweb?p=osstest.git;a=summary


Not pushing.

(No revision log; it would be 879 lines long.)


[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Nested HVM in xen-unstable tests

[Ian Jackson]

osstest service owner writes ("[xen-unstable test] 64750: regressions - FAIL"):
> flight 64750 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/64750/
...
>  test-amd64-amd64-qemuu-nested 16 debian-hvm-install/l1/l2 fail baseline untested

It appears that this new test case is failing in xen-unstable.  The
logs are here:

  http://logs.test-lab.xenproject.org/osstest/logs/64750/test-amd64-amd64-qemuu-nested/info.html

If you would like to avoid this feature regressing, you probably want
to figure out what is wrong and send patches to fix it.  In the
meantime, the test will continue to fail in osstest but this will
not block pushes and will not impede anyone else's work.


The primary failure symptom detected by osstest is visible here:

http://logs.test-lab.xenproject.org/osstest/logs/64750/test-amd64-amd64-qemuu-nested/16.ts-debian-hvm-install.log

Near the end:

  ssh: connect to host 172.16.146.31 port 22: No route to host

Searching for 172.16.146.31 from the top of that log shows this:

  2015-11-19 16:24:15 Z guest l1.guest.osstest: 5a:36:0e:ee:00:15 172.16.146.31

So, at some point during the L2 install, the L1 has fallen off the
network.  "No route to host" almost certainly means it has stopped
responding to ARP requests.

The L1's `serial console' log (actually, the log captured by the L0 on
the L1' emulated serial port) is here:

  http://logs.test-lab.xenproject.org/osstest/logs/64750/test-amd64-amd64-qemuu-nested/rimava0---var-log-xen-osstest-serial-l1.guest.osstest.log

That shows

  (XEN) *** Serial input -> Xen (type 'CTRL-x' three times to switch input to DOM0)

which is a result of ts-logs-capture sending it the debug keys (which
you can see here

  http://logs.test-lab.xenproject.org/osstest/logs/64750/test-amd64-amd64-qemuu-nested/17.ts-logs-capture.log

  2015-11-19 16:27:33 Z spawning ssh -o StrictHostKeyChecking=no -o BatchMode=yes -o ConnectTimeout=100 -o ServerAliveInterval=100 -o PasswordAuthentication=no -o ChallengeResponseAuthentication=no -o UserKnownHostsFile=tmp/t.known_hosts_64750.test-amd64-amd64-qemuu-nested root@172.16.144.42 'cat >/root/64750.test-amd64-amd64-qemuu-nested.l1.guest.osstest.serial.in'
  2015-11-19 16:27:33 Z xenuse sending request for input to Xen

So the L1 hasn't completely crashed.

During the log capture, ossstest correctly diagnoses that the L1 is
unreachable.  osstest would then normally `power cycle' the `host',
but in the version of osstest used for this test, that functionality
is broken.  This was fixed in my recent set of patches which have
passed the osstest push gate, and we will soon start to see test
reports which are using the fixed version.

You can see a similar failure with better logs here:

  http://osstest.xs.citrite.net/~osstest/testlogs/logs/38313/test-amd64-amd64-qemuu-nested/info.html


Let me know if I can do more to help point you to the right bits of
the logs, etc.  Good luck.

Regards,
Ian.

Re: Nested HVM in xen-unstable tests

[Hu, Robert]

> -----Original Message-----
> From: Ian Jackson [mailto:Ian.Jackson@eu.citrix.com]
> Sent: Friday, November 20, 2015 10:46 PM
> To: Hu, Robert <robert.hu@intel.com>
> Cc: osstest service owner <osstest-admin@xenproject.org>; Jin, Gordon
> <gordon.jin@intel.com>; xen-devel@lists.xensource.com
> Subject: Nested HVM in xen-unstable tests
> 
> osstest service owner writes ("[xen-unstable test] 64750: regressions -
> FAIL"):
> > flight 64750 xen-unstable real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/64750/
> ...
> >  test-amd64-amd64-qemuu-nested 16 debian-hvm-install/l1/l2 fail
> baseline untested
> 
> It appears that this new test case is failing in xen-unstable.  The
> logs are here:
> 
> 
> http://logs.test-lab.xenproject.org/osstest/logs/64750/test-amd64-amd64-
> qemuu-nested/info.html
[Hu, Robert] 

Thanks Ian letting us know about this.
Where can I find the related xen/qemu/dom0 kernel information?

> 
> If you would like to avoid this feature regressing, you probably want
> to figure out what is wrong and send patches to fix it.  In the
> meantime, the test will continue to fail in osstest but this will
> not block pushes and will not impede anyone else's work.
> 
[Hu, Robert] 

I thought the test failure would block related patches getting accepted.

> 
> The primary failure symptom detected by osstest is visible here:
> 
> http://logs.test-lab.xenproject.org/osstest/logs/64750/test-amd64-amd64-
> qemuu-nested/16.ts-debian-hvm-install.log
> 
> Near the end:
> 
>   ssh: connect to host 172.16.146.31 port 22: No route to host
> 
> Searching for 172.16.146.31 from the top of that log shows this:
> 
>   2015-11-19 16:24:15 Z guest l1.guest.osstest: 5a:36:0e:ee:00:15
> 172.16.146.31
> 
> So, at some point during the L2 install, the L1 has fallen off the
> network.  "No route to host" almost certainly means it has stopped
> responding to ARP requests.
> 
> The L1's `serial console' log (actually, the log captured by the L0 on
> the L1' emulated serial port) is here:
> 
> 
> http://logs.test-lab.xenproject.org/osstest/logs/64750/test-amd64-amd64-
> qemuu-nested/rimava0---var-log-xen-osstest-serial-l1.guest.osstest.log
> 
> That shows
> 
>   (XEN) *** Serial input -> Xen (type 'CTRL-x' three times to switch input to
> DOM0)
> 
> which is a result of ts-logs-capture sending it the debug keys (which
> you can see here
> 
> 
> http://logs.test-lab.xenproject.org/osstest/logs/64750/test-amd64-amd64-
> qemuu-nested/17.ts-logs-capture.log
> 
>   2015-11-19 16:27:33 Z spawning ssh -o StrictHostKeyChecking=no -o
> BatchMode=yes -o ConnectTimeout=100 -o ServerAliveInterval=100 -o
> PasswordAuthentication=no -o ChallengeResponseAuthentication=no -o
> UserKnownHostsFile=tmp/t.known_hosts_64750.test-amd64-amd64-qemuu
> -nested root@172.16.144.42
> 'cat >/root/64750.test-amd64-amd64-qemuu-nested.l1.guest.osstest.serial.i
> n'
>   2015-11-19 16:27:33 Z xenuse sending request for input to Xen
> 
> So the L1 hasn't completely crashed.
[Hu, Robert] 

Yes. Let me try to reproduce this after you tell me the Xen/qemu/dom0 version/commit id.

> 
> During the log capture, ossstest correctly diagnoses that the L1 is
> unreachable.  osstest would then normally `power cycle' the `host',
> but in the version of osstest used for this test, that functionality
> is broken.  This was fixed in my recent set of patches which have
> passed the osstest push gate, and we will soon start to see test
> reports which are using the fixed version.
[Hu, Robert] 

OK. Thanks.

> 
> You can see a similar failure with better logs here:
> 
> 
> http://osstest.xs.citrite.net/~osstest/testlogs/logs/38313/test-amd64-amd6
> 4-qemuu-nested/info.html
> 
> 
> Let me know if I can do more to help point you to the right bits of
> the logs, etc.  Good luck.
> 
> Regards,
> Ian.

Re: Nested HVM in xen-unstable tests

[Ian Campbell]

On Sun, 2015-11-22 at 06:26 +0000, Hu, Robert wrote:
> > -----Original Message-----
> > From: Ian Jackson [mailto:Ian.Jackson@eu.citrix.com]
> > Sent: Friday, November 20, 2015 10:46 PM
> > To: Hu, Robert <robert.hu@intel.com>
> > Cc: osstest service owner <osstest-admin@xenproject.org>; Jin, Gordon
> > <gordon.jin@intel.com>; xen-devel@lists.xensource.com
> > Subject: Nested HVM in xen-unstable tests
> > 
> > osstest service owner writes ("[xen-unstable test] 64750: regressions -
> > FAIL"):
> > > flight 64750 xen-unstable real [real]
> > > http://logs.test-lab.xenproject.org/osstest/logs/64750/
> > ...
> > >  test-amd64-amd64-qemuu-nested 16 debian-hvm-install/l1/l2 fail
> > baseline untested
> > 
> > It appears that this new test case is failing in xen-unstable.  The
> > logs are here:
> > 
> > 
> > http://logs.test-lab.xenproject.org/osstest/logs/64750/test-amd64-amd64
> > -
> > qemuu-nested/info.html
> [Hu, Robert] 
> 
> Thanks Ian letting us know about this.
> Where can I find the related xen/qemu/dom0 kernel information?

At the bottom of the info.html page there is a table of "Test control
variables" which contains build *buildjob variables, those links take you
to the relevant build job. The info for those jobs then contains "Test
control variables" which include the trees and revisions of things built.

Also under "Logfiles etc." there is a "build/" subdirectory with the actual
binaries, and in the case of the kernbuildjob the kernel's .config.


> > If you would like to avoid this feature regressing, you probably want
> > to figure out what is wrong and send patches to fix it.  In the
> > meantime, the test will continue to fail in osstest but this will
> > not block pushes and will not impede anyone else's work.
> > 
> [Hu, Robert] 
> 
> I thought the test failure would block related patches getting accepted.

Osstest looks for regressions and blocks patches which introduce them,
however for there to be a regression then the test needs to have been
passing first.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Nested HVM in xen-unstable tests

[Ian Campbell]

On Fri, 2015-11-20 at 14:45 +0000, Ian Jackson wrote:
> osstest service owner writes ("[xen-unstable test] 64750: regressions -
> FAIL"):
> > flight 64750 xen-unstable real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/64750/
> ...
> >  test-amd64-amd64-qemuu-nested 16 debian-hvm-install/l1/l2 fail
> > baseline untested
> 
> It appears that this new test case is failing in xen-unstable.  The
> logs are here:
> 
>   http://logs.test-lab.xenproject.org/osstest/logs/64750/test-amd64-amd64-qemuu-nested/info.html

After investigating my earlier reply to Robert I noticed that some recent
instances of test-amd64-amd64-qemuu-nested seems to have run on rimava,
which is an AMD machine.

At the very least I think we want to add hvm-intel to the host flags for
this test case, but I suspect we might also want to go one step further and
split into test-amd64-amd64-qemuu-nested-intel and  test-amd64-amd64-qemuu-
nested-amd with appropriate flags for each.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

[PATCH OSSTEST] make-flight: Run separate nested jobs on AMD and Intel

[Ian Campbell]

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.campbell@citrix.com>
Cc: "Hu, Robert" <robert.hu@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

Re: [PATCH OSSTEST] make-flight: Run separate nested jobs on AMD and Intel

[Ian Jackson]

Ian Campbell writes ("[PATCH OSSTEST] make-flight: Run separate nested jobs on AMD and Intel"):
> 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.campbell@citrix.com>
> Cc: "Hu, Robert" <robert.hu@intel.com>

Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>

Ian.

Re: [PATCH OSSTEST] make-flight: Run separate nested jobs on AMD and Intel

[Ian Jackson]

Ian Campbell writes ("[PATCH OSSTEST] make-flight: Run separate nested jobs on AMD and Intel"):
> 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.

Tested-by: Ian Jackson <ian.jackson@eu.citrix.com>

using `./standalone-generate-dump-flight-runvars xen-unstable'.

I will push this to pretest RSN, probably with some other fix(es).

Ian.

Re: [PATCH OSSTEST] make-flight: Run separate nested jobs on AMD and Intel

[Hu, Robert]

> -----Original Message-----
> From: Ian Campbell [mailto:ian.campbell@citrix.com]
> Sent: Monday, November 23, 2015 6:49 PM
> To: ian.jackson@eu.citrix.com; xen-devel@lists.xen.org
> Cc: Ian Campbell <ian.campbell@citrix.com>; Hu, Robert
> <robert.hu@intel.com>
> Subject: [PATCH OSSTEST] make-flight: Run separate nested jobs on AMD and
> Intel
> 
> 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.campbell@citrix.com>
> Cc: "Hu, Robert" <robert.hu@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 () {
[Hu, Robert] 

Aced-by: Robert Hu <robert.hu@intel.com>

And thanks!

> --
> 2.6.1