Archived/Xen 4.2 RC2 test instructions: Difference between revisions
From Xen
Jump to navigationJump to search
No edit summary |
(Add <code> tags around commands &c) |
||
| Line 1: | Line 1: | ||
= What needs to be tested = |
= What needs to be tested = |
||
The most important feature we need tested is the new toolstack, xl. Xen 4.2 is the first version where xl is meant to be a complete replacement for xend/xm. |
The most important feature we need tested is the new toolstack, <code>xl</code>. Xen 4.2 is the first version where <code>xl</code> is meant to be a complete replacement for <code>xend</code>/<code>xm.</code> |
||
Other things that need to be tested are: |
Other things that need to be tested are: |
||
| Line 7: | Line 7: | ||
* Making sure that Xen 4.2, along with appropriately up-to-date kernels, work on different hardware. |
* Making sure that Xen 4.2, along with appropriately up-to-date kernels, work on different hardware. |
||
In general, if you try to test xl on whatever software / hardware configuration you have, that will accomplish the other two as a by-product. |
In general, if you try to test <code>xl</code> on whatever software / hardware configuration you have, that will accomplish the other two as a by-product. |
||
As is probably obvious, this is still un-released software |
WARNING: As is probably obvious, this is still un-released software. We have tested it internally, but it may contain bugs that will crash, or even corrupt your system. Don't use it on systems you can't afford to lose. |
||
= Test instructions = |
= Test instructions = |
||
* Remove any old versions of Xen toolstack binaries (including qemu). |
* Remove any old versions of Xen toolstack binaries (including <code>qemu</code>). |
||
* Download and install the most recent Xen 4.2 RC. Make sure to check the README for changes in required development libraries and procedures. Some particular things to note: |
* Download and install the most recent Xen 4.2 RC. Make sure to check the <code>README</code> for changes in required development libraries and procedures. Some particular things to note: |
||
** Xen 4.2 now uses autoconf, so after downloading, you will need to run |
** Xen 4.2 now uses autoconf, so after downloading, you will need to run <code>./configure</code> before running <code>make</code> |
||
** Xen 4.2 now provides a |
** Xen 4.2 now provides a <code>make deb</code> target as a convenience to those building from source on Debian systems. The resulting <code>.deb</code> doesn't do any set-up or check any dependencies; it is simply a convenient way to keep track of installed files and allow them to be removed or upgraded easily. |
||
* Read the [[XL|xl wiki page]] to understand what xl is, and what differences are expected between xm and xl. |
* Read the [[XL|xl wiki page]] to understand what <code>xl</code> is, and what differences are expected between <code>xm</code> and <code>xl</code>. |
||
** In particular, xend typically did network setup (i.e., bridging, &c), while xl does not. So you |
** In particular, <code>xend</code> typically did network setup (i.e., bridging, &c), while <code>xl</code> does not. So you will need to set up your networking through the standard distro tools. |
||
** For less common commands, check the xl man page to make sure names or argument conventions haven't changed. |
** For less common commands, check the <code>xl</code> man page to make sure names or argument conventions haven't changed. |
||
* Try to use xl for things that you used to use xm for. |
* Try to use <code>xl</code> for things that you used to use <code>xm</code> for. |
||
* Report any missing functionality / unexpected results. Make sure to follow the guidelines on [[Reporting Bugs against Xen]]. |
* Report any missing functionality / unexpected results. Make sure to follow the guidelines on [[Reporting Bugs against Xen]]. |
||
Revision as of 13:17, 2 August 2012
What needs to be tested
The most important feature we need tested is the new toolstack, xl. Xen 4.2 is the first version where xl is meant to be a complete replacement for xend/xm.
Other things that need to be tested are:
- Making sure that Xen 4.2 compiles and installs properly on different software configurations; particularly on distros
- Making sure that Xen 4.2, along with appropriately up-to-date kernels, work on different hardware.
In general, if you try to test xl on whatever software / hardware configuration you have, that will accomplish the other two as a by-product.
WARNING: As is probably obvious, this is still un-released software. We have tested it internally, but it may contain bugs that will crash, or even corrupt your system. Don't use it on systems you can't afford to lose.
Test instructions
- Remove any old versions of Xen toolstack binaries (including
qemu). - Download and install the most recent Xen 4.2 RC. Make sure to check the
READMEfor changes in required development libraries and procedures. Some particular things to note:- Xen 4.2 now uses autoconf, so after downloading, you will need to run
./configurebefore runningmake - Xen 4.2 now provides a
make debtarget as a convenience to those building from source on Debian systems. The resulting.debdoesn't do any set-up or check any dependencies; it is simply a convenient way to keep track of installed files and allow them to be removed or upgraded easily.
- Xen 4.2 now uses autoconf, so after downloading, you will need to run
- Read the xl wiki page to understand what
xlis, and what differences are expected betweenxmandxl.- In particular,
xendtypically did network setup (i.e., bridging, &c), whilexldoes not. So you will need to set up your networking through the standard distro tools. - For less common commands, check the
xlman page to make sure names or argument conventions haven't changed.
- In particular,
- Try to use
xlfor things that you used to usexmfor.
- Report any missing functionality / unexpected results. Make sure to follow the guidelines on Reporting Bugs against Xen.
