Hi - thanks for the reply! On 12/18/06, Daniel P. Berrange <berrange@xxxxxxxxxx> wrote:
Most likely not got the correct set of modules built into the initrd. Upstream Xensource configs have most things built statically into the monolithic kernel.
Upstream Xen uses a lot of modules, but I rebuilt the sources without using modules. As that already worked, I did not yet try with the default xensource binaries - I gonna try that later and see if it also works, or if I just by accident built the only kernel allowing me to run debian on fedora.
Fedora practice is to build everything as a module whenever possible, so we do this on Xen kernels, as well as baremetal. Or perhaps the Debian kernel utils aren't new enough to work on a 2.6.18 kernel ?
Maybe, but sounds unlikely - when running on Debian, I use the debian Xen kernel version 2.6.17. but they also provide a 2.6.18 series kernel for non-xen and xen. So the tools for these kernek Versions must be there.
Finally, are there any SELinux AVC error messages in Dom0 logs ?
I don't see many selinux messages, I admit I have disabled selinux (I'm used to this from older fedora versions). But what I see now is that the dom0 messages log is full of "4gb seg fixup, process ..." messages. On xen-users there is a hint on setting hwcap 0 segneg, but this is already done by a file in /etc/ld.so.conf, provided by the Fedora xen packages I guess. I also tried further with a Fedora guest installed with yum, and this works in the meantime. Seems I probably did something wrong before, too hectic, because now it looks like making an own initrd with --with=xennet and --preload=xenblk seemed to help here. When this is running, also in the domU the logs and console are filled with the 4g seg fixup messages. Still, with including these modules, Debian is hanging at boot after printing "Starting periodic command scheduler: crond." Nothing happening anymore after this point. Henning -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
