LINUX DISTRIBUTION: WHAT TO TEST AFTER PACKAGING
- mkinitrd/mkinitramfs mkinitrd and/or mkinitramfs should be able to generate bootloader entries for Xen, see http://wiki.xensource.com/xenwiki/XenParavirtOps.html#head-ddcd55ead3979134d08f4688c93db74137dd5b66 for an example.
- Dom0 support in Linux The Linux kernel packaged with the distribution should be compiled with Xen support, see http://wiki.xensource.com/xenwiki/XenParavirtOps.html#head-6f737df8014f2223f274410565c6ee477620242b. Booting the machine with Xen and the default kernel should complete successfully.
- init scripts Xen relies on an init script called "xencommons" to initialize all its services. It should be executed by default at boot.
- qemu-xen-traditional and qemu-xen The two device model binaries Xen relies on should be installed in the location where Xl expect them to be, that by default is /usr/lib/xen/bin, and can be changed modifying tools/libxl/_libxl_paths.h.
- the Xen udev scripts have been installed correctly: after creating a bridge named "xenbr0", if starting a guest with a vif, the vif gets added to the default bridge automatically;