Difference between revisions of "Xen ARM Manual Smoke Test"

From Xen
 
(4 intermediate revisions by the same user not shown)
Line 7: Line 7:
 
* Test hypervisor functionalities: clone [http://xenbits.xen.org/gitweb/?p=raisin.git;a=summary| raisin] on the platform and run ./raise test
 
* Test hypervisor functionalities: clone [http://xenbits.xen.org/gitweb/?p=raisin.git;a=summary| raisin] on the platform and run ./raise test
   
* Report your findings to [http://lists.xenproject.org/cgi-bin/mailman/listinfo/xen-devel| xen-devel] (see below)
+
* Report your findings to [http://lists.xenproject.org/cgi-bin/mailman/listinfo/xen-devel| xen-devel] (see below) and/or add a quick record to [[Xen_ARM_Manual_Smoke_Test/Results]].
   
 
= Reporting Bugs (& Issues) =
 
= Reporting Bugs (& Issues) =
Line 17: Line 17:
 
* Make sure to follow the guidelines on [[Reporting Bugs against Xen]].
 
* Make sure to follow the guidelines on [[Reporting Bugs against Xen]].
   
= Reporting success =
+
= Reporting success by mail =
   
 
We would love it if you could report successes by e-mailing <code>xen-devel@lists.xen.org</code>, preferably including:
 
We would love it if you could report successes by e-mailing <code>xen-devel@lists.xen.org</code>, preferably including:
 
* '''Hardware''': Please at least include the exact board or hardware name into the test
 
* '''Hardware''': Please at least include the exact board or hardware name into the test
 
* '''Software''': If you're using a distro, the distro name and version would be the most helpful. Other helpful information might include the kernel that you're running, or other virtualization-related software you're using (e.g., libvirt).
 
* '''Software''': If you're using a distro, the distro name and version would be the most helpful. Other helpful information might include the kernel that you're running, or other virtualization-related software you're using (e.g., libvirt).
* '''Guest operating systems''': If running a Linux version, please specify whether you ran it in PV or HVM mode.
+
* '''Guest operating systems''': If you tested a guest, please specify here
 
* '''Functionality tested''': ARM Manual Smoke Test
 
* '''Functionality tested''': ARM Manual Smoke Test
   
 
<pre>
 
<pre>
Subject: [TESTDAY] Test report
+
Subject: [TESTDAY] Test report (<name of board>)
 
 
 
* Hardware:
 
* Hardware:
Line 39: Line 39:
 
</pre>
 
</pre>
   
  +
= Reporting success by wiki =
  +
The [[Xen ARM Manual Smoke Test/Results]] contains a list of people who have specific boards and also lists when these boards have been last tested. Feel free to add any test results to the table.
  +
  +
[[Category:XenARM]]
 
[[Category:Test Day]]
 
[[Category:Test Day]]

Latest revision as of 17:07, 29 March 2016

This page is about manually verifying that Xen on ARM works correctly on your ARM or ARM64 platforms. It is recommended to follow these steps during Xen test days and to verify Xen RCs (Release Candidates) on as many different platforms as possible.

  • Install Xen on ARM on your system. A lot of information about how to build Xen from source and install it on your ARM platform is available here.
  • Boot the system. Check the console logs and verify that Xen and Dom0 booted successfully. Connect to the console and verify that the system is usable (Is it responsive? Can you issue commands in Dom0?).
  • Test hypervisor functionalities: clone raisin on the platform and run ./raise test

Reporting Bugs (& Issues)

  • Use Freenode IRC channel #xentest to discuss questions interactively
  • Report any bugs / missing functionality / unexpected results.
  • Please put [TestDay] into the subject line
  • Also make sure you specify the RC number you are using
  • Make sure to follow the guidelines on Reporting Bugs against Xen.

Reporting success by mail

We would love it if you could report successes by e-mailing xen-devel@lists.xen.org, preferably including:

  • Hardware: Please at least include the exact board or hardware name into the test
  • Software: If you're using a distro, the distro name and version would be the most helpful. Other helpful information might include the kernel that you're running, or other virtualization-related software you're using (e.g., libvirt).
  • Guest operating systems: If you tested a guest, please specify here
  • Functionality tested: ARM Manual Smoke Test
Subject: [TESTDAY] Test report (<name of board>)
 
* Hardware:
 
* Software:

* Guest operating systems:

* Functionality tested: ARM Manual Smoke Test

* Comments:

Reporting success by wiki

The Xen ARM Manual Smoke Test/Results contains a list of people who have specific boards and also lists when these boards have been last tested. Feel free to add any test results to the table.