Hello,
Running a fairly stock RHEL4.4 (previously RHEL4.3) system, & having
issues booting Xen. In a nutshell, it simply halts shortly after
going thru GRUB, and then automatically reboots. Last output is...
----
Booting ''Xen 3.0 / XenLinux 2.6''
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /xen-3.0.gz dom0_mem=192M
[Multiboot-elf, <0x1000000:0x87508:0x35af8>, shtab=0x1bd078,
entry=0x10000.... (line cut off)
module /vmlinuz-2.6-xen ro root=LABEL=/ console=tty0
console=ttyS1,19200n8
[Multiboot-module @ 0x1be000, 0x5f18e8 byes]
module /initrd-2.6-xen.img
[Multiboot-module @ 0x7b0000, 0x20a800 bytes]
-----
grub.conf is...
-----
# 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/sda3
# initrd /initrd-version.img
#boot=/dev/sda
default 1
timeout=80
#splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
serial --unit=1 --speed=19200
terminal --timeout=80 console serial
title Red Hat Enterprise Linux ES (2.6.9-42.0.2.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.2.EL ro root=LABEL=/ console=tty0
console=ttyS1,19200n8
initrd /initrd-2.6.9-42.0.2.EL.img
title Red Hat Enterprise Linux ES (2.6.9-42.0.2.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.2.ELsmp ro root=LABEL=/
console=tty0 console=ttyS1,19200n8
initrd /initrd-2.6.9-42.0.2.ELsmp.img
title Xen 3.0 / XenLinux 2.6
root (hd0,0)
kernel /xen-3.0.gz dom0_mem=192M
module /vmlinuz-2.6-xen ro root=LABEL=/ console=tty0
console=ttyS1,19200n8
module /initrd-2.6-xen.img
#title OpenVZ Red Hat Enterprise Linux ES (2.6.8-022stab078.14-smp)
# root (hd0,0)
# kernel /vmlinuz-2.6.8-022stab078.14-smp ro root=LABEL=/
console=tty0 console=ttyS1,19200n8
# initrd /initrd-2.6.8-022stab078.14-smp.img
title Red Hat Enterprise Linux ES (2.6.9-34.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.ELsmp ro root=LABEL=/ console=tty0
console=ttyS1,19200n8
initrd /initrd-2.6.9-34.ELsmp.img
title Red Hat Enterprise Linux ES-up (2.6.9-34.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.EL ro root=LABEL=/ console=tty0
console=ttyS1,19200n8
initrd /initrd-2.6.9-34.EL.img
-----
Listing of /boot...
-----
config-2.6.16.13-xen
message vmlinuz-2.6.16-xen3_86.1_rhel4.1
config-2.6.16-xen
message.ja vmlinuz-2.6.8-022stab078.14-smp
config-2.6.16-xen3_86.1_rhel4.1 System.map-2.6.16.13-
xen vmlinuz-2.6.9-34.EL
config-2.6.9-34.EL System.map-2.6.16-
xen vmlinuz-2.6.9-34.ELsmp
config-2.6.9-34.ELsmp System.map-2.6.16-
xen3_86.1_rhel4.1 vmlinuz-2.6.9-42.0.2.EL
config-2.6.9-42.0.2.EL System.map-2.6.8-022stab078.14-
smp vmlinuz-2.6.9-42.0.2.ELsmp
config-2.6.9-42.0.2.ELsmp
System.map-2.6.9-34.EL vmlinuz-2.6-xen
grub
System.map-2.6.9-34.ELsmp xen-3.0.2-2.gz
initrd-2.6.16-xen3_86.1_rhel4.1.img
System.map-2.6.9-42.0.2.EL xen-3.0.2-3.gz
initrd-2.6.8-022stab078.14-smp.img
System.map-2.6.9-42.0.2.ELsmp xen-3.0.2.gz
initrd-2.6.9-34.EL.img vmlinux-2.6.8-022stab078.14-
smp xen-3.0.gz
initrd-2.6.9-34.ELsmp.img vmlinux-syms-2.6.16.13-
xen xen-3.gz
initrd-2.6.9-42.0.2.EL.img vmlinux-syms-2.6.16-
xen xen.gz
initrd-2.6.9-42.0.2.ELsmp.img vmlinux-syms-2.6.16-
xen3_86.1_rhel4.1 xen-syms-3.0.2
initrd-2.6-xen.img vmlinuz-2.6.16.13-
xen xen-syms-3.0.2-2
lost+found vmlinuz-2.6.16-
xen xen-syms-3.0.2-3
-----
Let me know if you need any more information...
TIA!
Yoav
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hello,
Running a fairly stock RHEL4.4 (previously RHEL4.3) system on an dual
Opteron system, & having issues booting Xen. In a nutshell, it simply
halts shortly after going thru GRUB, and then automatically reboots.
Last output is...
----
Booting ''Xen 3.0 / XenLinux 2.6''
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /xen-3.0.gz dom0_mem=192M
[Multiboot-elf, <0x1000000:0x87508:0x35af8>, shtab=0x1bd078,
entry=0x10000.... (line cut off)
module /vmlinuz-2.6-xen ro root=LABEL=/ console=tty0
console=ttyS1,19200n8
[Multiboot-module @ 0x1be000, 0x5f18e8 byes]
module /initrd-2.6-xen.img
[Multiboot-module @ 0x7b0000, 0x20a800 bytes]
-----
grub.conf is...
-----
# 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/sda3
# initrd /initrd-version.img
#boot=/dev/sda
default 1
timeout=80
#splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
serial --unit=1 --speed=19200
terminal --timeout=80 console serial
title Red Hat Enterprise Linux ES (2.6.9-42.0.2.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.2.EL ro root=LABEL=/ console=tty0
console=ttyS1,19200n8
initrd /initrd-2.6.9-42.0.2.EL.img
title Red Hat Enterprise Linux ES (2.6.9-42.0.2.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.2.ELsmp ro root=LABEL=/
console=tty0 console=ttyS1,19200n8
initrd /initrd-2.6.9-42.0.2.ELsmp.img
title Xen 3.0 / XenLinux 2.6
root (hd0,0)
kernel /xen-3.0.gz dom0_mem=192M
module /vmlinuz-2.6-xen ro root=LABEL=/ console=tty0
console=ttyS1,19200n8
module /initrd-2.6-xen.img
#title OpenVZ Red Hat Enterprise Linux ES (2.6.8-022stab078.14-smp)
# root (hd0,0)
# kernel /vmlinuz-2.6.8-022stab078.14-smp ro root=LABEL=/
console=tty0 console=ttyS1,19200n8
# initrd /initrd-2.6.8-022stab078.14-smp.img
title Red Hat Enterprise Linux ES (2.6.9-34.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.ELsmp ro root=LABEL=/ console=tty0
console=ttyS1,19200n8
initrd /initrd-2.6.9-34.ELsmp.img
title Red Hat Enterprise Linux ES-up (2.6.9-34.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.EL ro root=LABEL=/ console=tty0
console=ttyS1,19200n8
initrd /initrd-2.6.9-34.EL.img
-----
Listing of /boot...
-----
config-2.6.16.13-xen
message vmlinuz-2.6.16-xen3_86.1_rhel4.1
config-2.6.16-xen
message.ja vmlinuz-2.6.8-022stab078.14-smp
config-2.6.16-xen3_86.1_rhel4.1 System.map-2.6.16.13-
xen vmlinuz-2.6.9-34.EL
config-2.6.9-34.EL System.map-2.6.16-
xen vmlinuz-2.6.9-34.ELsmp
config-2.6.9-34.ELsmp System.map-2.6.16-
xen3_86.1_rhel4.1 vmlinuz-2.6.9-42.0.2.EL
config-2.6.9-42.0.2.EL System.map-2.6.8-022stab078.14-
smp vmlinuz-2.6.9-42.0.2.ELsmp
config-2.6.9-42.0.2.ELsmp
System.map-2.6.9-34.EL vmlinuz-2.6-xen
grub
System.map-2.6.9-34.ELsmp xen-3.0.2-2.gz
initrd-2.6.16-xen3_86.1_rhel4.1.img
System.map-2.6.9-42.0.2.EL xen-3.0.2-3.gz
initrd-2.6.8-022stab078.14-smp.img
System.map-2.6.9-42.0.2.ELsmp xen-3.0.2.gz
initrd-2.6.9-34.EL.img vmlinux-2.6.8-022stab078.14-
smp xen-3.0.gz
initrd-2.6.9-34.ELsmp.img vmlinux-syms-2.6.16.13-
xen xen-3.gz
initrd-2.6.9-42.0.2.EL.img vmlinux-syms-2.6.16-
xen xen.gz
initrd-2.6.9-42.0.2.ELsmp.img vmlinux-syms-2.6.16-
xen3_86.1_rhel4.1 xen-syms-3.0.2
initrd-2.6-xen.img vmlinuz-2.6.16.13-
xen xen-syms-3.0.2-2
lost+found vmlinuz-2.6.16-
xen xen-syms-3.0.2-3
-----
Let me know if you need any more information...
TIA!
Yoav
_______________________________________________
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
Hi, AFAIK module /initrd-... etc is ok for domU configurations: in dom0 configuration you should use the classic (like in the redhat original configuration) line starting with initrd /initrd... let us known ivan Yoav Felberbaum wrote:> Hello, > > Running a fairly stock RHEL4.4 (previously RHEL4.3) system on an dual > Opteron system, & having issues booting Xen. In a nutshell, it simply > halts shortly after going thru GRUB, and then automatically reboots. > Last output is... > > ---- > grub.conf is... > ... > > title Red Hat Enterprise Linux ES (2.6.9-42.0.2.EL) > root (hd0,0) > kernel /vmlinuz-2.6.9-42.0.2.EL ro root=LABEL=/ console=tty0 > console=ttyS1,19200n8 > ---> initrd /initrd-2.6.9-42.0.2.EL.img> title Xen 3.0 / XenLinux 2.6 > root (hd0,0) > kernel /xen-3.0.gz dom0_mem=192M > module /vmlinuz-2.6-xen ro root=LABEL=/ console=tty0 > console=ttyS1,19200n8 > ---> module /initrd-2.6-xen.img-- www.bio.dist.unige.it phone: +39 10 353.2789 fax: +39 10 353.2948 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Wrong answer... Sorry, ignore it.
I can only see in my configuration that I''ve absolute path for kernel
and module files. I don''t know if this can help solve your problem.
regards
title Xen (2.6.16-src-xen0)
root (hd0,0)
kernel /boot/xen-3.gz vcpus=1 com1=115200,8n1 dom0_mem=131072
module /boot/vmlinuz-2.6-xen root=LABEL=/1 ro maxcpus=1
console=tty1 console=ttyS0,115200n8
module /boot/initrd-2.6-xen.img
Ivan Porro wrote:> Hi,
>
> AFAIK module /initrd-... etc is ok for domU configurations: in dom0
> configuration you should use the classic (like in the redhat original
> configuration) line starting with initrd /initrd...
>
> let us known
> ivan
>
>
> Yoav Felberbaum wrote:
>> Hello,
>>
>> Running a fairly stock RHEL4.4 (previously RHEL4.3) system on an dual
>> Opteron system, & having issues booting Xen. In a nutshell, it
simply
>> halts shortly after going thru GRUB, and then automatically reboots.
>> Last output is...
>>
>> ----
>> grub.conf is...
>> ...
>>
>> title Red Hat Enterprise Linux ES (2.6.9-42.0.2.EL)
>> root (hd0,0)
>> kernel /vmlinuz-2.6.9-42.0.2.EL ro root=LABEL=/ console=tty0
>> console=ttyS1,19200n8
>> ---> initrd /initrd-2.6.9-42.0.2.EL.img
>
>> title Xen 3.0 / XenLinux 2.6
>> root (hd0,0)
>> kernel /xen-3.0.gz dom0_mem=192M
>> module /vmlinuz-2.6-xen ro root=LABEL=/ console=tty0
>> console=ttyS1,19200n8
>> ---> module /initrd-2.6-xen.img
>
--
www.bio.dist.unige.it
phone: +39 10 353.2789
fax: +39 10 353.2948
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On 4 Sep 2006, at 12:56, Ivan Porro wrote:> Wrong answer... Sorry, ignore it. > > I can only see in my configuration that I''ve absolute path for > kernel and module files. I don''t know if this can help solve your > problem. > > regards > > title Xen (2.6.16-src-xen0) > root (hd0,0) > kernel /boot/xen-3.gz vcpus=1 com1=115200,8n1 dom0_mem=131072 > module /boot/vmlinuz-2.6-xen root=LABEL=/1 ro maxcpus=1 > console=tty1 console=ttyS0,115200n8 > module /boot/initrd-2.6-xen.imgNo joy - I get Error 15: File not found... Any other suggestions? :( Y. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yoav Felberbaum wrote:> > On 4 Sep 2006, at 12:56, Ivan Porro wrote: > >> Wrong answer... Sorry, ignore it. >> >> I can only see in my configuration that I''ve absolute path for kernel >> and module files. I don''t know if this can help solve your problem. >> >> regards >> >> title Xen (2.6.16-src-xen0) >> root (hd0,0) >> kernel /boot/xen-3.gz vcpus=1 com1=115200,8n1 dom0_mem=131072 >> module /boot/vmlinuz-2.6-xen root=LABEL=/1 ro maxcpus=1 >> console=tty1 console=ttyS0,115200n8 >> module /boot/initrd-2.6-xen.img > > No joy - I get Error 15: File not found... > > Any other suggestions? :( > > Y. > >This error is returned if the specified file name cannot be found, but everything else (like the disk/partition info) is OK. Probably your original configuration was ok in term of file path but not in term of driver content. I mean, probably, because your kernel or initrd is missing a basic driver you need in dom0 (i.e. try an "lspci" while your system is booted with redhat and verify that there is support for these devices in your xen kernel. It sound strange if you used the default kernel that should have a huge number of driver in it, but maybe you are using a particularly modern or strange hardware, like a disk controller?) rerun mkinitrd may help too (mkinitrd <location of file> <kernel version> (I''m sure it is on the manual in Install from source section) regards ivan -- www.bio.dist.unige.it phone: +39 10 353.2789 fax: +39 10 353.2948 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 4 Sep 2006, at 15:53, Ivan Porro wrote:> Yoav Felberbaum wrote: >> >> On 4 Sep 2006, at 12:56, Ivan Porro wrote: >> >>> Wrong answer... Sorry, ignore it. >>> >>> I can only see in my configuration that I''ve absolute path for >>> kernel and module files. I don''t know if this can help solve your >>> problem. >>> >>> regards >>> >>> title Xen (2.6.16-src-xen0) >>> root (hd0,0) >>> kernel /boot/xen-3.gz vcpus=1 com1=115200,8n1 dom0_mem=131072 >>> module /boot/vmlinuz-2.6-xen root=LABEL=/1 ro maxcpus=1 >>> console=tty1 console=ttyS0,115200n8 >>> module /boot/initrd-2.6-xen.img >> >> No joy - I get Error 15: File not found... >> >> Any other suggestions? :( >> >> Y. >> >> > This error is returned if the specified file name cannot be found, > but everything else (like the disk/partition info) is OK. > > Probably your original configuration was ok in term of file path > but not in term of driver content. I mean, probably, because your > kernel or initrd is missing a basic driver you need in dom0 (i.e. > try an "lspci" while your system is booted with redhat and verify > that there is support for these devices in your xen kernel. It > sound strange if you used the default kernel that should have a > huge number of driver in it, but maybe you are using a particularly > modern or strange hardware, like a disk controller?)Well, I''m running with a 3ware RAID controller but from what I understand, this SHOULD only be an issue at a later stage of booting... How do I find out which drivers comes compiled into Xen? Have had no joy in finding a full list :(> rerun mkinitrd may help too (mkinitrd <location of file> <kernel > version> (I''m sure it is on the manual in Install from source section)No joy either. Same thing happens. For what it''s worth.... --- mkinitrd initrd-2.6-xen_new.img 2.6.16-xen3_86.1_rhel4.1 --- TIA! Y. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yoav Felberbaum wrote:> > Well, I''m running with a 3ware RAID controller but from what I > understand, this SHOULD only be an issue at a later stage of > booting... How do I find out which drivers comes compiled into Xen? > Have had no joy in finding a full list :( >Yes.. it should. It should happen a Kernel panic after a "no root device found" if the controller is in charge of the problem. However, if you want you can look at config-<kernel version> and inside you''ll find several string, i.e. CONFIG_SMP=Y If they are =Y the driver is compiled in. If they''re =M they''re compiled as module and should be present in initrd if required for boot (chipset, controllers...) and if they''re IS NOT SET and commented out with # they are not present anyway in your kernel I can''t help you anymore, sorry! ivan -- www.bio.dist.unige.it phone: +39 10 353.2789 fax: +39 10 353.2948 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 5 Sep 2006, at 08:22, Ivan Porro wrote:> Yoav Felberbaum wrote: >> >> Well, I''m running with a 3ware RAID controller but from what I >> understand, this SHOULD only be an issue at a later stage of >> booting... How do I find out which drivers comes compiled into >> Xen? Have had no joy in finding a full list :( >> > Yes.. it should. It should happen a Kernel panic after a "no root > device found" if the controller is in charge of the problem. > However, if you want you can look at config-<kernel version> and > inside you''ll find several string, i.e. CONFIG_SMP=Y > > If they are =Y the driver is compiled in. If they''re =M they''re > compiled as module and should be present in initrd if required for > boot (chipset, controllers...) and if they''re IS NOT SET and > commented out with # they are not present anyway in your kernel > > I can''t help you anymore, sorry!No, it''s ok, I found the issue, but now I have a new problem :P Basically, the situation is I am using IPMI to access this remote machine over Serial-over-LAN during the early booting stage. When the other kernels loaded, they echo to the serial console with no problem. BUT the xen kernel doesn''t - when the kernel loads, IPMI goes "dead". I''ve been over & over the documentation & can''t work out why this is so. This is why I THOUGHT the xen kernel was buggy. The relevant lines are... --- default 1 timeout=80 #splashimage=(hd0,0)/grub/splash.xpm.gz #hiddenmenu serial --unit=1 --speed=19200 --word=8 --parity=no --stop=1 terminal --timeout=80 console serial ... title Red Hat Enterprise Linux ES (2.6.9-42.0.2.ELsmp) root (hd0,0) kernel /vmlinuz-2.6.9-42.0.2.ELsmp ro root=LABEL=/ console=tty0 console=ttyS1,19200n8 initrd /initrd-2.6.9-42.0.2.ELsmp.img title Xen 3.0 / XenLinux 2.6 root (hd0,0) kernel /xen-3.0.gz dom0_mem=192M com1=19200,8n1 module /vmlinuz-2.6.16-xen ro root=LABEL=/ console=tty0 console=ttyS1,19200n8 module /initrd-2.6-xen.img --- The Red Hat linux works with serial-over-LAN, but I can''t get xen working with SOL :( Any ideas? Y. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Yoav Felberbaum > Sent: 05 September 2006 18:50 > To: Ivan Porro > Cc: xen-users@lists.xensource.com > Subject: Re: [Xen-users] Booting past GRUB (RHEL4) > > > On 5 Sep 2006, at 08:22, Ivan Porro wrote: > > > Yoav Felberbaum wrote: > >> > >> Well, I''m running with a 3ware RAID controller but from what I > >> understand, this SHOULD only be an issue at a later stage of > >> booting... How do I find out which drivers comes compiled into > >> Xen? Have had no joy in finding a full list :( > >> > > Yes.. it should. It should happen a Kernel panic after a "no root > > device found" if the controller is in charge of the problem. > > However, if you want you can look at config-<kernel version> and > > inside you''ll find several string, i.e. CONFIG_SMP=Y > > > > If they are =Y the driver is compiled in. If they''re =M they''re > > compiled as module and should be present in initrd if required for > > boot (chipset, controllers...) and if they''re IS NOT SET and > > commented out with # they are not present anyway in your kernel > > > > I can''t help you anymore, sorry! > > No, it''s ok, I found the issue, but now I have a new problem :P > > Basically, the situation is I am using IPMI to access this remote > machine over Serial-over-LAN during the early booting stage. When > the other kernels loaded, they echo to the serial console with no > problem. > > BUT the xen kernel doesn''t - when the kernel loads, IPMI goes > "dead". > I''ve been over & over the documentation & can''t work out why > this is > so. This is why I THOUGHT the xen kernel was buggy. > > The relevant lines are... > --- > default 1 > timeout=80 > #splashimage=(hd0,0)/grub/splash.xpm.gz > #hiddenmenu > serial --unit=1 --speed=19200 --word=8 --parity=no --stop=1 > terminal --timeout=80 console serial > ... > title Red Hat Enterprise Linux ES (2.6.9-42.0.2.ELsmp) > root (hd0,0) > kernel /vmlinuz-2.6.9-42.0.2.ELsmp ro root=LABEL=/ > console=tty0 console=ttyS1,19200n8 > initrd /initrd-2.6.9-42.0.2.ELsmp.img > title Xen 3.0 / XenLinux 2.6 > root (hd0,0) > kernel /xen-3.0.gz dom0_mem=192M com1=19200,8n1Add "console=com1" may help here - no guarantees, but I think it should work. -- Mats _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users