On Thu, 2007-07-05 at 11:36 +0200, Galevsky wrote:
> Many thanks for you suggestion. I tried a boot with no fall back, but
> nothing added neither to boot.log nor to dmesg. I am sure to target
> the right kernel image with no typo into grub.conf . This new kernel
> is a =xen-sources-2.6.16.49, and I configured it making an oldconfig
> based on current =gentoo-sources-2.6.20 running kernel. So, errors
> cannot come from drivers or such things, but specific xen options.
> Does anyone know any xen option able to prevent the kernel to boot up
> ?
I guess I (still) don't understand what your issue is. So I went back
and read your original post. Maybe I misunderstood it.
* What do you mean by "remote host"?
* If your box "does not boot" how would you expect to see a
boot.log or dmesg? They don't exist if the system has not
booted. In fact "does not boot" implies that you can't even log
in to check for dmesg or boot logs. Perhaps you can explain
what it is exactly you mean by "does not boot".
* Usually there is an error message on the console if there is a
boot loader/kernel issue with booting.
* Also you never posted your grub.conf.
So hopefully you can come up with a specific explanation of "does not
boot" as well as your config and any console messages you get. Else
this becomes a "blind leading the blind" issue.
--
Albert W. Hopkins
--
[EMAIL PROTECTED] mailing list
