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/
Home Products Support Community News


Re: [Xen-users] iSCSI root on Dom0

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] iSCSI root on Dom0
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Wed, 2 Apr 2008 12:35:14 +0100
Cc: Joe Royall <joenukem@xxxxxxxxx>, Maximilian Wilhelm <max@xxxxxxxxxxx>, "Ross S. W. Walker" <rwalker@xxxxxxxxxxxxx>
Delivery-date: Wed, 02 Apr 2008 04:35:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bb0fa5d0803311351w5badf0b4u9b5a6dd4bc4fca25@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <bb0fa5d0803311351w5badf0b4u9b5a6dd4bc4fca25@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.6 (enterprise 0.20070907.709405)
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...


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=
> ksdevice=link noipv6
> label kickstart_noxen
>         KERNEL /Centos/51/kickstart/vmlinuz
>         APPEND initrd=/Centos/51/kickstart/initrd.img ks=
> 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

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