this works for dom0, but the 'U' kernel needs it's own modules (which shouldn't be copied automatically to /lib/modules).
Is it possible to change the full names of the kernels to 2.4.26-xen0 and 2.4.26-xenU for domain 0 and >0 respectively? At least that way the modules could be copied to /lib/modules even if they would never actually be used from there.
I think i'm getting closer to starting another domain > 0. I just started it, then a few seconds later xend wrote a message about netif and then I lost my remote ssh connection to domain0. I assume that this is the bridge problem you described earlier.
Actually I have just found that I can connect to the other domain. For some reason eth0 has grabbed a dhcp address even though /etc/network/interfaces tells it to have a static address. But for today, i'll still call it success!
*yay*
James
> In addition to this, what would be the best way to deal with the modules? I understand the original config doesn't use modules but i've added a few things to it and so have modules to deal with. Ideally 'make world' would install the modules to a folder which can be installed on the other domains later...
I've updated the top level Makefile:
"make world" should build and install modules under ./install/lib/modules.
"make install" should copy them into /lib/modules/
Ian