I am installing Xen on a remote server. I left the other kernels on the grub.conf and made xen the default to boot from. The box didn''t boot into Xen on reboot but I''m not sure why. Here is my Xen config file: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/hda3 # initrd /initrd-version.img #boot=/dev/hda default=2 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.9-11.EL) root (hd0,0) kernel /vmlinuz-2.6.9-11.EL ro root=LABEL=/1 initrd /initrd-2.6.9-11.EL.img title CentOS 4.0 (2.6.9-5.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.0.3.EL ro root=LABEL=/1 initrd /initrd-2.6.9-5.0.3.EL.img # title Xen 2.0 / XenLinux 2.6 kernel /xen-2.0.gz dom0_mem=131072 module /vmlinuz-2.6-xen0 root=/dev/hda3 ro console=tty0 Here is the contents of /boot config-2.6.12-xen0 initrd-2.6.9-11.EL.img System.map-2.6.12-xen0 vmlinux-syms-2.6.12-xenU vmlinuz-2.6-xen0 xen.gz config-2.6.12-xenU initrd-2.6.9-5.0.3.EL.img System.map-2.6.12-xenU vmlinuz-2.6.12-xen0 vmlinuz-2.6-xenU xen-syms-2.0-testing config-2.6.9-11.EL lost+found System.map-2.6.9-11.EL vmlinuz-2.6.12-xenU xen-2.0.gz config-2.6.9-5.0.3.EL message System.map-2.6.9-5.0.3.EL vmlinuz-2.6.9-11.EL xen-2.0-testing.gz grub message.ja vmlinux-syms-2.6.12-xen0 vmlinuz-2.6.9-5.0.3.EL xen-2.gz This is a CentOS 4.1 box. What did I do wrong? Thank you. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, Could you try following and check title Xen 2.0 / XenLinux 2.6 kernel (hd0,0)/xen-2.0.gz dom0_mem=131072 module (hd0,0)/vmlinuz-2.6-xen0 root=/dev/hda3 ro console=tty0 Regards, Sharath On 9/13/05, G. Felter <xeninfo@gmail.com> wrote:> > I am installing Xen on a remote server. I left the other kernels on the > grub.conf and made xen the default to boot from. The box didn''t boot into > Xen on reboot but I''m not sure why. Here is my Xen config file: > > # grub.conf generated by anaconda > # > # Note that you do not have to rerun grub after making changes to this > file > # NOTICE: You have a /boot partition. This means that > # all kernel and initrd paths are relative to /boot/, eg. > # root (hd0,0) > # kernel /vmlinuz-version ro root=/dev/hda3 > # initrd /initrd-version.img > #boot=/dev/hda > default=2 > timeout=5 > splashimage=(hd0,0)/grub/splash.xpm.gz > hiddenmenu > title CentOS (2.6.9-11.EL) > root (hd0,0) > kernel /vmlinuz-2.6.9-11.EL ro root=LABEL=/1 > initrd /initrd-2.6.9-11.EL.img > title CentOS 4.0 (2.6.9-5.0.3.EL) > root (hd0,0) > kernel /vmlinuz-2.6.9-5.0.3.EL ro root=LABEL=/1 > initrd /initrd-2.6.9-5.0.3.EL.img > # > title Xen 2.0 / XenLinux 2.6 > kernel /xen-2.0.gz dom0_mem=131072 > module /vmlinuz-2.6-xen0 root=/dev/hda3 ro console=tty0 > > Here is the contents of /boot > > config-2.6.12-xen0 initrd-2.6.9-11.EL.img System.map-2.6.12-xen0 > vmlinux-syms-2.6.12-xenU vmlinuz-2.6-xen0 xen.gz > config-2.6.12-xenU initrd-2.6.9-5.0.3.EL.img System.map-2.6.12-xenU > vmlinuz-2.6.12-xen0 vmlinuz-2.6-xenU xen-syms-2.0-testing > config-2.6.9-11.EL lost+found System.map-2.6.9-11.EL vmlinuz-2.6.12-xenU > xen-2.0.gz > config-2.6.9-5.0.3.EL message System.map-2.6.9-5.0.3.EL > vmlinuz-2.6.9-11.EL xen-2.0-testing.gz > grub message.ja vmlinux-syms-2.6.12-xen0 vmlinuz-2.6.9-5.0.3.EL xen-2.gz > > > This is a CentOS 4.1 box. What did I do wrong? > Thank you. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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? ---------- Forwarded message ---------- From: G. Felter <xeninfo@gmail.com> Date: Sep 12, 2005 9:58 PM Subject: Re: [Xen-users] Won''t boot to Xen, GRUB Problem To: Daniel Hulme <dh286@cam.ac.uk>, sadique@vanillanetworks.com, mccabemt@gmail.com 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. 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@cam.ac.uk> 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@lists.xensource.com http://lists.xensource.com/xen-users
> 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@cam.ac.uk> 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@lists.xensource.com http://lists.xensource.com/xen-users