Aaron Weller // Crucial Paradigm
2005-Aug-11 15:18 UTC
[Xen-users] Warning: unable to open an initial console
Hi,
I''m fairly new to Xen (just started testing it today), but I''m
having
trouble getting the Xen Kernel to start. I use the Xen binary install,
and added the following entry to Grub:
title Xen 2.0 / XenLinux 2.6
kernel /boot/xen-2.0.gz dom0_mem=131072
module /boot/vmlinuz-2.6-xen0 root=/dev/sda1 ro console=tty0 panic=5
Upon booting up, the kernel boots fine, but then freezes and displays:
Warning: unable to open an initial console
I''ve tried a few things including removing the console=tty0 line, but
have been unable to get it past this point.
This is a brand new install of CentOS 4.1, and running on a Dell 2450,
512MB RAM, SCSI, and 3com network card.
Any suggestions or help is greatly appreciated.
Thanks!
--
*Aaron Weller*
Crucial Paradigm
Business Hosting Solutions
e: aaron@crucialp.com
m: +61 414 312 399
o: +61 2 9343 4058
f: +61 2 9343 4059
w: www.crucialp.com
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi,
I''m fairly new to Xen (just started testing it today), but I''m
having
trouble getting the Xen Kernel to start. I use the Xen binary install,
and added the following entry to Grub:
title Xen 2.0 / XenLinux 2.6
kernel /boot/xen-2.0.gz dom0_mem=131072
module /boot/vmlinuz-2.6-xen0 root=/dev/sda1 ro console=tty0 panic=5
Upon booting up, the kernel boots fine, but then freezes and displays:
Warning: unable to open an initial console
I''ve tried a few things including removing the console=tty0 line, but
have been unable to get it past this point.
This is a brand new install of CentOS 4.1, and running on a Dell 2450,
512MB RAM, SCSI, and 3com network card.
Any suggestions or help is greatly appreciated.
Thanks!
--
*Aaron Weller*
Crucial Paradigm
Business Hosting Solutions
e: aaron@crucialp.com
m: +61 414 312 399
o: +61 2 9343 4058
f: +61 2 9343 4059
w: www.crucialp.com
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Michael Paesold
2005-Aug-12 16:02 UTC
Re: [Xen-users] Warning: unable to open an initial console
Aaron // LT wrote:> I''m fairly new to Xen (just started testing it today), but I''m having > trouble getting the Xen Kernel to start. I use the Xen binary install, > and added the following entry to Grub: > > title Xen 2.0 / XenLinux 2.6 > kernel /boot/xen-2.0.gz dom0_mem=131072 > module /boot/vmlinuz-2.6-xen0 root=/dev/sda1 ro console=tty0 panic=5 > > Upon booting up, the kernel boots fine, but then freezes and displays: > > Warning: unable to open an initial console > > I''ve tried a few things including removing the console=tty0 line, but have > been unable to get it past this point. > > This is a brand new install of CentOS 4.1, and running on a Dell 2450, > 512MB RAM, SCSI, and 3com network card.I have a similar problem here. I don''t think the problem is related to the console warning. This here is a server bases on the Intel SR1325 mainboard including Adaptec SATA onboard RAID. I have also installed CentOS 4.1 and the latest Xen 2.0.7 binary distribution. Linux will find the root volume to mount, then after some more messages the boot process freezes. The last message before the console warning is: kjournald starting. Commit interval 5 seconds In native boot, the ordering of the boot messages is rather different, as many of the drivers are modules and loaded only after the root partition. Could you please help me find the problem here? Should I use a serial cable to get xen console messages? Are there any xen/kernel options I could try set using grub? Best Regards, Michael Paesold _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Michael Paesold
2005-Aug-12 18:17 UTC
Re: [Xen-users] Warning: unable to open an initial console
Michael Paesold wrote:> I have a similar problem here. I don''t think the problem is related to the > console warning. This here is a server bases on the Intel SR1325 mainboard > including Adaptec SATA onboard RAID. I have also installed CentOS 4.1 and > the latest Xen 2.0.7 binary distribution. > > Linux will find the root volume to mount, then after some more messages > the boot process freezes. > > The last message before the console warning is: > kjournald starting. Commit interval 5 seconds > > In native boot, the ordering of the boot messages is rather different, as > many of the drivers are modules and loaded only after the root partition. > > Could you please help me find the problem here? Should I use a serial > cable to get xen console messages? Are there any xen/kernel options I > could try set using grub?I am very sorry for this nonsense... this was my first attempt at using CentOS 4.1 with Xen. The reason for the error was the udev issue (as explained for FedoraCore 3) in the wiki. Perhaps I should add some lines there... ? So the problem was solved by: mkinitrd --builtin=ata_piix /boot/initrd-2.6.12.3-xen0.img 2.6.12.3-xen0 and adding the initrd to the grub configuration. Just confused... Michael Paesold _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Michael Paesold
2005-Aug-13 12:54 UTC
Re: [Xen-users] Warning: unable to open an initial console
Aaron // LT wrote:>> I am very sorry for this nonsense... this was my first attempt at >> using CentOS 4.1 with Xen. The reason for the error was the udev issue >> (as explained for FedoraCore 3) in the wiki. Perhaps I should add some >> lines there... ? >> >> So the problem was solved by: >> mkinitrd --builtin=ata_piix /boot/initrd-2.6.12.3-xen0.img 2.6.12.3-xen0 >> and adding the initrd to the grub configuration. > > > Thanks, did that get it working for you? I''m guessing its the SCSI > controller which is causing the problems, I''ll see if I can do a similar > step for the SCSI controller...Yes, it worked for me. Short explaination: Similar to what is described here, the problem is udev: http://wiki.xensource.com/xenwiki/XenFaq#head-ea8b39d71e49cc16d287257de4c482f99d883097 Before udev is started, /dev/console, /dev/null etc. do not exist in the root file system. The solution is to use an initial ram disk that contains these entries. To create an initrd for the xen kernels do: cd /lib/modules # look for the correct kernel version depmod 2.6.12.3-xen0 # create module dependencies if missing # create the initrd image mkinitrd /boot/initrd-2.6.12.3-xen0.img 2.6.12.3-xen0 If mkinitrd complains that it can''t find a specific module (from /etc/modules.conf), and you know that it is compiled into the kernel directly, you can tell mkinitrd so. E.g. for the ata_piix module: mkinitrd --builtin=ata_piix /boot/initrd-2.6.12.3-xen0.img 2.6.12.3-xen0 Then add an additional line to the grub.conf file for the correct kernel: module /initrd-2.6.12.3-xen0.img or module /boot/initrd-2.6.12.3-xen0.img if you don''t have a boot partition. Hope that helps. With this additional step, both Xen 2.0.7 and the latest unstable builds work well on this hardware with CentOS 4.1. Best Regards, Michael Paesold _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users