I consistently get an error booting Dom0 from a SAN on JS21. I'm using xen_maple_defconfig + QLA2xxx device driver.
With an nfsroot boot argument passed in, the system boots fine.
With a root=/dev/nfs changed to root=/dev/sdc1 (a lun on the SAN), it mounts the root filesystem, and then fails with the following message:
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 244k freed
/bin/bash: /lib/libdl.so.2: version `' not found (required by /bin/bash)
/bin/bash: /lib/libdl.so.2: version `' not found (required by /bin/bash)
/bin/bash: /lib/power4/libc.so.6: version `' not found (required by /bin/bash)
/bin/bash: /lib/power4/libc.so.6: version `' not found (required by /bin/bash)
/bin/bash: /lib/power4/libc.so.6: version `' not found (required by /bin/bash)
/bin/bash: /lib/power4/libc.so.6: version `' not found (required by /bin/bash)
/bin/bash: /lib/power4/libc.so.6: version `' not found (required by /bin/bash)
/bin/bash: /lib/power4/libc.so.6: version `' not found (required by /bin/bash)
Kernel panic - not syncing: Attempted to kill init!
<0>Rebooting in 180 seconds..Connection closed by foreign host.
The two root filesystems are basically identical, and I can boot and mount the SAN based filesystem as root for a linux kernel (no Xen).
This can be repeated on my test blade cso86 (chassis 4 blade 6). I am using yaboot, and the failing configuration is target cxeny2s.
David Daly
Research Staff Member
32-003 IBM T.J. Watson Research Center
Yorktown Heights, NY, 10958
(914) 945-1845, T/L 862-1845
_______________________________________________ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
