Comment 3 for bug 260998

Xen requires a special kernel to support booting. While these kernels are built from the intrepid source package, it creates difficulties in testing backports and such since not only are you adding the hypervisor, but an updated kernel to match the changes made by xen in the kernel source.

Backports are supposed to be relatively non-disruptive. By introducing a Xen kernel update through backports, you encounter issues which may only happen on specific hardware, as well as issues which may occur while the computer is booting and so forth. This undermines the philosophyof backporters.

Looking at backports.org, it appears they only backported the hypervisor and not the kernel. This may be an acceptable solution, but I have no means which to test Xen dom0 support, nor do I think backporting the hypervisor alone given the possibility of bugs due to the old dom0 kernels in hardy and the newer hypervisors. I'm leaving this WONTFIX, but any other backports developer should reopen this if they feel they disagree with me.