WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Won't boot to Xen, GRUB Problem

> I forgot to send this to the list when I sent it. /dev/console is there if
> that makes any differance. I'm pretty green with linux, I can hold my own
> with FreeBSD so some of your replies are confusing as I don't know quite
> what you are talking about. Any idea where I go from here?
<snip>
> Thanks to everyone who replied. As I mentioned the computer is a remote box
> in a datacenter. I made arrangements to reboot the box as I saw nothing in
> the logs helpful. The datacenter said the last line that appeared was:
>
>  Warning: unable to open an initial console.

Ah, that's probably the problem.  Don't worry about the TLS warnings - in 
recent RH distros you can't (and don't need to!) make them go away.  That's 
nothing to worry about.

Re the console problem: RHEL / CentOS 4 uses udev to create device nodes at 
runtime (i.e. like a DevFS, implemented as a userspace application).

Your original CentOS grub entry should have an "initrd" line.  Copy this to 
the Xen grub entry (but rename the first word to "module" instead of 
"initrd").  That should take care of the initial setup of device nodes for 
you.

I think this'll solve the problem.  You *could* make an initrd (that is, init 
ramdisk) specifically for XenLinux but you'll probably get away with the 
original one for now.

Cheers,
Mark

> Warning: currently emulating unsupported memory accesses in /lib/tls
> libraries the emulation is very slow to ensure full performance you should
> execute the following as root: mv /lib/tls /lib/tls.disabled
>
> I renamed (mv) /lib/tls to /lib/tls.disabled and did another reboot. It
> still would not boot and when the datacenter looked the last message was:
>
>  Warning: unable to open an initial console.
>
> The hands on people went home until morning, remote reboots now, so there
> is no one to select the original kernel. I havent't rebooted again.
>
> I'm running CentOS 4.1 (fresh install) on an AMD 2400 XP with IDE HD. Other
> than that I don't know too much about the box. I compiled from source and
> it is version xen-2.0-testing. Where do I go from here? Thanks
>
> Greg
>
> On 9/12/05, Daniel Hulme <dh286@xxxxxxxxx> wrote:
> > > The box didn't boot into Xen on reboot but I'm not sure why.
> >
> > What did happen? Did it give any output at all? Did it load Xen but
> > fail on starting XenLinux? Did Grub wink at you twice then blow up your
> > computer?
> >
> > Please give a little more detail. You seem to have avoided the major
> > gotchas with configuring Grub but it is hard to say what the problem is
> > without seeing the symptoms.
> >
> > --
> > Though I'm deep inside a storm it won't defeat me, Floating free.
> > Look out here comes trouble, Maybe I'm just pushing through a dream,
> > But strange how things feel quite real to me. http://surreal.istic.org/
> > That which will guide the lost child back to her mother's arms... EXILE.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>