On Mon, 26 Feb 2007, Abhishek Gaurav wrote: > If I use a ramdisk, the error log changes (its attached to this mail). Not > sure if I am in the right direction. Yes you are! Your logs show: > Bootdata ok (command line is ip=136.159.8.59:136.159.8.14:136.159.8.14:255.255.255.0::eth0:off root=/dev/nfs nfsroot=136.159.8.14:/home/xen-images/fc4 ) > > Linux version 2.6.18-1.2798.fc6xen (brewbuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) #1 SMP Mon Oct 16 14:59:01 EDT 2006 > > SELinux: Initializing. > > checking if image is initramfs... it is > > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize it loads the ramdisk > Xen virtual console successfully installed as xvc0 > > XENBUS: Device with no driver: device/vif/0 Looks like a missing xenblk or xennet driver... > Write protecting the kernel read-only data: 440k > > Red Hat nash version 5.1.19 starting > Mounting proc filesystem > Mounting sysfs filesystem > Creating /dev > Creating initial device nodes > Setting up hotplug. > Creating block device nodes. > Loading uhci-hcd.ko module > USB Universal Host Controller Interface driver v3.0 > > Loading ohci-hcd.ko module > Loading ehci-hcd.ko module > Loading jbd.ko module > Loading ext3.ko module > Loading scsi_mod.ko module > SCSI subsystem initialized > > Loading sd_mod.ko module > Loading cciss.ko module > HP CISS Driver (v 3.6.10) > > Loading dm-mod.ko module > device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@xxxxxxxxxx > > Loading dm-mirror.ko module > Loading dm-zero.ko module > Loading dm-snapshot.ko module > Creating root device. > Mounting root filesystem. > mount: could not find filesystem '/dev/root' > Setting up other filesystems. > Setting up new root fs > setuproot: moving /dev failed: No such file or directory > no fstab.sys, mounting internal defaults > setuproot: error mounting /proc: No such file or directory > setuproot: error mounting /sys: No such file or directory > Switching to new root and running init. > unmounting old /dev > unmounting old /proc > unmounting old /sys > switchroot: mount failed: No such file or directory > Kernel panic - not syncing: Attempted to kill init! I am confused that I don't see xenblk being loaded, yet you are able to get mount the rootfs. Might be a NFS thing. Try creating a special ramdisk/initrd for this machine on the dom0 using: mkinitrd /boot/initrd-2.6.18-1.2798.fc6xenU.img --preload=xenblk --with=xennet 2.6.18-1.2798.fc6xen and change your config to use the ramdisk /boot/initrd-2.6.18-1.2798.fc6xenU.img instead. Please let me know if this works. Paul -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
