pushkar rajkarnikar
2008-Feb-20 07:23 UTC
[Xen-users] Problem - Boot Xen 3.0.1 Guest using NFS
I have been trying to boot Xen guest (Fedora Core 6 - linux version 2.6.18) from NFS server but I kept encountering a problem despite using ramdisk or not. Key items in my config file are as follows: ================================================kernel "/root/Xen/xen-3.1.0-src/linux-2.6.18-xenU2/vmlinuz" # Optional ramdisk. # ramdisk = "/boot/initrd-2.6.18-xenU2.img" #root/Xen/xen-3.1.0-src/linux-2.6.18-xenU2/init.img" memory = 128 name = "Fedora2" vcpus = 1 vif = [ ''mac=00:16:3e:24:2D:c7, bridge=xenbr0'' ] ip = ''192.168.23.232'' netmask = ''255.255.255.0'' gateway = ''192.168.0.1'' hostname = ''Fedora2'' #"vm%d" % vmid broadcast = ''192.168.23.255'' root = ''/dev/nfs'' nfs_server = ''192.168.23.252'' nfs_root = ''/root/Desktop/FC6'' # Sets runlevel 4. extra = "4" =============================================== and THE ERROR I ENCOUNTERED ARE AS FOLLOWS - (see at the end of the output .. ) ............... ............ .............. waiting for link... 0 seconds. Sending request for IP information through eth0 Listening on LPF/eth0/00:16:3e:24:2d:c7 Sending on LPF/eth0/00:16:3e:24:2d:c7 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 DHCPOFFER from 192.168.23.10 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.23.10 bound to 192.168.23.241 -- renewal in 9660 seconds. DHCPv4 eth0 - obtained lease 192.168.23.241 DHCPv4 eth0 - option subnet-mask: 255.255.255.0 DHCPv4 eth0 - option subnet-mask - prefix_len: 24 broadcast: 192.168.23.255 DHCPv4 eth0 - option routers: Scanning logical volumes Reading all physical volumes. This may take a while... No volume groups found Activating logical volumes Volume group "VolGroup00" not found Creating root device. Mounting root filesystem. 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. unmounting old /dev unmounting old /proc unmounting old /sys modprobe: FATAL: Could not load /lib/modules/2.6.18/modules.dep: No such file or directory modprobe: FATAL: Could not load /lib/modules/2.6.18/modules.dep: No such file or directory INIT: version 2.86 booting Welcome to Fedora Core Press ''I'' to enter interactive startup. Setting clock : Wed Feb 20 02:00:56 EST 2008 [ OK ] Setting hostname fc6_pristine: [ OK ] Setting up Logical Volume Management: No volume groups found [ OK ] Checking filesystems Checking all file systems. [ OK ] Remounting root filesystem in read-write mode: [ OK ] Mounting local filesystems: [ OK ] Enabling /etc/fstab swaps: [ OK ] modprobe: FATAL: Could not load /lib/modules/2.6.18/modules.dep: No such file or directory INIT: Entering runlevel: 4 Entering non-interactive startup Bringing up loopback interface: ./network-functions: line 166: cd: /var/run/netreport: No such file or directory [ OK ] Bringing up interface eth0: Determining IP information for eth0... done. ./network-functions: line 390: /dev/null: Network is unreachable ./network-functions: line 390: grep: command not found /etc/sysconfig/network-scripts/ifup-eth: line 295: ip: command not found /etc/sysconfig/network-scripts/ifup-eth: line 312: /etc/sysconfig/network-scripts/ifup-post: Network is unreachable /etc/sysconfig/network-scripts/ifup-eth: line 312: exec: /etc/sysconfig/network-scripts/ifup-post: cannot execute: Network is unreachable [FAILED] /etc/rc4.d/S10network: line 165: /dev/null: Network is unreachable /etc/rc4.d/S10network: line 167: touch: command not found /etc/rc.d/rc: line 90: rm: command not found WHAT DO YOU THING IS THE PROBLEM HERE?? THANKS A MILLION IN ADVANCE FOR ANY HELP OR LEADS. Regards, Pushkar. Send instant messages to your online friends http://uk.messenger.yahoo.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Evan Lavelle
2008-Feb-20 10:49 UTC
Re: [Xen-users] Problem - Boot Xen 3.0.1 Guest using NFS
I''m no expert here, but it looks like your initrd is incorrect. Where did you get the DomU kernel and initrd? Does the DomU kernel have built-in drivers? If it doesn''t, then you need the (correct) initrd. You''ll probably have to rebuild it. You''ve also got some interesting syntax in your config file - ''broadcast'' isn''t mentioned in the 3.0 user''s manual, or any of the XenSource docs I''ve seen - where did you find it? Evan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users