I am getting the following error on boot on a new install Centos 51:
#/bin/sh ro no such file or directory
then a kernel panic
I have traced it to the call ''switchroot'' in the init script
in the initrd.
the exact same build without zen has no problems.
the boot messages look like:
Attaching to iSCSI storage
iscsistart: transport class version 2.0-724. iscsid version 2.0-865
iscsistart: version 2.0-865
scsi0 : iSCSI Initiator over TCP/IP
iscsistart: connection1:0 is operational now
Vendor: IET Model: Controler Rev: 0001
Type: RAID ANSI SCSI revision: 05
Vendor Model: VIRTUAL-DISK Rev: 0001
Type: Direct -Access ANSI SCSI revision: 05
SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write back
SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write back
sda: sda1
sd 0:0:0:1: Attached scsi disk sda
Waiting for driver initialization
Scanning and configuring dmraid supported devices
Create root device
Mounting root filesystem.
kjournaled starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with orded data mode.
Setting up other filesystems.
Setting up new root fs
no fstab.sys, mounting internal defaults
Copying DHCP lease
Switching to new root and running init
#/bin/sh ro no such file or directory
/tftpboot/pxelinux.cfg/default .....
default iscsi_root_xen
prompt 0
label manual_install
KERNEL /Centos/51/kickstart/vmlinuz
APPEND initrd=/Centos/51/kickstart/initrd.img
label kickstart_xen
KERNEL /Centos/51/kickstart/vmlinuz
APPEND initrd=/Centos/51/kickstart/initrd.img
kshttp://192.168.1.202/anaconda-ks.cfg ksdevice=link noipv6
label kickstart_noxen
KERNEL /Centos/51/kickstart/vmlinuz
APPEND initrd=/Centos/51/kickstart/initrd.img
kshttp://192.168.1.202/anaconda-ks.noxen.cfg ksdevice=link noipv6
label iscsi_root_xen
KERNEL mboot.c32
APPEND /Centos/boot/xen.gz-2.6.18-53.el5 --- /Centos/boot/vmlinuz-
2.6.18-53.el5xen ro root=LABEL=/ noipv6 --- /Centos/boot/initrd-
2.6.18-53.el5xen.img
label iscsi_root_noxen
KERNEL /Centos/boot/vmlinuz-2.6.18-53.el5
APPEND initrd=/Centos/boot/initrd-2.6.18-53.el5.img ro root=LABEL=/
noipv6
the xen and the noxen have different iscsi partitions and only one is
activated at a time.
the xen and noxen kickstarts are the same execpt the xen includes the
package @Virtualization
Any ideas?
attached is the anaconda generated init inside initrd.
--
Joe Royall
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Am Monday, den 31 March hub Joe Royall folgendes in die Tasten: [...]> Switching to new root and running init > #/bin/sh ro no such file or directory[...]> attached is the anaconda generated init inside initrd.What type of file in ''switchroot'' called at the end of init? I would guess it''s a shell script. I guess further that it somehow fiddles around with the kernel parameters (''ro'') and that it would expect something diffent there... So if I''m right with the first guess, can you post the contents of the script here? Ciao Max -- Follow the white penguin. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Joe Royall wrote:> > I am getting the following error on boot on a new install Centos 51: > > #/bin/sh ro no such file or directory > then a kernel panic > > I have traced it to the call ''switchroot'' in the init script > in the initrd. > > the exact same build without zen has no problems. > > the boot messages look like: > > Attaching to iSCSI storage > iscsistart: transport class version 2.0-724. iscsid version 2.0-865 > iscsistart: version 2.0-865 > scsi0 : iSCSI Initiator over TCP/IP > iscsistart: connection1:0 is operational now > Vendor: IET Model: Controler Rev: 0001 > Type: RAID ANSI SCSI revision: 05 > Vendor Model: VIRTUAL-DISK Rev: 0001 > Type: Direct -Access ANSI SCSI revision: 05 > SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB) > sda: Write Protect is off > SCSI device sda: drive cache: write back > SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB) > sda: Write Protect is off > SCSI device sda: drive cache: write back > sda: sda1 > sd 0:0:0:1: Attached scsi disk sda > Waiting for driver initialization > Scanning and configuring dmraid supported devices > Create root device > Mounting root filesystem. > kjournaled starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with orded data mode. > Setting up other filesystems. > Setting up new root fs > no fstab.sys, mounting internal defaults > Copying DHCP lease > Switching to new root and running init > #/bin/sh ro no such file or directory > > > /tftpboot/pxelinux.cfg/default ..... > > > default iscsi_root_xen > prompt 0 > > label manual_install > KERNEL /Centos/51/kickstart/vmlinuz > APPEND initrd=/Centos/51/kickstart/initrd.img > > label kickstart_xen > KERNEL /Centos/51/kickstart/vmlinuz > APPEND initrd=/Centos/51/kickstart/initrd.img > ks=http://192.168.1.202/anaconda-ks.cfg ksdevice=link noipv6 > > label kickstart_noxen > KERNEL /Centos/51/kickstart/vmlinuz > APPEND initrd=/Centos/51/kickstart/initrd.img > ks=http://192.168.1.202/anaconda-ks.noxen.cfg ksdevice=link noipv6 > > label iscsi_root_xen > KERNEL mboot.c32 > APPEND /Centos/boot/xen.gz-2.6.18-53.el5 --- > /Centos/boot/vmlinuz-2.6.18-53.el5xen ro root=LABEL=/ noipv6 > --- /Centos/boot/initrd-2.6.18-53.el5xen.img > > > label iscsi_root_noxen > KERNEL /Centos/boot/vmlinuz-2.6.18-53.el5 > APPEND initrd=/Centos/boot/initrd-2.6.18-53.el5.img ro > root=LABEL=/ noipv6 > > > the xen and the noxen have different iscsi partitions and > only one is activated at a time. > > the xen and noxen kickstarts are the same execpt the xen > includes the package @Virtualization > > Any ideas?I suggest starting out by looking at the kernel configs for both versions to see if anything differs besides the Xen options. Maybe upstream forgot to compile it the iSCSI support into the Xen kernel? -Ross ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
when anaconda installs a system it creates a initrd with an init script is
its root. The last statement is ''switchroot'' I think it is
pulling the
''ro'' from my kernel command line. I have tried mucking with
the command
line all day and will see a variety of errors.
man nash says
switchroot newrootpath
Makes the filesystem mounted at newrootpath the new
root
filesystem by moving the mountpoint. This will only work in
2.6
or later kernels.
I am guessing its like a chroot
Like I said earlier, this config works perfectely with the noxen config and
the init script is excactly the same in both initrds. However, pxe works a
little different with xen
BTW this is the x86_64
On Mon, Mar 31, 2008 at 4:57 PM, Maximilian Wilhelm <max@rfc2324.org>
wrote:
> Am Monday, den 31 March hub Joe Royall folgendes in die Tasten:
>
> [...]
> > Switching to new root and running init
> > #/bin/sh ro no such file or directory
>
> [...]
> > attached is the anaconda generated init inside initrd.
>
> What type of file in ''switchroot'' called at the end of
init?
> I would guess it''s a shell script.
> I guess further that it somehow fiddles around with the kernel
> parameters (''ro'') and that it would expect something
diffent there...
>
> So if I''m right with the first guess, can you post the contents of
the
> script here?
>
> Ciao
> Max
> --
> Follow the white penguin.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
--
Joe Royall
407-401-2007
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
If you boot vanilla Linux with the partition you''re using to boot Xen, does that work? (or vice versa) It seems like everything is working right until *after* the correct iSCSI partition has been mounted as / - then when it tries to boot, it messes things up I wouldn''t be surprised if this was a problem with the underlying CentOS install and not Xen related. If it is somehow Xen related, it''s quite possibly just a problem with the CentOS Xen package but that should still be possible to debug a bit... Cheers, Mark On Monday 31 March 2008, Joe Royall wrote:> I am getting the following error on boot on a new install Centos 51: > > #/bin/sh ro no such file or directory > then a kernel panic > > I have traced it to the call ''switchroot'' in the init script in the initrd. > > the exact same build without zen has no problems. > > the boot messages look like: > > Attaching to iSCSI storage > iscsistart: transport class version 2.0-724. iscsid version 2.0-865 > iscsistart: version 2.0-865 > scsi0 : iSCSI Initiator over TCP/IP > iscsistart: connection1:0 is operational now > Vendor: IET Model: Controler Rev: 0001 > Type: RAID ANSI SCSI revision: 05 > Vendor Model: VIRTUAL-DISK Rev: 0001 > Type: Direct -Access ANSI SCSI revision: 05 > SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB) > sda: Write Protect is off > SCSI device sda: drive cache: write back > SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB) > sda: Write Protect is off > SCSI device sda: drive cache: write back > sda: sda1 > sd 0:0:0:1: Attached scsi disk sda > Waiting for driver initialization > Scanning and configuring dmraid supported devices > Create root device > Mounting root filesystem. > kjournaled starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with orded data mode. > Setting up other filesystems. > Setting up new root fs > no fstab.sys, mounting internal defaults > Copying DHCP lease > Switching to new root and running init > #/bin/sh ro no such file or directory > > > /tftpboot/pxelinux.cfg/default ..... > > > default iscsi_root_xen > prompt 0 > > label manual_install > KERNEL /Centos/51/kickstart/vmlinuz > APPEND initrd=/Centos/51/kickstart/initrd.img > > label kickstart_xen > KERNEL /Centos/51/kickstart/vmlinuz > APPEND initrd=/Centos/51/kickstart/initrd.img ks> http://192.168.1.202/anaconda-ks.cfg ksdevice=link noipv6 > > label kickstart_noxen > KERNEL /Centos/51/kickstart/vmlinuz > APPEND initrd=/Centos/51/kickstart/initrd.img ks> http://192.168.1.202/anaconda-ks.noxen.cfg ksdevice=link noipv6 > > label iscsi_root_xen > KERNEL mboot.c32 > APPEND /Centos/boot/xen.gz-2.6.18-53.el5 --- /Centos/boot/vmlinuz- > 2.6.18-53.el5xen ro root=LABEL=/ noipv6 --- /Centos/boot/initrd- > 2.6.18-53.el5xen.img > > > label iscsi_root_noxen > KERNEL /Centos/boot/vmlinuz-2.6.18-53.el5 > APPEND initrd=/Centos/boot/initrd-2.6.18-53.el5.img ro root=LABEL=/ > noipv6 > > > the xen and the noxen have different iscsi partitions and only one is > activated at a time. > > the xen and noxen kickstarts are the same execpt the xen includes the > package @Virtualization > > Any ideas? > > attached is the anaconda generated init inside initrd.-- Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello, In my experience, I have noticed that iSCSI is never brought up properly. On a box we have running Xen 3.1 and Centos 5.0 the iSCSI mount needs to be brought up manually after it fails to load on boot. I don''t have a working solution, just trying to point you in a direction. Probably happens for us here because the box tries to bring up the iSCSI before trying to bring up the NICS. Anyways, just thought I''d add my two cents. Cheers, Tait -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Ross S. W. Walker Sent: Monday, March 31, 2008 5:01 PM To: Joe Royall; xen-users@lists.xensource.com Subject: RE: [Xen-users] iSCSI root on Dom0 Joe Royall wrote:> > I am getting the following error on boot on a new install Centos 51: > > #/bin/sh ro no such file or directory > then a kernel panic > > I have traced it to the call ''switchroot'' in the init script > in the initrd. > > the exact same build without zen has no problems. > > the boot messages look like: > > Attaching to iSCSI storage > iscsistart: transport class version 2.0-724. iscsid version 2.0-865 > iscsistart: version 2.0-865 > scsi0 : iSCSI Initiator over TCP/IP > iscsistart: connection1:0 is operational now > Vendor: IET Model: Controler Rev: 0001 > Type: RAID ANSI SCSI revision: 05 > Vendor Model: VIRTUAL-DISK Rev: 0001 > Type: Direct -Access ANSI SCSI revision: 05 > SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB) > sda: Write Protect is off > SCSI device sda: drive cache: write back > SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB) > sda: Write Protect is off > SCSI device sda: drive cache: write back > sda: sda1 > sd 0:0:0:1: Attached scsi disk sda > Waiting for driver initialization > Scanning and configuring dmraid supported devices > Create root device > Mounting root filesystem. > kjournaled starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with orded data mode. > Setting up other filesystems. > Setting up new root fs > no fstab.sys, mounting internal defaults > Copying DHCP lease > Switching to new root and running init > #/bin/sh ro no such file or directory > > > /tftpboot/pxelinux.cfg/default ..... > > > default iscsi_root_xen > prompt 0 > > label manual_install > KERNEL /Centos/51/kickstart/vmlinuz > APPEND initrd=/Centos/51/kickstart/initrd.img > > label kickstart_xen > KERNEL /Centos/51/kickstart/vmlinuz > APPEND initrd=/Centos/51/kickstart/initrd.img > ks=http://192.168.1.202/anaconda-ks.cfg ksdevice=link noipv6 > > label kickstart_noxen > KERNEL /Centos/51/kickstart/vmlinuz > APPEND initrd=/Centos/51/kickstart/initrd.img > ks=http://192.168.1.202/anaconda-ks.noxen.cfg ksdevice=link noipv6 > > label iscsi_root_xen > KERNEL mboot.c32 > APPEND /Centos/boot/xen.gz-2.6.18-53.el5 --- > /Centos/boot/vmlinuz-2.6.18-53.el5xen ro root=LABEL=/ noipv6 > --- /Centos/boot/initrd-2.6.18-53.el5xen.img > > > label iscsi_root_noxen > KERNEL /Centos/boot/vmlinuz-2.6.18-53.el5 > APPEND initrd=/Centos/boot/initrd-2.6.18-53.el5.img ro > root=LABEL=/ noipv6 > > > the xen and the noxen have different iscsi partitions and > only one is activated at a time. > > the xen and noxen kickstarts are the same execpt the xen > includes the package @Virtualization > > Any ideas?I suggest starting out by looking at the kernel configs for both versions to see if anything differs besides the Xen options. Maybe upstream forgot to compile it the iSCSI support into the Xen kernel? -Ross ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof. _______________________________________________ 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
On Wed, Apr 02, 2008 at 10:41:01AM -0400, Tait Clarridge wrote:> Hello, > > In my experience, I have noticed that iSCSI is never brought up > properly. On a box we have running Xen 3.1 and Centos 5.0 the iSCSI > mount needs to be brought up manually after it fails to load on boot. I > don''t have a working solution, just trying to point you in a direction. > > Probably happens for us here because the box tries to bring up the iSCSI > before trying to bring up the NICS. > > Anyways, just thought I''d add my two cents. >I''ll add my two cents too.. Upcoming RHEL 5.2 (and CentOS 5.2) should support software iSCSI root using iBFT information.. if your BIOS/NIC/whatnot support iBFT and fills up the iBFT table before booting the OS then initrd image is able to configure iSCSI root using the IP/LUN information on the iBFT table. See RHEL 5.2 beta announcement for more information.. -- Pasi> Cheers, > Tait > > -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Ross S. W. > Walker > Sent: Monday, March 31, 2008 5:01 PM > To: Joe Royall; xen-users@lists.xensource.com > Subject: RE: [Xen-users] iSCSI root on Dom0 > > Joe Royall wrote: > > > > I am getting the following error on boot on a new install Centos 51: > > > > #/bin/sh ro no such file or directory > > then a kernel panic > > > > I have traced it to the call ''switchroot'' in the init script > > in the initrd. > > > > the exact same build without zen has no problems. > > > > the boot messages look like: > > > > Attaching to iSCSI storage > > iscsistart: transport class version 2.0-724. iscsid version 2.0-865 > > iscsistart: version 2.0-865 > > scsi0 : iSCSI Initiator over TCP/IP > > iscsistart: connection1:0 is operational now > > Vendor: IET Model: Controler Rev: 0001 > > Type: RAID ANSI SCSI revision: 05 > > Vendor Model: VIRTUAL-DISK Rev: 0001 > > Type: Direct -Access ANSI SCSI revision: 05 > > SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB) > > sda: Write Protect is off > > SCSI device sda: drive cache: write back > > SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB) > > sda: Write Protect is off > > SCSI device sda: drive cache: write back > > sda: sda1 > > sd 0:0:0:1: Attached scsi disk sda > > Waiting for driver initialization > > Scanning and configuring dmraid supported devices > > Create root device > > Mounting root filesystem. > > kjournaled starting. Commit interval 5 seconds > > EXT3-fs: mounted filesystem with orded data mode. > > Setting up other filesystems. > > Setting up new root fs > > no fstab.sys, mounting internal defaults > > Copying DHCP lease > > Switching to new root and running init > > #/bin/sh ro no such file or directory > > > > > > /tftpboot/pxelinux.cfg/default ..... > > > > > > default iscsi_root_xen > > prompt 0 > > > > label manual_install > > KERNEL /Centos/51/kickstart/vmlinuz > > APPEND initrd=/Centos/51/kickstart/initrd.img > > > > label kickstart_xen > > KERNEL /Centos/51/kickstart/vmlinuz > > APPEND initrd=/Centos/51/kickstart/initrd.img > > ks=http://192.168.1.202/anaconda-ks.cfg ksdevice=link noipv6 > > > > label kickstart_noxen > > KERNEL /Centos/51/kickstart/vmlinuz > > APPEND initrd=/Centos/51/kickstart/initrd.img > > ks=http://192.168.1.202/anaconda-ks.noxen.cfg ksdevice=link noipv6 > > > > label iscsi_root_xen > > KERNEL mboot.c32 > > APPEND /Centos/boot/xen.gz-2.6.18-53.el5 --- > > /Centos/boot/vmlinuz-2.6.18-53.el5xen ro root=LABEL=/ noipv6 > > --- /Centos/boot/initrd-2.6.18-53.el5xen.img > > > > > > label iscsi_root_noxen > > KERNEL /Centos/boot/vmlinuz-2.6.18-53.el5 > > APPEND initrd=/Centos/boot/initrd-2.6.18-53.el5.img ro > > root=LABEL=/ noipv6 > > > > > > the xen and the noxen have different iscsi partitions and > > only one is activated at a time. > > > > the xen and noxen kickstarts are the same execpt the xen > > includes the package @Virtualization > > > > Any ideas? > > I suggest starting out by looking at the kernel configs for > both versions to see if anything differs besides the Xen > options. Maybe upstream forgot to compile it the iSCSI > support into the Xen kernel? > > -Ross >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Apr 2, 2008 at 11:55 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> On Wed, Apr 02, 2008 at 10:41:01AM -0400, Tait Clarridge wrote: > > Hello, > > > > In my experience, I have noticed that iSCSI is never brought up > > properly. On a box we have running Xen 3.1 and Centos 5.0 the iSCSI > > mount needs to be brought up manually after it fails to load on boot. I > > don''t have a working solution, just trying to point you in a direction. > > > > Probably happens for us here because the box tries to bring up the iSCSI > > before trying to bring up the NICS. > > > > Anyways, just thought I''d add my two cents. > > > > I''ll add my two cents too.. > > Upcoming RHEL 5.2 (and CentOS 5.2) should support software iSCSI root > using iBFT > information.. if your BIOS/NIC/whatnot support iBFT and fills up the iBFT > table > before booting the OS then initrd image is able to configure iSCSI root > using the > IP/LUN information on the iBFT table. > > See RHEL 5.2 beta announcement for more information..I think this would make the problem go away and a lot of others. Do you know of any GBE nics that support this?> > > -- Pasi > > > Cheers, > > Tait > > > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Ross S. W. > > Walker > > Sent: Monday, March 31, 2008 5:01 PM > > To: Joe Royall; xen-users@lists.xensource.com > > Subject: RE: [Xen-users] iSCSI root on Dom0 > > > > Joe Royall wrote: > > > > > > I am getting the following error on boot on a new install Centos 51: > > > > > > #/bin/sh ro no such file or directory > > > then a kernel panic > > > > > > I have traced it to the call ''switchroot'' in the init script > > > in the initrd. > > > > > > the exact same build without zen has no problems. > > > > > > the boot messages look like: > > > > > > Attaching to iSCSI storage > > > iscsistart: transport class version 2.0-724. iscsid version 2.0-865 > > > iscsistart: version 2.0-865 > > > scsi0 : iSCSI Initiator over TCP/IP > > > iscsistart: connection1:0 is operational now > > > Vendor: IET Model: Controler Rev: 0001 > > > Type: RAID ANSI SCSI revision: 05 > > > Vendor Model: VIRTUAL-DISK Rev: 0001 > > > Type: Direct -Access ANSI SCSI revision: 05 > > > SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB) > > > sda: Write Protect is off > > > SCSI device sda: drive cache: write back > > > SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB) > > > sda: Write Protect is off > > > SCSI device sda: drive cache: write back > > > sda: sda1 > > > sd 0:0:0:1: Attached scsi disk sda > > > Waiting for driver initialization > > > Scanning and configuring dmraid supported devices > > > Create root device > > > Mounting root filesystem. > > > kjournaled starting. Commit interval 5 seconds > > > EXT3-fs: mounted filesystem with orded data mode. > > > Setting up other filesystems. > > > Setting up new root fs > > > no fstab.sys, mounting internal defaults > > > Copying DHCP lease > > > Switching to new root and running init > > > #/bin/sh ro no such file or directory > > > > > > > > > /tftpboot/pxelinux.cfg/default ..... > > > > > > > > > default iscsi_root_xen > > > prompt 0 > > > > > > label manual_install > > > KERNEL /Centos/51/kickstart/vmlinuz > > > APPEND initrd=/Centos/51/kickstart/initrd.img > > > > > > label kickstart_xen > > > KERNEL /Centos/51/kickstart/vmlinuz > > > APPEND initrd=/Centos/51/kickstart/initrd.img > > > ks=http://192.168.1.202/anaconda-ks.cfg ksdevice=link noipv6 > > > > > > label kickstart_noxen > > > KERNEL /Centos/51/kickstart/vmlinuz > > > APPEND initrd=/Centos/51/kickstart/initrd.img > > > ks=http://192.168.1.202/anaconda-ks.noxen.cfg ksdevice=link noipv6 > > > > > > label iscsi_root_xen > > > KERNEL mboot.c32 > > > APPEND /Centos/boot/xen.gz-2.6.18-53.el5 --- > > > /Centos/boot/vmlinuz-2.6.18-53.el5xen ro root=LABEL=/ noipv6 > > > --- /Centos/boot/initrd-2.6.18-53.el5xen.img > > > > > > > > > label iscsi_root_noxen > > > KERNEL /Centos/boot/vmlinuz-2.6.18-53.el5 > > > APPEND initrd=/Centos/boot/initrd-2.6.18-53.el5.img ro > > > root=LABEL=/ noipv6 > > > > > > > > > the xen and the noxen have different iscsi partitions and > > > only one is activated at a time. > > > > > > the xen and noxen kickstarts are the same execpt the xen > > > includes the package @Virtualization > > > > > > Any ideas? > > > > I suggest starting out by looking at the kernel configs for > > both versions to see if anything differs besides the Xen > > options. Maybe upstream forgot to compile it the iSCSI > > support into the Xen kernel? > > > > -Ross > > >-- Joe Royall 407-401-2007 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Apr 02, 2008 at 01:13:58PM -0400, Joe Royall wrote:> On Wed, Apr 2, 2008 at 11:55 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > > On Wed, Apr 02, 2008 at 10:41:01AM -0400, Tait Clarridge wrote: > > > Hello, > > > > > > In my experience, I have noticed that iSCSI is never brought up > > > properly. On a box we have running Xen 3.1 and Centos 5.0 the iSCSI > > > mount needs to be brought up manually after it fails to load on boot. I > > > don''t have a working solution, just trying to point you in a direction. > > > > > > Probably happens for us here because the box tries to bring up the iSCSI > > > before trying to bring up the NICS. > > > > > > Anyways, just thought I''d add my two cents. > > > > > > > I''ll add my two cents too.. > > > > Upcoming RHEL 5.2 (and CentOS 5.2) should support software iSCSI root > > using iBFT > > information.. if your BIOS/NIC/whatnot support iBFT and fills up the iBFT > > table > > before booting the OS then initrd image is able to configure iSCSI root > > using the > > IP/LUN information on the iBFT table. > > > > See RHEL 5.2 beta announcement for more information.. > > > > I think this would make the problem go away and a lot of others. Do you > know of any GBE nics that support this? >Afaik both Intel and Broadcom _server_ NICs have special iBFT/int13h capable firmware available making boot-from-iscsi-san without HBA possible. -- Pasi> > > > > > -- Pasi > > > > > Cheers, > > > Tait > > > > > > -----Original Message----- > > > From: xen-users-bounces@lists.xensource.com > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Ross S. W. > > > Walker > > > Sent: Monday, March 31, 2008 5:01 PM > > > To: Joe Royall; xen-users@lists.xensource.com > > > Subject: RE: [Xen-users] iSCSI root on Dom0 > > > > > > Joe Royall wrote: > > > > > > > > I am getting the following error on boot on a new install Centos 51: > > > > > > > > #/bin/sh ro no such file or directory > > > > then a kernel panic > > > > > > > > I have traced it to the call ''switchroot'' in the init script > > > > in the initrd. > > > > > > > > the exact same build without zen has no problems. > > > > > > > > the boot messages look like: > > > > > > > > Attaching to iSCSI storage > > > > iscsistart: transport class version 2.0-724. iscsid version 2.0-865 > > > > iscsistart: version 2.0-865 > > > > scsi0 : iSCSI Initiator over TCP/IP > > > > iscsistart: connection1:0 is operational now > > > > Vendor: IET Model: Controler Rev: 0001 > > > > Type: RAID ANSI SCSI revision: 05 > > > > Vendor Model: VIRTUAL-DISK Rev: 0001 > > > > Type: Direct -Access ANSI SCSI revision: 05 > > > > SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB) > > > > sda: Write Protect is off > > > > SCSI device sda: drive cache: write back > > > > SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB) > > > > sda: Write Protect is off > > > > SCSI device sda: drive cache: write back > > > > sda: sda1 > > > > sd 0:0:0:1: Attached scsi disk sda > > > > Waiting for driver initialization > > > > Scanning and configuring dmraid supported devices > > > > Create root device > > > > Mounting root filesystem. > > > > kjournaled starting. Commit interval 5 seconds > > > > EXT3-fs: mounted filesystem with orded data mode. > > > > Setting up other filesystems. > > > > Setting up new root fs > > > > no fstab.sys, mounting internal defaults > > > > Copying DHCP lease > > > > Switching to new root and running init > > > > #/bin/sh ro no such file or directory > > > > > > > > > > > > /tftpboot/pxelinux.cfg/default ..... > > > > > > > > > > > > default iscsi_root_xen > > > > prompt 0 > > > > > > > > label manual_install > > > > KERNEL /Centos/51/kickstart/vmlinuz > > > > APPEND initrd=/Centos/51/kickstart/initrd.img > > > > > > > > label kickstart_xen > > > > KERNEL /Centos/51/kickstart/vmlinuz > > > > APPEND initrd=/Centos/51/kickstart/initrd.img > > > > ks=http://192.168.1.202/anaconda-ks.cfg ksdevice=link noipv6 > > > > > > > > label kickstart_noxen > > > > KERNEL /Centos/51/kickstart/vmlinuz > > > > APPEND initrd=/Centos/51/kickstart/initrd.img > > > > ks=http://192.168.1.202/anaconda-ks.noxen.cfg ksdevice=link noipv6 > > > > > > > > label iscsi_root_xen > > > > KERNEL mboot.c32 > > > > APPEND /Centos/boot/xen.gz-2.6.18-53.el5 --- > > > > /Centos/boot/vmlinuz-2.6.18-53.el5xen ro root=LABEL=/ noipv6 > > > > --- /Centos/boot/initrd-2.6.18-53.el5xen.img > > > > > > > > > > > > label iscsi_root_noxen > > > > KERNEL /Centos/boot/vmlinuz-2.6.18-53.el5 > > > > APPEND initrd=/Centos/boot/initrd-2.6.18-53.el5.img ro > > > > root=LABEL=/ noipv6 > > > > > > > > > > > > the xen and the noxen have different iscsi partitions and > > > > only one is activated at a time. > > > > > > > > the xen and noxen kickstarts are the same execpt the xen > > > > includes the package @Virtualization > > > > > > > > Any ideas? > > > > > > I suggest starting out by looking at the kernel configs for > > > both versions to see if anything differs besides the Xen > > > options. Maybe upstream forgot to compile it the iSCSI > > > support into the Xen kernel? > > > > > > -Ross > > > > > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Apr 02, 2008 at 09:01:45PM +0300, Pasi Kärkkäinen wrote:> On Wed, Apr 02, 2008 at 01:13:58PM -0400, Joe Royall wrote: > > On Wed, Apr 2, 2008 at 11:55 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > > > > On Wed, Apr 02, 2008 at 10:41:01AM -0400, Tait Clarridge wrote: > > > > Hello, > > > > > > > > In my experience, I have noticed that iSCSI is never brought up > > > > properly. On a box we have running Xen 3.1 and Centos 5.0 the iSCSI > > > > mount needs to be brought up manually after it fails to load on boot. I > > > > don''t have a working solution, just trying to point you in a direction. > > > > > > > > Probably happens for us here because the box tries to bring up the iSCSI > > > > before trying to bring up the NICS. > > > > > > > > Anyways, just thought I''d add my two cents. > > > > > > > > > > I''ll add my two cents too.. > > > > > > Upcoming RHEL 5.2 (and CentOS 5.2) should support software iSCSI root > > > using iBFT > > > information.. if your BIOS/NIC/whatnot support iBFT and fills up the iBFT > > > table > > > before booting the OS then initrd image is able to configure iSCSI root > > > using the > > > IP/LUN information on the iBFT table. > > > > > > See RHEL 5.2 beta announcement for more information.. > > > > > > > > I think this would make the problem go away and a lot of others. Do you > > know of any GBE nics that support this? > > > > Afaik both Intel and Broadcom _server_ NICs have special iBFT/int13h capable > firmware available making boot-from-iscsi-san without HBA possible. >And IBM blade servers also have iBFT support on their BIOS.. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users