Distros: Difference between revisions

From Xen
Jump to navigationJump to search
(Created page with "=== LINUX DISTRIBUTION: WHAT TO TEST AFTER PACKAGING === - mkinitrd/mkinitramfs mkinitrd and/or mkinitramfs should be able to generate bootloader entries for Xen, see http://wik…")
 
Line 1: Line 1:
=== LINUX DISTRIBUTION: WHAT TO TEST AFTER PACKAGING ===
== LINUX DISTRIBUTION: WHAT TO TEST AFTER PACKAGING ==


- mkinitrd/mkinitramfs
=== 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.
mkinitrd and/or mkinitramfs should be able to generate bootloader entries for Xen, see [[XenParavirtOps#GRUB1_and_GRUB2_.28Booting.29|this page]] for an example.


- Dom0 support in Linux
=== 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.
The Linux kernel packaged with the distribution should be compiled with Xen support, see [[XenParavirtOps#configure_xen|this page]]. Booting the machine with Xen and the default kernel should complete successfully.


- init scripts
=== init scripts: xencommons ===
Xen relies on an init script called "xencommons" to initialize all its services.
Xen relies on an init script called '''xencommons''' to initialize all the services.
It should be executed by default at boot.
It should be executed by default at boot time.


- qemu-xen-traditional and qemu-xen
=== 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 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'''.


=== Xen udev scripts ===

The Xen udev scripts should be installed correctly: after creating the default bridge named '''xenbr0''', starting a guest with a vif, the vif should be added to the bridge automatically.

- 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;

Revision as of 14:50, 26 March 2012

LINUX DISTRIBUTION: WHAT TO TEST AFTER PACKAGING

mkinitrd/mkinitramfs

mkinitrd and/or mkinitramfs should be able to generate bootloader entries for Xen, see this page for an example.

Dom0 support in Linux

The Linux kernel packaged with the distribution should be compiled with Xen support, see this page. Booting the machine with Xen and the default kernel should complete successfully.

init scripts: xencommons

Xen relies on an init script called xencommons to initialize all the services. It should be executed by default at boot time.

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.

Xen udev scripts

The Xen udev scripts should be installed correctly: after creating the default bridge named xenbr0, starting a guest with a vif, the vif should be added to the bridge automatically.