I have just received this e-mail about a workaround for Xen in Hardy.

Cheers, Leandro.

---------- Forwarded message ----------
Subject: [Bug 204010] Workaround Procedure

I was able to get things working by doing the following:


PREREQUISITES:
==========
*The domUs are able to start
*The domUs have interfaces
*The dom0 and domUs are unable to ping each other.
* "brctl show" should show something like:
** bridge name**** bridge id**************************STP enabled******interfaces

** eth0****************** 8000.001ec93cb620****no************************pet h0
************************************************** ************************************************ vif1.0
* dom0 can run anything up to and including 2.6.24-16. Latter kernels

** have not been tested.

(note: the /gutsy is not a typo. Its a way to tell apt-get to
use a different release of ubuntu)

PROCEDURE:
=========
1. apt-get install linux-ubuntu-modules-2.6.22-14-xen/gutsy

2. apt-get install linux-image-2.6.22-14-xen/gutsy
3. apt-get install linux-restricted-modules-2.6.22-14-xen/gutsy
4. Edit the /etc/xen/*.cfg file, and replace:
****kernel******= '/boot/vmlinuz-2.6.24-15-xen'

****ramdisk**** = '/boot/initrd.img-2.6.24-15-xen'
with:
****kernel******= '/boot/vmlinuz-2.6.22-14-xen'
****ramdisk**** = '/boot/initrd.img-2.6.22-14-xen'


--
networking not working

https://bugs.launchpad.net/bugs/204010
You received this bug notification because you are a direct subscriber
of the bug.

--
Leandro Pereira de Lima e Silva
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam