I’m currently trying to get a Xen domU running openSuSE 11.3 to boot correctly over NFS. I’ve used the YaST dirinstall module to install openSUSE 11.3 into an NFS share. After doing that, I chroot’d to the directory and created the initrd module, making sure to specify /dev/nfs as the root device and making sure that the xennet driver is loaded in initrd. I then set up my domU, and specified the necessary options for nfs root in the domU configuration. I tried two methods of obtaining an IP address - the first using the dhcp option in the domU configuration, and the second using the “-D eth0” option in mkinitrd. I’m not sure if this is working or not - I get some output from the domU, but then it hangs. The last few lines are:
0.237446] NET: Registered protocol family 2
0.237544] IP route cache hash table entries: 16384 (order: 5, 131072 bytes)
0.237835] TCP established hash table entries: 65536 (order: 8, 1048576 bytes)
0.238072] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
0.238321] TCP: Hash tables configured (established 65536 bind 65536)
0.238326] TCP reno registered
0.238330] UDP hash table entries: 256 (order: 2, 16384 bytes)
0.238339] UDP-Lite hash table entries: 256 (order: 2, 16384 bytes)
0.238478] NET: Registered protocol family 1
0.238638] platform rtc_cmos: registered platform RTC device (no PNP device found)
0.239049] audit: initializing netlink socket (disabled)
0.239069] type=2000 audit(1284326421.675:1): initialized
0.264032] VFS: Disk quotas dquot_6.5.2
0.264072] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
0.264339] msgmni has been set to 256
0.264737] alg: No test for stdrng (krng)
0.264802] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
0.264811] io scheduler noop registered
0.264814] io scheduler deadline registered
0.264862] io scheduler cfq registered (default)
0.264964] pci-stub: invalid id string ""
0.265948] Non-volatile memory driver v1.3
0.266003] Xen virtual console successfully installed as xvc0
0.266038] Fixed MDIO Bus: probed
0.266062] PNP: No PS/2 controller found. Probing ports directly.
0.266884] i8042.c: No controller found.
0.266920] mice: PS/2 mouse device common for all mice
0.267076] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
0.267304] TCP cubic registered
0.267446] NET: Registered protocol family 10
0.267808] lo: Disabled Privacy Extensions
0.268030] registered taskstats version 1
0.268063] PCI IO multiplexer device installed.
0.268075] Magic number: 1:252:3141
0.268086] XENBUS: Device with no driver: device/vif/0
0.268090] /usr/src/packages/BUILD/kernel-xen-2.6.34.4/linux-2.6.34/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
12.820200] Freeing unused kernel memory: 352k freed
12.820366] Write protecting the kernel read-only data: 7104k
12.859878] netfront: Initialising virtual ethernet driver.
12.967432] udev: starting version 157
13.014760] NET: Registered protocol family 17
14.294123] RPC: Registered udp transport module.
14.294133] RPC: Registered tcp transport module.
14.294141] RPC: Registered tcp NFSv4.1 backchannel transport module.
14.299798] Slow work thread pool: Starting up
14.299871] Slow work thread pool: Ready
14.299914] FS-Cache: Loaded
14.310745] FS-Cache: Netfs ‘nfs’ registered for caching
So, it looks like the virtual Ethernet driver loads correctly, as do all of the NFS modules. If I look at my DHCP server’s log file, I see that an IP address is picked up by the interface. However, a tcpdump on my NFS server shows no attempt by the system contact the server.
Any hints?
-Nick