Xen users - Jun 2005 - ttylinux-xen domain U Boot problems

Hi,

I have got xen compiled and installed properly.Domain 0 is created on the 
Xen port of Linux-2.6.11.10.But I am unable to boot the host domains.

This is what one of my XenU config file contains

[root@xion /]# cat /etc/xen/ttylinux
kernel = "/boot/vmlinuz-2.6.11.10-xenU"
memory = 64
name = "ttylinux"
nics = 1
vif = [ ''mac=bb:00:00:00:00:11, bridge=xen-br0'' ]
disk = [ ''file:/mnt/xenfs/ttylinux-xen,hda3,w'' ]
ip = "10.1.10.20 <http://10.1.10.20>"
hostname = "ttylinux"
root = "/dev/hda3 ro"

/dev/hda3 maps to / on where my Xen Domain 0 is running.

This is the error in detail I get after trying to boot Xen U.

[root@xion /]# xm create -c /etc/xen/ttylinux
Using config file "/etc/xen/ttylinux".
Started domain ttylinux, console on port 9601
************ REMOTE CONSOLE: CTRL-] TO QUIT ********
Linux version 2.6.11.10-xenU (root@xion) (gcc version 3.2.3 20030502 (Red 
Hat Linux 3.2.3-20)) #1 Tue Jun 28 16:59:12 IST 2005
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000004000000 (usable)
64MB LOWMEM available.
DMI not present.
IRQ lockup detection disabled
Allocating PCI resources starting at 04000000 (gap: 04000000:fc000000)
Built 1 zonelists
Kernel command line: ip=10.1.10.20:1
<http://10.1.10.20:1>.2.3.4:::ttylinux:eth0:off
root=/dev/hda3 ro 4
Initializing CPU#0
PID hash table entries: 512 (order: 9, 8192 bytes)
Xen reported: 2792.983 MHz processor.
Using tsc for high-res timesource
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
vmalloc area: c4800000-fbff9000, maxmem 34000000
Memory: 54352k/65536k available (1652k kernel code, 11100k reserved, 442k 
data, 112k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking ''hlt'' instruction... disabled
checking if image is initramfs...it isn''t (bad gzip magic numbers);
looks
like an initrd
Freeing initrd memory: 8000k freed
NET: Registered protocol family 16
xen_mem: Initialising balloon driver.
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Xen virtual console successfully installed as tty
Event-channel device installed.
xen_blk: Initialising virtual block device driver
xen_net: Initialising virtual ethernet driver.
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
NET: Registered protocol family 1
NET: Registered protocol family 17
IP-Config: Guessing netmask 255.0.0.0 <http://255.0.0.0>
IP-Config: Complete:
device=eth0, addr=10.1.10.20 <http://10.1.10.20>,
mask=255.0.0.0<http://255.0.0.0>,
gw=255.255.255.255 <http://255.255.255.255>,
host=ttylinux, domain=, nis-domain=(none),
bootserver=1.2.3.4 <http://1.2.3.4>, rootserver=1.2.3.4
<http://1.2.3.4>,
rootpathRAMDISK: ext2 filesystem found at block 0
RAMDISK: image too big! (8000KiB/4096KiB)
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 112k freed
kjournald starting. Commit interval 5 seconds

ttylinux 4.2 by Pascal Schmidt <der.eremit@email.de>

Mounting proc: done
Mounting sysfs: done
Setting console loglevel: done
Setting system clock: hwclock: Could not access RTC: No such file or 
directory
failed
Starting fsck for root filesystem.
e2fsck 1.35 (28-Feb-2004)
fsck.ext3: No such file or directory while trying to open 
/mnt/xenfs/ttylinux-xen

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

WARNING: Errors found while checking root filesystem.
You can login as root now, the system will reboot after logout.

Give root password for system maintenance
(or type Control-D for normal startup):
************ REMOTE CONSOLE EXITED *****************

Please help!

~$ubh


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users