WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Installing a domU on NFS

  By default the Xen kernel which is installed by "make world && make
 install" doesn't have NFS_ROOT setup.  Neither do many of the kernels
 packaged by distributions.  (eg. Debian Etch has a range of Xen kernels
 but none of them have NFS_ROOT compiled in).

  By happy coincidence I wrote a guide on getting NFS_ROOT working
 on a Debian machine yesterday evening and it just got published:

        http://www.debian-administration.org/articles/505

So I think I have got everything I need, but it still does not work.

/mnt/etc # cat fstab
10.2.50.21:/xenvm1 / nfs defaults 0 0
proc /proc proc defaults 0 0
sysfs /proc sysfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0

/etc/xen/vm # cat x-dktest
kernel = '/boot/vmlinuz-2.6.18.2dk2-34-xen'
ramdisk = '/boot/initrd-2.6.18.2dk2-34-xen'
vif = [ 'bridge=xenbr0, ip=10.2.50.41' ]
dhcp = 'off'
netmask = '255.255.255.0'
gateway = '10.2.50.10'
ip = '10.2.50.41'
hostname = 'x-dktest'
root = '/dev/nfs'
nfs_server = '10.2.50.21'
nfs_root = '/xenvm1'
memory = 512
vcpus = 1
builder = 'linux'
name = 'x-dktest'
localtime = 0
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
extra = ' TERM=xterm'

/etc/xen/vm # uname -a
Linux ACD-xen01 2.6.18.2dk2-34-xen #3 SMP Thu Mar 8 16:44:33 CET 2007 i686 i686 i386 GNU/Linux

/etc/xen/vm # zgrep ROOT_NFS /proc/config.gz
CONFIG_ROOT_NFS=y

/etc/xen/vm # zgrep IP_PNP /proc/config.gz
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_PNP_RARP=y

/etc/xen/vm # ls /mnt/lib/modules/
2.6.18.2-34-default  2.6.18.2-34-xen  2.6.18.2dk2-34-xen  2.6.18.2dk-34-xen

Error Message is this:
NET: Registered protocol family 1
Using IPI No-Shortcut mode
XENBUS: Device with no driver: device/vif/0
Time: xen clocksource has been installed.
IP-Config: Device `eth0' not found.
Freeing unused kernel memory: 200k freed
Boot logging started on /dev/tty1(/dev/console) at Mon Mar 12 07:26:10 2007
Creating device nodes with udev
netfront: Initialising virtual ethernet driver.
Loading xennet
netfront: device eth0 has flipping receive path.
Loading xenblk
Loading jbd
Loading mbcache
Loading ext3
Mounting root 10.2.50.21:/xenvm1
mount server reported tcp not available, falling back to udp
mount: RPC: Remote system error - Network is unreachable
umount: /dev: device is busy
umount: /dev: device is busy
umount: /dev/pts: device is busy
umount: /dev/pts: device is busy
Kernel panic - not syncing: Attempted to kill init!

What I'm curious about is the line "IP-Config: Device `eth0' not found." which seems to be a problem. But it is actually attached to the correct bridge. See here (this is after booting the vm while it hangs with kernel panic):

/etc/xen/vm # xm list
Name                                      ID Mem(MiB) VCPUs State   Time(s)
Domain-0                                   0      511     4 r-----   1519.3
x-dktest                                   9      512     1 r-----    102.6


/etc/xen/vm # brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.000423c0b340       no              vif0.0
                                                        bond0
                                                        vif9.0

/etc/xen/vm # xm network-list 9
Idx BE     MAC Addr.     handle state evt-ch tx-/rx-ring-ref BE-path
0 0 00:16:3e:4c:38:23 0 4 6 520 /521 /local/domain/0/backend/vif/9/0

Any ideas appreciated.

Thanks in advance,
Dominik

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