I am trying to run my old Ubuntu 6.06 on a newer 8.04 with backported XEN 3.3
I have tried a million different kernels.
The closest I got was booting up to when getty should present a console, i.e. just kernel messages, then nothing on the XEN console.
I can ping the domU, but not SSH into it.
I have tried kernels from within the domU filesystem with pygrub, XEN kernels from 8.10, 8.04. I have also tried compiling XEN kernels myself and point them out directly in the domU config file. I tried downloading a precompiled kernel from XEN.org. All these failed with various version of "can not load" messages. (Some disguised as can not allocate memory errors.)
Hardware is 32 bit Pentium IV. (Not 64 bit capable.)
Update: I waited a looong time (maybe half an hour) and now I can login. However I am met by a lot of:
-bash: /dev/null: Permission denied
-bash: /dev/null: Permission denied
-bash: /dev/null: Permission denied
-bash: /dev/null: Permission denied
-bash: /dev/null: Permission denied
-bash: /dev/null: Permission denied
-bash: /dev/null: Permission denied
-bash: /dev/null: Permission denied
-bash: /dev/null: Permission denied
-bash: /dev/null: Permission denied
Hitting CTRL-C got me a prompt, so things seem to work.
I strongly suspect you're boned. The old version of Xen included in Dapper won't operate with the newer hypervisor, and Dapper won't run on a newer kernel (blame udev). Get yourself a HVM-capable box and run it fully-virtualised.
Okey this works. But /dev/null gets wrong permissions, so I patched /etc/init.d/bootmisc to do chmod a+rw /dev/null
On the Dapper 6.06 I put 2.6.24-25-xen from the 8.04 dom0 in the Dapper /boot/ and ran update-grub.
It then boots properly via pygrub. A LOT of kernel warnings on the console and no prompt on the console, but at least SSH works. After waiting a while.
On both Dapper domU and Hardy dom0 I run the same kernel: