Xen 4.12 RC test instructions
|If you come to this page before or after the Test Day is completed, your testing is still valuable, and you can use the information on this page to test, post any bugs and test reports to xen-devel@. If this page is more than two weeks old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.|
- 1 What needs to be tested
- 2 Installing
- 3 Known issues
- 4 Test instructions
- 5 Reporting Bugs (& Issues)
- 6 Reporting success
What needs to be tested
- Making sure that Xen 4.12 compiles and installs properly on different software configurations; particularly on distros
- Making sure that Xen 4.12, along with appropriately up-to-date kernels, work on different hardware.
For more ideas about what to test, please see Testing Xen.
ARM Smoke Testing
If you use ARM Hardware, which is not widely available or not rackable (and thus not part of our automated test suite), please check out Xen ARM Manual Smoke Test. Helping out to manually test ARM boards (which will only take a few minutes) will guarantee that Xen 4.12 will work on the board that you use. If you want to see which boards need testing, check Xen ARM Manual Smoke Test/Results.
Getting a RC
For the expressions/examples below, set the following bash/sh/... variable to the release candidate number (e.g. one of
rc2, ... )
RC="<release candidate number>" # rc1, rc2 ...
For RC1: RC=rc1.2 (see #RC1)
With a recent enough
git (>= 188.8.131.52), just pull from the proper tag (
4.12.0-$RC) from the main repo directly:
git clone -b 4.12.0-$RC git://xenbits.xen.org/xen.git
With an older
git version (and/or if that does not work, e.g., complaining with a message like this:
Remote branch 4.12.0-$RC not found in upstream origin, using HEAD instead), do the following:
git clone git://xenbits.xen.org/xen.git ; cd xen ; git checkout 4.12.0-$RC
Namespace changes affecting downstreams and users
- kdd (tool for debugging guest OSes with the windows kernel debugger) has been renamed to xen-kdd in order to reduce namespace pollution.
- The fsimage library used by pygrub, which does not have a stable ABI, and the corresponding python module, have been renamed to 'xenfsimage' (to reduce namespace pollution). Any out-of-tree users of this library will have to be updated.
- Remove any old versions of Xen toolstack and userspace binaries (including
- Remove any Xen-related udev files under /etc because Xen 4.12 doesn't use those anymore.
- Download and install the most recent Xen 4.12 RC, as described above. Make sure to check the
INSTALLfor changes in required development libraries and procedures. Some particular things to note:
Once you have Xen 4.12 RC installed check that you can install a guest etc and use it in the ways which you normally would, i.e. that your existing guest configurations, scripts etc still work.
For more ideas about what to test, please see Testing Xen or the sections below. Note that typically specific tests for new features will be added around RC2.
Specific ARM Test Instructions
Boards and hardware we do not test in our CI Loop
Although we do have automated Test Infrastructure for the project, we only include rackable hardware into our CI Loop. We do have a mixture of Allwinner and Exynos processors in a custom chassis. If you have one of the following boards and want to ensure it runs on Xen 4.12, please make sure you run the Xen ARM Manual Smoke Test on an RC.
Boards not tested by our CI Loop: Allwinner sun6i/A31, DRA7[J6] EVM, Exynos5410, HiKey board from 96boards.org, Mustang (XC-1), OMAP5432, Renesas R-Car H2, Versatile Express and Xilinx Zynq Ultrascale MPSoC
We are also not able to include non-production servers that require a legal agreement such as an NDA into our Test Infrastructure.
<TODO: Add Additional Feature here>
Specific x86 testing instructions
<TODO: Add Additional Feature here>
RC specific things to test
None for now.
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 (please CC the relevant maintainers and the Release Manager - julien dot grall at arm dot com).
We would love it if you could report successes by e-mailing
firstname.lastname@example.org, preferably including:
- Hardware: Please at least include the processor manufacturer (Intel/AMD). Other helpful information might include specific processor models, amount of memory, number of cores, and so on
- 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, xen-tools, drbd, &c).
- Guest operating systems: If running a Linux version, please specify whether you ran it in PV or HVM mode.
- Functionality tested: High-level would include toolstacks, and major functionality (e.g., suspend/resume, migration, pass-through, stubdomains, &c)
The following template might be helpful: should you use
Xen 4.12.0-<Some RC> for testing, please make sure you state that information!
Subject: [TESTDAY] Test report * Hardware: * Software: * Guest operating systems: * Functionality tested: * Comments:
Subject: [TESTDAY] Test report * Hardware: Dell 390's (Intel, dual-core) x15 HP (AMD, quad-core) x5 * Software: Ubuntu 10.10,11.10 Fedora 17 * Guest operating systems: Windows 8 Ubuntu 12.10,11.10 (HVM) Fedora 17 (PV) * Functionality tested: xl suspend/resume pygrub * Comments: Window 8 booting seemed a little slower than normal. Other than that, great work!