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] iSCSI root on Dom0

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@xxxxxx> 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@xxxxxxxxxxxxxxxxxxx
> > > [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Ross S. W.
> > > Walker
> > > Sent: Monday, March 31, 2008 5:01 PM
> > > To: Joe Royall; xen-users@xxxxxxxxxxxxxxxxxxx
> > > 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

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