[Fedora-xen] NFS Booting - Kernel modification

Paul Wouters paul at xelerance.com
Tue Feb 27 01:31:08 UTC 2007


On Mon, 26 Feb 2007, Abhishek Gaurav wrote:

The loading of those two drivers look good, but I don't know why it still
does not work. I haven't tried booting xenu's over NFS myself.

Paul

> Paul Wouters wrote:
> > 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 at hs20-bc1-6.build.redhat.com) (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 at redhat.com
> > >
> > > 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
> >
> Hi Paul,
> It ends up in the same error with the following diff in the boot sequence. I
> have also attached the complete boot sequence.
>
> 15,16c15,16
> Memory: 1017080k/1056768k available (2323k kernel code, 30784k reserved, 1328k
> data, 172k init)
> Calibrating delay using timer specific routine.. 6002.08 BogoMIPS
> (lpj=12004172)
> ---
> Memory: 1016956k/1056768k available (2323k kernel code, 30912k reserved, 1328k
> data, 172k init)
> Calibrating delay using timer specific routine.. 6001.96 BogoMIPS
> (lpj=12003922)
> 26c26
> CPU: Processor Core ID: 1
> ---
> CPU: Processor Core ID: 0
> 54c54
> audit(1172530246.553:1): initialized
> ---
> audit(1172530185.634:1): initialized
> 87,88c87,88
> Memory: 1017080k/1056768k available (2323k kernel code, 30784k reserved, 1328k
> data, 172k init)
> Calibrating delay using timer specific routine.. 6002.08 BogoMIPS
> (lpj=12004172)
> ---
> Memory: 1016956k/1056768k available (2323k kernel code, 30912k reserved, 1328k
> data, 172k init)
> Calibrating delay using timer specific routine.. 6001.96 BogoMIPS
> (lpj=12003922)
> 98c98
> CPU: Processor Core ID: 1
> ---
> CPU: Processor Core ID: 0
> 126c126
> audit(1172530246.553:1): initialized
> ---
> audit(1172530185.634:1): initialized
> 170a171
> > Loading xenblk.ko module
> 187c188,191
> < Creating root device.
> ---
> > Loading xennet.ko module
> > netfront: Initialising virtual ethernet driver.
> netfront: Created netdev eth0 with flipping receive path.
> Creating root device.
>
>
> Also, for your reference, the config file for the VM is:
>
> kernel = "/boot/vmlinuz-2.6.18-1.2798.fc6xen"
> ramdisk = "/boot/initrd-2.6.18-1.2798.fc6xenU.img"
> name = "grc59"
> memory = "1024"
> vif = [ 'mac=00:16:3e:0e:81:59' ]
> root = '/dev/nfs'
> nfs_server = '136.159.8.14'
> nfs_root = '/home/xen-images/fc4'
>
>
> Thanks for the help,
> Abhishek.
>
>

-- 
Building and integrating Virtual Private Networks with Openswan:
http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155




More information about the Fedora-xen mailing list