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/
Home Products Support Community News


[Xen-users] Trouble booting domU over NFS

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Trouble booting domU over NFS
From: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>
Date: Mon, 13 Sep 2010 15:47:39 -0600
Delivery-date: Mon, 13 Sep 2010 14:48:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I'm attempting to boot a domU with a NFS Root filesystem.  I've configured by 
domU with a network interface, the DHCP option set correctly, and the necessary 
nfs root options.  The domU is supposed to run openSuSE 11.3.  I've also used 
mkinitrd to generate the necessary initrd image with xennet, nfs, etc., and 
have this configured correctly in my domU configuration.  However, every time I 
try to boot it, it seems to just hang.  Here is the last of the output:

[    0.271143] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
[    0.271369] TCP cubic registered
[    0.271510] NET: Registered protocol family 10
[    0.271876] lo: Disabled Privacy Extensions
[    0.272102] registered taskstats version 1
[    0.272135] PCI IO multiplexer device installed.
[    0.272147]   Magic number: 1:252:3141
[    0.272158] XENBUS: Device with no driver: device/vif/0
[    0.272163] 
unable to open rtc device (rtc0)
[   12.824902] Freeing unused kernel memory: 352k freed
[   12.825043] Write protecting the kernel read-only data: 7104k
[   12.863444] netfront: Initialising virtual ethernet driver.
[   12.971358] udev: starting version 157
[   13.052730] NET: Registered protocol family 17
[   14.172028] RPC: Registered udp transport module.
[   14.172035] RPC: Registered tcp transport module.
[   14.172043] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   14.177726] Slow work thread pool: Starting up
[   14.177851] Slow work thread pool: Ready
[   14.177911] FS-Cache: Loaded
[   14.188728] FS-Cache: Netfs 'nfs' registered for caching

So, it looks like xennet loads correctly, and, in fact, looking at my DHCP 
server logs, I see that the domU picks up an IP address.  However, this is as 
far as it gets - it never contacts the NFS server, and there's no further 
output on the console.  Any hints would be greatly appreciated - I've tried 
increasing verbosity of the boot process, doing TCP dumps, etc., but I'm not 
able to figure out what the domU is attempting to do and what's holding up the 
boot process.


This e-mail may contain confidential and privileged material for the sole use 
of the intended recipient.  If this email is not intended for you, or you are 
not responsible for the delivery of this message to the intended recipient, 
please note that this message may contain SEAKR Engineering (SEAKR) 
Privileged/Proprietary Information.  In such a case, you are strictly 
prohibited from downloading, photocopying, distributing or otherwise using this 
message, its contents or attachments in any way.  If you have received this 
message in error, please notify us immediately by replying to this e-mail and 
delete the message from your mailbox.  Information contained in this message 
that does not relate to the business of SEAKR is neither endorsed by nor 
attributable to SEAKR.

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>